damethos

I personally feel very lucky that I experienced the days were we had to wait for the updated MSDN DVDs to arrive so we can check out the new docs/code samples and make changes to our drivers and docs! Good times.

I am experiencing the same. I have decided that the only way to use these tools (at least for now) and at the same time to avoid the janky crap and understand what's going on with the codebase, is to ask from the model to work in very small committable batches which I can review without my head exploding, commit in branch, repeat. I feel much better now and I catch things fast and early.

Are you implying that there isn't an operational cost for maintaining the infrastructure to support cashless payments or that it's cheaper? Unless I see actual numbers I am not convinced and that 1% you mention sounds completely random to me and not really "the true answer".

Nostalgia activated. I now have to play Grim Fandango! Loved that game!

The article had me at "[...] every new feature is the one that's going to be the one (but certainly not that one that was supposed to be the one during the previous sprint)".

I have fought way too many times the new "the one" feature. Just ship it, it's already good enough, everything else just adds cost, especially psychological cost to the team.

I am not a Fastmail user but I completely doubt this. I have been using Gmail for 20 years and I have never seen a spam mail land in my inbox which has always impressed me. Everything else I have used from time to time does miss a few, which I guess it might be acceptable if you want to move to another host.

I still read programming books, especially if I want to check out a new language and get the gist of its capabilities and how are things are done in that specific environment. Also I prefer to read a book written by an author that I know has the experience and the insight to actually write the book than read random sources on the internet. Or maybe I am just used to it.

Time to re-re-re-re-N-watch this!

"covered/invisible knowledge" aka tacit knowledge

I have the same questions in my head lately.

Hey Mike! Alex from GR here. Good to see you around :)

Probably just let them vent until they adjust their habits and just chat with their co-workers, without the need to use this as an excuse. Then, they can enjoy the fast loading times :)

- How big things get done

- The Tyranny of Merit: What's Become of the Common Good?

- The Pragmatic Programmer: From Journeyman to Mastery, 20th Anniversary Edition

- The Secrets of Consulting: A Guide to Giving and Getting Advice Successfully

- Rework

Added them on my blog as well with a small review on each in case anyone is interested: https://www.alexanderlolis.com/my-2025-reads

Loved the article. I completely agree. We ALL need more thick days.

This has been my experience as well and I will probably end up paying for a tool because the free ones just don't work smoothly.

I was using SmartGit for many years and was very happy with it, until they made it subscription based and had to switch to SourceTree. It works but I do not find it very smooth at all. It hangs every now (using MacOSX) and in general the experience is not as smooth as it was with SmartGit. I am surprised that you are saying that you haven't come across any better tool.

This is pure awesomeness. It made my day.

I liked the article, but I also laughed a bit because <sarcasm>it was the engineers’ fault that they didn’t rise to the occasion and skip-level to save the company!</sarcasm>

Useful, but 10 years ago without JSONB in PG it wasn't really the answer to everything. But as of today, I am recommending PG to anyone that does not have a good reason or use case to NOT use it.

This comment sums up my view as well, but I must confess that I’ve designed architectures more complex than necessary more than once, just to try new things and compare them with what I already knew. I just had to know!