ta238911

I never understood why people like Musk are admired that much. He's a bully, period. If you cheer a bully, you're probably also one.

Played around with the very first IBM PC, running CP/M. I value these experiences - computing was much more direct than it is today.

I probably would not enter the field today.

It's best, when you can take a break and know money is still flowing in. That requires a separation from hours worked to the money you earn.

Imagine most people could live off passive income (like dividends) - we could all work less, I guess.

A great recap of some papers: Software engineering's greatest hits.

* https://www.youtube.com/watch?v=HrVtA-ue-x0 * slides: https://third-bit.com/talks/greatest-hits/#1

1. I work full time, on a set of projects

2. if all works out, I'm booked for the next 24 month straight - if I do not have clients' projects I have more than enough own projects to work on (I actually wish for some time off for years, but it never happened)

3. I do not live in the us, but in a rich economy and I am comfortable financially; compared to many people I know I live a simple life, why is probably why I do not need to charge $100+ or more - I'm in the top 10% wealth bracket already and looking forward to three more productive decades.

I know people with way less experience charging more, but I'm in no rush.

Between $50-$80, senior engineer and consultant.

I was lucky that my open source contributions led to some interesting short and long term engagements. If I'm already into something, it may be that I find it interesting - no need to search.

I believe, if you can maintain a genuine interest in certain, contemporary topics than you will probably have an easier time to stay relevant.

Today, depending on your interest, I'd probably would go deep into the "devops" field, since that's quite technical, fast moving but with lots of stable parts (like operating systems) and there's demand and will be for some more time.

There's also always a way to stay relevant by just being very good at a very particular thing - even if there are only a few jobs. I remember mainframe people advertising that if you know your way around z/OS you'll never have to search for a job again.

In my ears, knowledge graph sounds a bit grandiloquent. I do not have a definition, but I know that when talking about knowledge as it is embodied in people, it's quite a subtle thing, hard to formalize and to be honest, something relatively rare.

Why can we just call these things fact databases?

Add. Knowledge evokes a lot of other associations as well, for example that what we are able to know changes over time. That a time has a certain underlying grid, into which certain factual stories appear and later disappear.

My perspective on the Nx debate: As developers we can do a lot of good. Over the course of my career I helped millions of developers (through my writing on the net) and tens of thousands people use my code and programs to run things smoother or more efficiently.

I'm not that technically brilliant, but I enjoy finding ways to make the efforts worthwhile and I feel that gives me already a small edge.

I happily pay for sourcehut, not only but also because sourcehut aligns so much with the software world I am hoping to see more of.

Imagine just 10% of the revenue involving software globally would go into supporting all excellent open source projects that millions of people depend on on a daily basis. What a beautiful world that could be.