A mixture of Computer Science and Software engineering related writings, study notes, book reviews and general ramblings. Opinions are my own - enjoy!
See the first post in The Pragmatic Programmer 20th Anniversary Edition series for an introduction. Challenge 1 While reviewing a draft of the first edition, John Lakos raised the following issue: The soldiers progressively deceive the villagers, but the change they catalyze does them all good. However, by progressively deceiving the frog, you’re doing it harm. Can you determine whether you’re making stone soup or frog soup when you try to catalyze change?
See the first post in The Pragmatic Programmer 20th Anniversary Edition series for an introduction. Challenge 1 Help strengthen your team by surveying your project neighborhood. Choose two or three broken windows and discuss with your colleagues what the problems are and what could be done to fix them. I’ll discuss one example from work recently - exact details removed of course. Our current main project is the next version (3) of our main API.
See the first post in The Pragmatic Programmer 20th Anniversary Edition series for an introduction. Taking responsibility, in my opinion, is a large part of what contributes towards being a professional - as opposed to simply trading time for money. Furthermore, it not only applies to Software Engineering but to any profession and everyday life. Tip #4 (“Provide Options, Don’t Make Lame Excuses”) is especially applicable to Software Engineering.
Introducing a a very pragmatic blog post series.
Even Santa has to deal with software licensing and non standard serialisation formats.