Lecture 24: eXtreme Programming - Richard Buckland
extreme programming, unit tests, test as you go, unit tests in C, one objective at a time, refactoring. asserts.
multi-file programs in C. linking. #include header files prototypes. main. static helper functions. object files .o files
Also: hornblower patriotism / the french
Пікірлер: 92
re-watching this lecture 10 years later, really inspiring lectures from Richard Buckland.
Excellent and engaging lecturer.
Awesome! thanks for sharing. Another teacher, that is worth listening.
Rewatching this video years later. Damn, he's good at explaining things!
Really inspiring teaching... Making/keeping an interesting subject interesting. You'd never guess how tricky that can be sometimes....
this guy is awesome...I wish I had teachers like him. I learned something today
Fantastic ! A truly engaging lecturer !
0:47 Introduction 1:19 Waterfall 5:15 XP Introduction
Great video! Love learning this stuff...
2014 now still incredibly important and working well extreme programming concepts.
I needed this... thank you!
Awesome video! I'm going to give this methodology a try! Thanks!!
Brilliant presentation.
superb teaching... love the way he is delivering the knowledge... gud enth too..
i like this teacher.... it's awesome...
amazing lecturer
Brilliant teacher
Yes he is a wonderful teacher with lots awards, he was my lecture on monday for enginnering design in law theatre:) i am so lucky :)
There is really nothing strange about just start and see where you get along the line. Painters, carpenters, plumbers and lots of other craftsman work that way for thousands of years.
i wish this was my teacher! he knows his stuf n hes not the boring type. great job bro
This prof is lots of fun!
such a awesome teacher lul. Hes so interactive and into it :3
Thanks. I finally understood tests :D
UML is a high level abstraction. If it isn't a higher level abstraction you may as well say you are writing code. In actual fact tools like Delphi were very much visual. Point is that you will often find that lower level implementation details allow you to discover better higher level abstractions. UML is primarily for communication of architectural structures, not for low level implementation detail.
This man is amazing.
Allthough I'm not a student of computer science I understand nearly everything. And to not spam the commentsarea of the other videos for the same reason I say it here for them too, they're really informative...keep up the good work :D
Its awesome that he teaches it. Some comments are not true (i.e. never delete tests, every code-File has a testFile (maybe in c its true, but in Java this is for sure wrong), but hey, better close than nothing.
DOES THAT MAKE SENSE? I love this dude.
Rather than sigh and feeling sorry for ourselves; we should be happy to get a recording of his class online.
This is the best teaching online! He puts other lame videos to shame :)
This guy makes me actually want to do my homework!
Best teacher..
This guy is power packed fun...
I'm only just out of university but this is bringing some memories back :) I was the only question-asker in class
Love it
I am no programmer, and i dont understand anything about it. This i understand actually, and is was great fun listening. Good work!
i wish i get a professor like that when i go to school/collage !
@Untouchab1e I agree... I'm from Romania, a Computer Science student at one of the best universities here. We did a whole Sudoku Solver using 2-3 strategies in 2 hours during a lab. Needless to say, it was immensely stressful. Sure, we got the job done in a shorter time but we missed all the important things like testing thoroughly, talking to your partner, etc. It really sucks! Our school system is a lot of work without moral support. Also, we just jump in the technical details and don't think
Programming is really a psychological thing!! :D
God perfect teacher
Muito Bom ...
ashoom! hehe This is a really good lecture :) Wish I could go back to school.
Makes me wanna stop going to school and learn from these videos lol
Perhaps, but the pertinent question is: would using a waterfall methodology have helped? And that's not an easy question to answer - you have to know the intimate details of the project, including why it failed, etc.
Wow, he's awesome! He could even make history funny :D
I love this guy! "It will put out this compiler error message: 'Compiler is saadd :('" xD
I once had the craziest bug in my program that I could never solve. It appeared as if the program was partially running backwards. :) It was really simple stuff aswell, and I could never find the reason for it. In the end, I just had to assume the compiler was bugged or something, and I gave up.
"your test on our code and our test on your code"
I would love to be on one of his classes
so all this time that I have been programming I have realized I have been doing extreme the whole time.
This guy is fuckin awesome, why ain't all teachers like this :/
He reminds me so of Frezned, and not just 'cause of the accent, but also his personality and even his face and haircut. You can see what mean really well at 23:25 - best part is, Tom is studying programming, isn't he?!
The hardest thing about programming is knowing when to release.
omg, he's such an amazing teacher :D... and he looks like john green :D
"Does that make sense?"
Teacher makes a major mistake-only the module’s public interface should be tested. Do not write tests for private functions as it inhibits refactoring. Your public interface tests will cover all the private code and will validate that they are correct indirectly.
@JohnKerbaugh
8 ай бұрын
This is definitely just an opinion. There's no hard rule on where to draw lines for unit testing. Some organizations set minimum percentage code coverage. Some don't have any. Some projects lifecycle and value wouldn't make sense to put much time into testing.
Unit testing without the big picture sounds like suboptimization to me. Plus redundant programming. I'm not sure, but I suspect it would be better to move all the testing to the system level with use cases. ZERO unit testing! Which means DRY programming (don't repeat yourself). ;-)
So what happens to your unit tests if the refactoring you would need to do is caused by a change in a software feature that will invalidate your unit tests you have written? We know this happens a lot especially when the users don't really know what they really like until they've tried it.
Any one know if their are any more videos of this guy ?
cool And I am from Algeria
Great Talk! but first 10 minutes are about Agile, and not specific to XP ... right !?
thats ausie john green right there
Poor guy, he rlly needs a new blackboard :DDD yea, he's amazing!
DROPPED THE S-BOMB
if only "specification told i can assume" so my program can do whatever i want for illegal input and i'm correct worked in real life situations..
He's quite funny.
3 people are french
waaaa-teeeer-faaaaall- method! LOL he is stoned as fuck.
You never throw away a test? How come software needs refactoring but tests don’t? Aren’t tests programs, too?
Watoh fall method
When you see it ..... lol
27:52 - 27:54 lol ^^
cool, I am from planet earth.
lol i just watched extreme ironing
WOW awesome teacher when i ask my teacher some question he is like "ok you asked question you got my attention now I'll FFFF you and FFFF you with hardest questions till you cry" and I'm from Pakistan, Ignore my name :(
like like like
Meanwhile everyone has moved from waterfall to bug filled hellscape of agile.
LOL I HOPE I WAS HIS STUDENT AHMED FROM DUBAI
why use the static keyword, why not private?
Great 😂😂 waaaterr faal method
TDD/BDD forever and ever ;)
what is ashoom xD
It's just an odd pronunciation of assume.
is Richard on facebook?
ima nigga programmer. i programm in the hood
? photoshop = big.. = 1500$ ++ small product = mp3 to wave converter (dll/static libaray) = 30/45$ 30 day use.. keygen/cracked.. no one pays.. same goes for photoshop but they send out notices to illegal users to peoples HOME mail's and you might go to jail/fined (happened to me I got warned =P they contacted my ISP and sent me home letter). Now is it better to sell good products or cheap ones? up to you really :) I would always code big.. maybe interfaces for me
This guy is a machine, talk too fast.
maybe.. but whats the point? when u are going to improve a structure you will have to redo everything refactoring is for losers. Better start with a good layout so you don't need to improve anything in long run. think big.
yah its better to make a crappy program in 1 hour then waste 6 hours writing a good program.. then just keep improving the crappy program if u still have time.