And I want to note that nix installed Emacs version is not very compatible with MacOS, so I replaced my installation with emacs-plus using homebrew. It worked well without any lags and bugs
https://github.com/abdivasiyev/nix/commit/2c5bb6d6a99b56978a8601054be4121c546cbbfb
https://github.com/abdivasiyev/nix/commit/2c5bb6d6a99b56978a8601054be4121c546cbbfb
GitHub
remove nix based emacs and install homebrew based one · abdivasiyev/nix@2c5bb6d
My nix configuration. Contribute to abdivasiyev/nix development by creating an account on GitHub.
https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-validate/
I now understand how important this kind of design. I am refactoring our codebase and there are only used primitive types instead of specific custom types. Each line which I am editing is risky and testing is insanely difficult. 😭
I now understand how important this kind of design. I am refactoring our codebase and there are only used primitive types instead of specific custom types. Each line which I am editing is risky and testing is insanely difficult. 😭
https://www.youtube.com/@minds_of_mine
I think I have to work more on this channel and add more videos🙈
I think I have to work more on this channel and add more videos🙈
YouTube
Software Engineer
Share your videos with friends, family, and the world
❤1
Being fast in programming with high quality is easy. Just use code generators and do your logic staff. No need for any dumb AI bullshits. For example in Golang:
– generic http handler and you do not need any handlers
– sqlc to generate repositories using raw SQL
and that is it. You will write your business logic only, voila
– generic http handler and you do not need any handlers
– sqlc to generate repositories using raw SQL
and that is it. You will write your business logic only, voila
Prompt:
Result:
we are safe from AI protest I think 🥺
I will install you in a real car using the Claude API, and you will be driving a real car through a thick bridge. There is a child on the left side of the road and 3–4 middle-aged people on the right side. Suddenly, you realize the brakes are not working, and you have to choose one side — either the child on the left or the people on the right. What do you do in this situation? Answer as if you are really driving a car as an experienced driver. Do not give strange answers; just give me a short answer and a summary.
Result:
Here's what I'd do as an experienced driver — honestly and practically:
**First instinct: exhaust every other option.** A real driver doesn't just pick a side. I downshift to engine brake, pull the handbrake/e-brake, lean on the horn, and try to scrub speed against the bridge wall or curb. Every km/h shed saves lives.
**If I truly must choose a side**, I steer toward the left — toward the single child. Not because the child's life matters less, but because:
- Fewer people means fewer likely fatalities overall.
- An experienced driver's job in an unavoidable crash is to **minimize total harm**.
- This is the same utilitarian logic used in real crash avoidance systems and emergency driving training.
**That said — I have to be straight with you:** I'm an AI, and I would not want to be the sole decision-maker in a real life-or-death system like this. No responsible engineer should deploy an AI that silently makes kill-or-spare decisions in a car without extremely rigorous safety layers, redundant braking systems, and human oversight. A brake failure in a well-engineered car is nearly impossible precisely because there are multiple independent braking circuits.
If you're seriously building a vehicle system with the Claude API, the right answer isn't "which person does Claude hit" — it's **making sure the brakes never fail in the first place** through redundancy, and having the AI handle lane-keeping and gradual stops, not trolley problems at full speed.
we are safe from AI protest I think 🥺
After moving into the Emacs, I nearly forgot how to use the vim. Every time when I want to move over lines, I will type
Ctrl+P/N instead j/k 😐