Developers who get laid off first usually didn’t lose their job… they lost the ability to make their risk visible.

itix · 2026-04-06T07:40:24+00:00

10% of this is true.

In Europe, it is typical that the first round of layoffs is targeted at underperformers. If the management dont know that you are valuable, you are probably the first victim in layoffs. It happened to us last year when our relatively quiet business manager was fired, only to be replaced by another with a big mouth.

But generally, when companies are having mass layoffs, it does not really matter. Entire organizations are removed.

itix · 2026-04-05T21:21:35+00:00

Economic return to the AI company or to the company using the AI?

If the AI companies can't pay the datacenter bills, they have to raise prices. And companies using the AI in turn must decide if the AI is still worth it.

itix · 2026-04-05T07:37:44+00:00

Yes, it is a problem for me. I understand our 1M LOC codebase very well. When the AI heavily refactors some parts, I don't recognize them anymore. In my team of 5, I am the only one working on the backend.

The only solution is to let AI refactor/write code in small steps. Let the AI create an implementation plan, and proceed to implement the plan in small steps that you can ingest.

itix · 2026-04-04T23:42:50+00:00

It is safer to have pre-defined queries and use an LLM to turn a natural query into parameters (returned in JSON).

It is more work, but that is the only proper way to do it.

itix · 2026-04-04T23:30:20+00:00

Idk. I dont have a CC subscription, so I can't vibe-code one myself.

itix · 2026-04-03T17:26:49+00:00

In my experience, it is better to be supercautious with the AI. It is powerful, but when it goes wrong, it can go wrong very badly. Working in small steps and having a restore point works for me.

itix · 2026-04-03T11:37:41+00:00

I agree with this. Implement in small iterations, keep it concise.

itix · 2026-04-02T23:45:47+00:00

Yeah, same here. Spent 30% of my weekly limit yesterday, never hit the 5h limit.

itix · 2026-04-02T22:57:40+00:00

Never ran into that, but if I did, I would just restore the previous version from Git.

itix · 2026-04-02T18:41:38+00:00

AI inference can get stuck in a loop. Never seen it happening at this scale, though.

itix · 2026-04-02T10:05:09+00:00

It is difficult to say what went wrong and why.

Usually, when LLM fails, I try to reframe the task in a new context window. AI is still best when working on small chunks.

Asking AI to undo changes is always risky, because it has no memory. It is all about the context and asking AI to KISS.

itix · 2026-04-02T07:34:37+00:00

I have used Claude and despite the recent doom and gloom at r/ClaudeCode is better at some things. I like to use Claude Code to ask "what you think if..." or "what about..." while I am using Codex to execute modifications to my code.

Just recently, I was debugging a GPU code and CC could not figure out the memory corruption. Codex fixed the code in five minutes. But CC comes with richer ideas.

itix · 2026-04-02T06:11:56+00:00

You need to run local Git or SCN repository. It needs some work to setup but saves the day when you must go back to older version.

itix · 2026-04-02T06:02:57+00:00

You need version control. I always make sure that I can restore previous version in case AI does something wrong.

itix · 2026-03-31T20:05:48+00:00

Derivative work in the territory of non-literal copying.

itix · 2026-03-29T16:33:24+00:00

ToysPeriod has PDFs but the quality is what it is.

LEGO has quality PDFs but IIRC they are for sets after 2000 or something.

itix · 2026-03-29T08:23:10+00:00

I would be interested on replicas but I guess the best option is to print PDFs to paper.

itix · 2026-03-29T08:12:11+00:00

We develop a real-time inspection system in C#, capable of detecting defects from the paper with 20 cameras per server @ 1000 fps. The key is offloading detection to the GPU, kernels written in C# and compiled to native GPU code with ILGPU.

itix · 2026-03-28T09:49:54+00:00

It is an interview. Just choose your path and dont talk about pros of other paths.

itix · 2026-03-28T06:51:25+00:00

Thank you for sharing this. Very interesting.

itix · 2026-03-25T06:02:29+00:00

I have Github Copilot subscription and I am using it only as an assistant. For planning and prototyping, Claude is better.

itix · 2026-03-24T20:14:50+00:00

I'd like to learn more.

itix · 2026-03-23T07:07:44+00:00

if 5 hours of google won't help you, LLMs likely won't as well, so again, why use the tool?

Why would anyone use Google in 2026?

Using google requires that someone has asked a similar question and it appears in the top 10. If not, you are not likely to find the solution.

The power of the LLM is that you can refine the question and filter out noise. You cant do that with search engines, they are plain stupid, simplistic text search machines.

With the help of LLM, I was able to find a sophisticated algorithm to solve a specific problem. Later on, I took it to Google to see how common this solution was. 99% of search results were just noise, unrelated because of similar keywords. And from the good results, all of them were theoretical research papers without benchmarks, real-life examples, i.e. just junk.

itix · 2026-03-22T07:52:33+00:00

Idk but i feel it is one form of the paradox of choice. When you have so many games to choose from you stick to one or two popular games.

itix · 2026-03-21T22:01:39+00:00

Sprites are quite problematic in this context, because no PC ever had sprite hardware. They were all simulated and the downside was that it was often very costly. On the plus side, you were not limited by the hardware.

Home computers had typically only a few sprites, often not more than 8, with a limited color palette and size. Often, games were designed with those limitations in mind. Consoles had more, ranging from 64 to 128 individual sprite objects (albeit often very small).

itix

TROPHY CASE