Zombie

Entrepreneur | Software Engineer | Elixir | Ruby on Rails

[Zombie @MaxRostotski]

@ADHDForReal The first three bullets have no space after the dash 🙈

[Zombie @MaxRostotski]

@mkruglova Супер!

[Zombie @MaxRostotski]

@mkruglova Точка — зайки

[Zombie @MaxRostotski]

@thsottiaux Codex app:
- Easy account switching (jumping between personal and business accs)
- Code review specific commit
- Code review button
- Better naming for the forked threads

[Mitchell Hashimoto @mitchellh]

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.

I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).

It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.

The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.

We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.

I worry.

[Zombie @MaxRostotski]

@thsottiaux LSP integration

[Zombie @MaxRostotski]

@thsottiaux Codex app:
1. Dedicated Code Review button, it’s the most used command
2. Automatic commit message suggestion that can be edited before submitting
3. Show how much context MCPs take
4. Permissions management from the app
5. In questionnaire free form field should have more space

[Zombie @MaxRostotski]

@thsottiaux Really needs a dedicated Code Review button, typing /code review multiple times a day

[Zombie @MaxRostotski]

Implicit dependency anxiety

[Zombie @MaxRostotski]

@lilydavay @YesMolotowa @Sota_Vision О, она прям первая в результатах. Спасибо за идею

[Zombie @MaxRostotski]

@lilydavay @YesMolotowa @Sota_Vision Да, это моя фотка 2023 года. Представьте мое удивление увидеть ее сегодня утром в рандомном твите

[Zombie @MaxRostotski]

@YesMolotowa @Sota_Vision Только эта фотка не имеет отношения к этому событию. Снято не в РФ и не в 2025 году

[Zombie @MaxRostotski]

Jitter in background jobs = mis-tuned queue concurrency. Fix the concurrency. Let the scheduler balance load instead of relying on random backoff.

[Zombie @MaxRostotski]

Good code is boring and predictable. It prioritizes readability and maintainability, ensuring minimal cognitive overhead. It favors clarity and explicitness. It minimizes dependencies and codebase jumping.

PS: Looking for #ElixirLang or #Rails projects. Let's talk!

[Zombie @MaxRostotski]

#MyElixirStatus Looking for a new role! Entrepreneurial software engineer (18+ years of exp: 8 with #ElixirLang, 12 with #Rails, open to #Erlang).

I build readable, secure code, coach devs, keep deps lean, and refine existing code.

Remote (UTC+4). Contract or full time. DM me!

[Zombie @MaxRostotski]

Whoever slips side effects into validation hooks deserves their booleans flipped.

[Zombie @MaxRostotski]

Please never ever do this in your code!

Your karma will thank you later.

[Zombie @MaxRostotski]

@ioquatix No, please don’t.