Well, people asking relevant questions slow you down obviously... since the goal about the latest set of generative models is to "move them into customers hands at a very high speed" this creates tension. Instead of slowing down they seem hell bent at throwing ethics out of the window.

Looks like it completes Comby nicely for the search only case.

Definitely this. If it's too fancy and fashionable you're likely to pay it in later with the undue complexity it introduced.

Une histoire édifiante sur le sexisme ordinaire... et tout le monde regarde ailleurs.

Interesting advises for higher management roles. The information gathering and the distorsion fields are key factors to have in mind to not loose perspective. Otherwise it's when you'll start doing more harm than good.

Indeed, it's important for architects to get their "hands dirty". Organizations where it's not the case prevent their architects to challenge their assumptions pushing them to stay in their ivory tower. It's a good way for bad decisions to pile up over time.

An often forgotten feature of git. That said it is very convenient when we need to juggle several branches at the same time. This can save some time and space.

Very thorough overview of everything you can do with vim but also your IDE vim emulation.

Early days but could turn out useful when it gets more complete. Good way to easily have a CI pipeline targeting mobile platforms.

This is very very centralized. No good surprise here unfortunately... and still email is really tough to fully self-host.

The report is very US centric. Still it looks like the future standard for developer jobs will be more and more remote.

I find debuggers to be underused at quite a few places. A shame when you see what they can do nowadays, and they keep improving!

Neat way to think about array indices, if it was widespread it would simplify a few things in documentations I think.

Very interesting conversation between Uncle Bob and one of the recent critics of his work regarding performance. I like how he admits some faults in the way he presents things and try to improve for later rather than trying to be right. Some people should learn from that. There's clearly a tension between performance and what is described in Clean Code, it'd be pointless to deny it.

Fascinating old school way to manage cables. And indeed the result looks pretty as well.

People tend to be fixated on the "unsafe" keyword and assuming not using it will make their code devoid of memory safety bugs. Well, it's a bit more subtle than this. It helps you know where such bugs can hide but it can't completely prevent them all the way down the stack.

This is definitely a worthy advice with lots of interesting side effects. For me the main motive beyond cheer curiosity is developing more empathy towards others with different roles.

This is an excellent piece. Very nice portrait of Emily M. Bender a really gifted computational linguist and really bad ass if you ask me. She's out there asking all the difficult questions about the current moment regarding large language models and so far the answers are (I find) disappointing. We collectively seem to be way too fascinated by the shiny new toy and the business opportunities to pay really attention to the impact on the social fabric of all of this.

Hiring and interview isn't simple. There are good advises in this piece. In particular I strongly agree with the fact that leet coding is probably not it and that having something guided and scripted it necessary.

Early days for this type of research so a couple of limitations to keep in mind while reading this paper. Most notably: rather small sample explored (it's a qualitative study) and tends to conflate GitHub with "the Open Source community". The later especially matters since the vibe can be very different outside of GitHub.
That being said, very interesting findings in there. Some validate my experience with GitHub. It's clear that compared to other spaces there's much more entitlement behavior from some people. Interestingly the words seem on average less violent (although it does happen of course) than in other platforms... still this is important to keep in check since it could have implication toward prospective contributors.
The last point in their discussion section is promising. Some of the current manual interventions from maintainers seem to have good results (encouraging) and it seems possible to at least semi-automate the handling of toxic comments which could help with maintainers well-being.