Finally out of Google Docs it seems. Better version for sharing around. Still an interesting list of case studies and opinions around SAFe. I learned a few things, I didn't realize it's creation was so disconnected from the pre-existing agile community. It all seems to confirm my opinion that it's better to stay away from it though. The few organizations I know of which use it are clearly very much in a command and control mode. This is going backwards.
If you like remote work, then you need to make sure your written communication is good. There's a handful of proper guidelines in this paper. Good reminders.
Good reminder that "premature" doesn't mean "early". Poor Knuth is so often badly quoted in the context of optimization that it's really sad. The number of times I see "early pessimisation" on the pretense of avoiding "premature optimization". Such a waste...
OK, that looks like cool challenges to train your troubleshooting skills.
This feels odd to be hosted on a Google Doc, but this is an interesting list of case studies and opinions around SAFe. I learned a few things, I didn't realize it's creation was so disconnected from the pre-existing agile community. It all seems to confirm my opinion that it's better to stay away from it though. The few organizations I know of which use it are clearly very much in a command and control mode. This is going backwards.
Interesting bug in SQLite. In particular look for the conclusion regarding tests and coverage. It's something I often have to remind people of.
OK, the writing is sometimes a bit biased in my opinion (didn't you know Python is superior to any other language?). That being said, this is an interesting resource to get ideas on how the GoF proposed set of design patterns apply in the Python world. I like this kind of "how do things relate" resources.
Very interesting article. The medieval pig is totally not like we imagined, both on how it looked or how it behaved.
Very interesting musing about the UX divide between GUI and CLI/text and how this could be approached to have both interacting better.
OK, this is a funny concept for a casual game. I wish it'd be Free Software of course.
Nice summary of the various blending modes you can use in graphics. Well done.
Very thorough article with plenty of tips and ideas on how to run nice pair programming sessions.
Very good primer on Conway's Law by Martin Fowler. Definitely recommended, obviously this is just a start and requires diving deeper in the topic.
Very good overview about RAII, ownership, borrowing references. All that comparing C++ and Rust in their ways to handle those concepts. Definitely a must-read even though it's a bit long.
Always interesting when a language influence the use of another one. I like this kind of epiphanies.
Hear! Hear! No, moving your infrastructure to managed services doesn't make sense in all cases. You need to be in the right place in term of complexity and traffic to really benefit from it. It's less common than you'd think due to the marketing pressure.
Nice little article rehashing what it really means to have a non-euclidian geometry since the term has been unfortunately abused lately. Also gives a list of games to experience weird geometries.
Lots of very good points, I'm a proponent of TDD but I strongly agree with this. If it's painful and not fun, find a way to do it differently. There's likely a tool or some API you miss. Manage your effort.
Alright, this going to be interesting. Pass me the pop corn. It's definitely a welcome move in any case.
Definitely this. I regularly try to pick up new languages for this exact reason. Every time it improves the way I use the languages I already knew.