koliber

I’m not an accountant and what you’re saying is probably right. However, if you hire an engineer to do R&D, build systems, and take R&D tax credits, it “feels” like capex.

Replace “Claude code” with “programmers” and you get what we’ve had up until now. It’s all just moving quicker now.

You don’t need to teach anyone about this. The wealth tax should apply to extremely wealthy people, not everyone.

If you accumulated a fortune, there was some skill at play. There was also considerable luck and some exploitation. The wealth tax is a way of paying back for the luck and exploitation.

You will still be extremely wealthy.

Paul wants to play the fairness card. Life is not fair and those who accumulated massive fortunes won the lottery. Don’t let the massively rich conflate issues. Don’t get fooled.

Is it capex of training new models and hiring people for 250mln pay packages? Or is it opex running inference?

Absolutely right. I had a "math moment" myself. I was thinking margin instead of markup.

EDIT: [ IGNORE THIS COMMENT -- IT IS WRONG - I had a "bad math moment" myself ]

The math seems off. How is 7.8 million vs 4 million 95% more expensive. Article makes good points but I doubt the numbers as they don’t add up.

Still agree with the conclusion though.

You’re right and that’s intentional. Japanese companies don’t optimize for efficiently but for longevity. Sometimes those things go hand in hand. Sometimes they don’t.

The article makes a good point, but it's based on a polarized view that people make good judgement and AI is incapable of making good judgement.

I've worked with people who demonstrated below-average judgement, and I've seen cases of good judgement from AI. I think if a company can identify the poor performers and part wit them, there is a decent chance that the remaining people with AI in hand can more than make up the difference.

Now given the logic that you can't be dependent on any one service to run your SaaS, how does Railway convince its customers to run their SaaS on a single service?

You can have an offboarding doc even if you don’t have employees. It will apply in the future once/if you do. It will be silly and useless now, but you can check it off as a YES.

How will you know that it produced correct code if you don’t know how to write it yourself?

If a behavior is undefined, the theoretical answer to this could be anything, including -123, 500, or 0. We are just lucky that the compilers choose a more sane version of undefined behavior in practice.

I don't. But many others do. The only thing that let's banks and other companies know that you are dead is a piece of paper called a Death Certificate.

A doctor friend of mine once joked that it would be really cruel to issue a death certificate for someone who is alive. This seems to be a soft version of that.

The only thing that would be crueler is to revoke someone's birth certificate. "Sir, you never existed in the first place."

What you are talking about is in a large part authentication. You can do authentication using an external service and still have your user table locally. You can also do authorization locally with a local session table while leaving authentication to a SaaS.

Many engineers with a long career have probably thought about becoming a manager at one point. A large portion of them decided to stay in the IC (individual contributor) track because they did not like some of the aspects of being a manager. Some decided to stick to the IC role because they liked creating code.

With AI, every engineer will need to become a manager to manager one or more AI assistants who do a lot of the work. The good news is that this will not involve dealing with performance reviews, psychological problems, and raises. You will also remain close to the code.

Look at the manager role again, and see which parts of it will be needed to manage AI agents. Learn those parts from standard management books. You will kind of pivot, but still remain close to the code.

On the other hand, if all you enjoyed is typing in code, but hated working with product people to understand the intent, doing code reviews, or building software that is easy to QA, there will be fewer and fewer such jobs.

She is a woman.

There are so many shades of gray in freedom of speech. In free European countries the police are also not at the door of outspoken government critics.

If you are alluding to dictatorial European countries like Russia and Belarus, the US is miles away and moving in their direction. Compared to Western Europe, there is no difference.

Lately I keep hearing the same thing over and over: the things that are good for managing a team of devs are good for LLMs.

Good test cases.

Clear and concise documentation.

CI/CD.

Best practices and onboarding docs.

Managing LLMs is becoming more and more similar to managing teams of people.

Bad UI plagued software development since ages immortal. The reason is not AI. Good UI design is a skill (or art?) and not an afterthought. But most people do not see it that way and that is why things are the way they are.

Most small companies don’t need AI to be more efficient. They need Excel.

I’ve already had two cases where a friend asked me to show them how AI can help them run their company better. In each case it turned out that they needed Excel. Specifically an excel export from one system, some bulk editing, and an excel import into another system.

(I understand the satire in this article but this is a serious post)

A long time ago a vast majority of people on earth were farmers. They used relatively simple tools like scathes.

Over a few centuries better tools and technology made it so that <5% of the population in rich countries are farmers. They use tools like million dollar harvesters.

Is it like CSS for HTML?

After looking at it for 1 minute, it seems that this is to markdown what CSS is to HTML.

How accurate is that?

There was a time when there were no separate names for blue and green in the Japanese language. Some languages right now have concepts of fundamental colors like navy blue and light blue, where English rolls it into a single "blue". Naming colors is highly cultural and changes over time. The idea that colors have boundaries is fascinating from both psychological as well as linguistic perspectives.

The framing seems stupid if you take the naive perspective that your language's way of dividing colors is the only valid one. Exercises like this and discussions that follow help expand perspectives.

Correct. Order-of-magnitude-wise, it's roughly the same as the alternatives.

In the context of writing a new service for a new company, you should not spend one second thinking about whether your technical choices will allow you to serve 100,000 requests per second, or 150,000 requests per second. If you are, you are focusing on the wrong thing. If you get to 1,000 requests per second with a real paying client base you already achieved more than most dream of.

On the other hand, if you are optimizing a mature distributed low-latency equity trading system that is consuming ten's of thousands of market data ticks per second, a 50% improvement in performance on a 20 machine cluster might turn into some real $$$ savings. But that's not what this article is about.

postgres is great and is also a good default choice. It needs a bit more setup than sqlite. Unless I need a capability that postgres provides, I go with sqlite. It just works.

Apple should build this, and start giving away free Macs subsidized by idle usage.

Communicating with an attorney is protected by privilege. In this case it seems they ruled that researching your case is not protected by privilege.

What about drafting communications with an attorney? Is a draft email that has not yet been sent protected? What about a Word doc containing a draft of an email? What about a Google search for “how do I spell amfeetamine?” that is part of your process of drafting your communication with your lawyer?

The reality is that things will be blazing fast in any language if you save things by PK in HashMaps.

Backups are super-simple as well.

I'm also a convert.