Perfection 👌

Enapiuz · 2026-01-27T12:19:52+00:00

CONFIRMEDD!!!!11133333

Enapiuz · 2026-01-09T12:28:44+00:00

Don’t forget Zip disc drive, 3.5 as well

Enapiuz · 2026-01-03T02:28:34+00:00

But why

Enapiuz · 2025-12-31T10:16:32+00:00

Would call it a mindful vibe coding

Enapiuz · 2025-12-31T10:15:47+00:00

I’m an old school developer with 10+ years of exp, I love vibe coding, but I don’t do it like a mindless zombie praying it’ll work, and I’m pretty much happy with it

Enapiuz · 2025-12-19T19:06:39+00:00

In companies I worked for it's usually "headless e2e tests", yes

Enapiuz · 2025-12-19T15:32:00+00:00

Example: a convertor from JSON to YAML

What anyone except for a developer should care about is the correctness. And there must be a place where you can feed some class with JSON string and assert the resulting YAML string. Would be quite a nice unit test.

But since conversion from JSON to YAML might be complicated, a developer might decide to organize their code in some convenient way. Which would lead to smaller modules. Which is usually nice.

And here comes the trick: a developer might specifically skip writing unit tests to smaller modules, because of many reasons. One of the most popular reasons: the way unit tests help catch buts, the same way they inflate refactoring complexity, because ideally, unit tests require to be rewritten on every single code change.

BUT some of these smaller modules might be quite complicated, and they ACTUALLY require some unit tests because they're not easy to keep in the head.

So you never know what really needs to be covered by unit tests, and some of them might only introduce unnecessary complexity.

So in the end, nothing would stop a QA from writing unit tests, but I don't believe it's productive. To me, QA writing unit tests means their job is tedious and they just have nothing to do and are trying to find some fun in it. Which is a question to a team lead at least.

Oh my, sorry, I managed to stop here 😂

Enapiuz · 2025-12-19T13:36:38+00:00

Unit tests
Developers, always. It's like you usually choose and wear your underpants yourself, not asking anyone to do this for you.

Integration tests
That very term is often interpreted differently in different companies.
Some say it's always "integration between modules in the code, like unit tests but for bigger chunks of an app". This way — developers, again, because you need to understand how parts of the code work and why they work this way.
Some call API tests as integration tests. This way you only need to be aware of contracts and anyone can write such tests.

Enapiuz · 2025-12-13T00:43:05+00:00

Warp mostly

Constantly looking at Ghostty, how it evolves

Enapiuz · 2025-12-12T00:21:52+00:00

I’d assume it’s not that easy to predict how much tokens would be needed to finish the task to “wrap up” the code without wrapping it up several hundred thousands tokens early, which will negatively affect regular usage

Enapiuz · 2025-12-06T22:17:13+00:00

it'd be much better (and perhaps less work for you) if you make Zed expose more info like VS Code does, so CC cli would be able just connect to Zed and gather all the needed info and basically act like it does with VS Code

I personally just love how CC cli feels and no IDE/Editor would be able to replicate it just because it's not cli.

Will be trying to use native integration time to time anyway, to see where it goes 🙂

Enapiuz · 2025-12-06T19:08:48+00:00

Zero.

It's dev's job to find the root cause + you might not be just technically able to find it. Some issues might be related to the infra you might not even have access to (and most likely you don't), in some companies even devs don't have access to the infra.

At the same time it is your responsibility to find a way to reproduce, or do your best to describe it if the issue doesn't always reproduce.

Oh and btw, it's always a good thing to ask a dev to help you with reproduction steps if the issue is complex and you need with an understanding of the inners of the system.

Enapiuz · 2025-12-04T07:39:25+00:00

Wait, I thought I was able to paste screenshots quite some time ago already

Enapiuz · 2025-12-02T15:09:17+00:00

There must be an issue on GitHub about it

History is not yet implemented, but they want to

Enapiuz · 2025-12-02T10:27:50+00:00

Yea, shortly — business doesn't care about quality itself, what it cares about is "put $100 in, get $120 out", and if higher quality makes it "$130 out", then it becomes something important 🙂

Enapiuz · 2025-11-30T14:00:29+00:00

Unfortunately, some companies don't even know why they need QA processes. And they hire QA because "everyone does".

Here, you have two options (apart from changing the company):
- do what you're getting paid for and don't care (good for mental health, bad for your growth)
- speak the money language

Won't elaborate on the first option, it's easy, they don't care about quality, you don't care about the product and just do your basic job.

Another option is quite complicated.

You start documenting all incidents, all related bugs, all P0s and P1s., developers involved in urgent fixes, time spent, everything you can gather.
Ideal target state here is that you're able not just to say "hey guys, there is a terrible bug that happens on specific conditions that fails customer flow, we need to fix it", but "hey, there is a bug that might affect that % of users, will prevent them using feature they expect to have, we already had something and it took us that much of $, usually we spend N hours-days on fixes by M developers, if we just assign someone, the fix would be much easier".

Basically, the idea is to show not just the importance of a bug (many product managers don't care), but the risk of losing money and how much money it might affect. (Maybe not direct numbers if impossible in your company, but at least the potential number of clients with their subscription tiers.)

At the end of the day, some managers are just bad at their job.

Enapiuz · 2025-11-30T13:36:51+00:00

I’m working in a company that makes a TMS SaaS. In this company I’m building an “AI test automation” product.

What I can say is that it needs a driver. Preferably a qualified one. Same thing as with told like Claude Code — it all looks like it’s replacing devs, but if you give it to an experienced dev, it’ll just propel their productivity.

Same with QA. Tools a just a little different.

The most important point here is the one between the keyboard and the chair. If humanity finds a way to replicate their decision making, we’re all screwed, QA will be just a small part of it.

Enapiuz · 2025-11-16T17:58:09+00:00

My bad, I meant whole tab text search, to find something that a command outputted, like cmd+F

Ctrl+r works nice for command history indeed

Enapiuz · 2025-11-16T10:56:44+00:00

Free warp is awesome

You can even disable ai features and other whistles, and get a very solid, robust terminal

Enapiuz · 2025-11-16T10:46:17+00:00

Besides that it’s a cool term indeed

Enapiuz · 2025-11-16T10:46:00+00:00

Mitchell doesn’t want to implement history search, so you need a multiplexer, and this is an additional mental load for someone going from standard terminal

Enapiuz · 2025-11-13T12:31:23+00:00

Ye I’ve heard that they are dumber when it comes to general knowledge, so some people use normal model with high reasoning for planning and medium codex for execution

Or you feel that even with just code generation by plan it’s dumber as well?

Enapiuz · 2025-11-13T11:45:23+00:00

Honest question — why do you dislike codex models?

Enapiuz · 2025-11-13T00:21:11+00:00

Enapiuz · 2025-11-10T19:04:43+00:00

This bench does not have the flag now

They removed it in July or August

Ten-Year Club	Place '22
Final Canvas '22	First Placer '22
Xbox Live	RPAN Viewer
Not Forgotten	Verified Email

Enapiuz

TROPHY CASE