Very early days for research on this topic and the sample is rather small still. That said the results are interesting, there seems to have a few biases inherent to the use of such an assistant, there's also clearly a link between the AI agency and the quality of what gets produced. We'll see if those result holds to larger studies.
What the title said, there's nothing fancy about optimizations. It's mostly well known knowledge, doesn't change much over time or on different stacks... still it's very satisfying.
Definitely this! It's important to model properly your domain and leverage smart value types everywhere it makes sense. This can prevent quite a few different types of bugs.
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, 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 musing about the UX divide between GUI and CLI/text and how this could be approached to have both interacting better.
Very thorough article with plenty of tips and ideas on how to run nice pair programming sessions.
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.
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.
Useful list of gotchas if you need to dabble in linear algebra. You gotta love those floats.
A bit messy sometimes and a few arguments seem weak to me. Still the core message holds: don't let a framework rule your project.
Very good list. It sets the bar very high! I know most people will fail on a few of those items. It's fine this gives a good direction and something to aim for.
Excellent piece on joy being a better drive than discipline. This then dabbles into why TDD might not work for you.
I definitely agree with this opinion. We definitely don't use state machines enough
This is an interesting simple rule so know when to split something, I like it.
Lots of good insight for a long career as a programmer. Definitely a few things I live by and a few... I tend to loose sight of. More progress to be made.
Indeed a good list of attributes. Not sure if that's the only attributes you want in a team but that's definitely must haves in at least one person.
Unfortunately seems to subscribe to the 10x programmer myth at least partly while trying to debunk another one... apart from that, it was very insightful, shows well how it's a team sport and how you want people to complete each other. The whole "rockstar developer" thing is a recruitment marketing scheme.
Still controversial in the Python community, this post shows a balanced view on where it makes sense and where it doesn't.