

Amazing! Thank you for your comment and allthis informations.


Amazing! Thank you for your comment and allthis informations.


Oh, I remember having read nice blog post about git flow in his blog, thank you.


A good one, thank you :)


Wow, a little bit out of scoop for me right now, but thank you for sharing.
It’s on my todo list to learn functionnal programming, but you know … times running out!! :)


Oh, that’s nice to have a book that speak about programming without code.
Thank you. :)


Nice, thank you :)


Cool, thank you for the podcast, I listen the first episode and it sounds very nice.


Thank you for this nice list. :)


Ahah! But which part is bad!! And which one good!! 😁


I love it !! I think it’s a very very good satire!! 😂😂
Look at that:
What if the liberated code has bugs? Our SLA guarantees functional equivalence, not perfection. Besides, the original open source code probably had bugs too. At least now they’re YOUR bugs, under YOUR license.


Hi, I guess that a point he made could be:
Start with how you talk about your own work. “Implemented feature X” doesn’t mean much. But “evaluated three approaches including an event-driven architecture and a custom abstraction layer, determined that a straightforward implementation met all current and projected requirements, and shipped in two days with zero incidents over six months”, that’s the same simple work, just described in a way that captures the judgment behind it. The decision not to build something is a decision, an important one! Document it accordingly.


They are partner / sponsor : https://selfh.st/sponsor/
… I feel like picking the right DE makes much bigger impact
For me too!
I was used to Gnome and Ubuntu style, and since I bought a Tuxedo I use their OS with KDE, and even if I love a lots of things there is often little things like gesture that are different and I sometimes miss.


Hi, if you like very lite solution you can export your bookmark in an html file.
This way you can see it as a web page and edit it with any text editor.


Interesting read!
My key points are:
So how do I estimate, given all that?
I gather as much political context as possible before I even look at the code.
and
Finally, I go back to my manager with a risk assessment, not with a concrete estimate. I don’t ever say “this is a four-week project”. I say something like “I don’t think we’ll get this done in one week, because X Y Z


The article is nice and the finals observations are saddly so true :/ :(
Even LLMs (Large Language Models) like ChatGPT optimize for the wrong thing. They optimize for sounding confident. For sounding like they know the answer. Not for being right. Not for being honest.


Nice read.
The entire smartphone ecosystem is designed to be used almost exclusively through Google or iOS services: government apps, banking apps, prepaid health-insurance apps, and countless other examples. Even though a phone is a handheld computer, it’s far from being a computer in the sense of giving users real control over the software they run.
That’s for me one of the biggest problem.
Skillsare the new name for markdown file… 😏