alenmilk

In my mind all these productivity systems cook down to creating a list of tasks. The list can be between 4 and 10 items. You do one task at a time and when you are finished you can cross out the task. This is the extent of focus my brain is capable of. Creating giant backlogs and plans is just | /dev/null in my case.

Because of inline css and different fonts on different os-es and generally no guarantees about render size. In short, you have no idea how big a block is without rendering it.

I remember the sysadmins trying to figure out why sqiud was so slow and tracing the system calls. It was because they did not use kqueue/epoll. When he asked the maintainer to improve on this he said squid was fast enough. This was the start of Varnish where one of main ideas was to use modern os-calls to speed up things.

I don't understand. You complain about coworkers getting high pay and complaining while not producing any value. Do you think a downturn and potentially getting fired will educate them in this matters and getting less pay will make them solve actual problems?

Yes, this is true as long as the method or function doesn't contain if's changing the behaviour depending on the data. In other words if the problem is so well defined that you can create a method that solves the problem and it doesn't need to take into account x variations of the problem then it is fine. This is the copy-paste versus creating a function discussion. Problem is the x variations of the problem and you need the code to do different things depending on the variation, we usually break the modularity of the function instead of separating the generic and non-generic parts. Hence the ifs in the function. From what I have seen people are unable to do this in their own codebase properly so I don't think it will happen globally. But on the other hand libraries are kind of the answer to the problem and as problems get well defined, one starts using libraries. Raising the level of abstraction is a continuous process.

If you are used to being the guy everybody goes to it is a big change since nobody will depend on you if you are new. But that is fine, it takes som time to get recognised in a new work environment. If you are skilled it will change in 2-3 months.

But then from the wikipedia page.

The Online Etymology Dictionary states that the use of the term to mean "'calculating machine' (of any type) is from 1897.

The Online Etymology Dictionary indicates that the "modern use" of the term, to mean 'programmable digital electronic computer' dates from "1945 under this name

So computer is the correct term before 1945.

> Computers are programmable. A system created from logic gates, executing a fixed set of operations is not called a computer. Your washing machine is not a computer either.

Found this quote that sums it up nicely.

> The Nimatron.” A non-programmable digital computer.

How can a computer be non-programmable? The whole idea of a computer is that it runs a list of instructions.

>What has the world come to, where technology has been appropriated and we are left paying rents every month and companies are increasingly becoming user-hostile and predatory and monopolistic!

This is the issue. While the subscription model may be the right choice forward it may also be the catalyst of a collapse (like the dotcom bust) if the users get bullied enough.

Beware of the imposter syndrome. It never goes away. If your old code looks awful and embarrassing, you are on the right track (you are learning). Focus on learning to read code. It is more important than writing. Find a good open source project and read some good code.

Haha, no that was missing. I mean all the features/loggers that were used in the project mapped one to one.

I have ported a Spring Boot application from log4j to logback and it was pretty easy since we used slf4j. The code was the same, the only thing I had to do is to convert the logging configuration. The features mapped one to one and it to some fidgeting to make it work, but all in all it was pretty straight forward. Would recommend.

I think the problem here is motivation and keeping it up for so many years. Maybe there is a trick to it. Idk.