Is that actually a thing? All projects I have worked on for 30+ years were monoliths doing just fine thank you very much.
However colleagues are fighting daily battles with an ancient microservices monster. I am very happy that isn't me.
2,848 karma · joined February 27, 2013
Is that actually a thing? All projects I have worked on for 30+ years were monoliths doing just fine thank you very much.
However colleagues are fighting daily battles with an ancient microservices monster. I am very happy that isn't me.
I see that as an opportunity to negotiate something in return from them. And if they refuse I simply move on.
That doesn't make me a super star or whatever. Just more efficient.
Have you actually looked at LEAN proofs? They are typically split into small bite size definitions and proofs, making it easy to dive in where you want, and skip what you don't care about, while knowing that you can trust the conclusions.
I personally think that having hundreds of mathematicians working together as a team is a beautiful thing.
You need to learn to manage your manager(s). Google it.
You can think of a view as a function that computes an output table from N input tables. Kinda like how Excel works but with tables instead of cells. That is extremely powerful.
That is quite a claim. I will argue that Categorical Databases most definitely haven't. Any areas where it is true?
An obvious example is the invention of the steam engine.
Almost all "new" languages presented on HN are basically slightly different flavours of languages that have been around for a very long time. But without the libraries/documentation/tools etc. needed to make it useful.
Or it will turn out we no longer need middle managers because of AI.
Side note: I am pretty sure most companies could fire 50% of middle management and see a dramatic productivity improvement. With or without AI.
Thinking hard (and discussing with experienced colleagues) before writing any code can dramatically speed up your overall delivery time and completely remove whole classes of potential errors.
If you skip the "thinking hard" bit to "go fast" you will probably end up being 10x slower overall.
My comment was more a meta comment on the trap a lot of open source developers fall into thinking that the world will fairly reward them for their work.
What is shocking to me is that people give away their work for free and then get upset when they have financial problems. It should be kinda obvious that one leads to the other. Except in unusual cases (Linus for example).
Yes I agree it would be nice if that was not the case. If people were always generous and always did the right thing. However that is not how people operate in general. Pretending otherwise is crazy.
1. You chose to give your work away for free.
2. You are complaining that you haven't made money from your work.
Is that a fair interpretation of your argument?