ativzzz

I use herdr a lot

If anything, with things like libghostty, I expect more desktop apps with built in terminals. Instead of me having to go to the browser for github, jira, etc, have it all in one app along with whatever terminal tooling you're using

Or more likely, based on what the other engineers I work with are doing, we will all vibecode our own tooling that fit our individual workflow

It looks like they are specifically optimizing for incidents/reverts and shipping faster

> The goal hasn't changed: less human time per change, and no more reverts than before.

Is this Goodhart's law in action? Less reverts and less incidents was measured and became the target. Is this then still a good measure? I guess Revenue is a more direct measure, but we don't have access to that one.

> once the 5-Year mark passes

What juniors are sticking around at 5 years? The market reality is they can likely 1.5x-2x their pay by switching jobs, unless they started at FAANG or some other ultra high paying co

My mom, who stayed at home, buys clothes for my dad, who works. I don't think I've ever seen him buy clothes for himself other than shoes and outdoor work equipment.

By asking this, you're effectively the shallow professional with more money that hugs the festival to death, so of course you wouldn't know the cool ones that are mostly art community driven

Agreed - I know it's poor security but damn does it work so well

I'm ok with the risk because I typically am pretty explicit about telling the agent what to do - I don't do the loops like "Do this until X" where the agent can make up its own workflow

When i tell it to add features, it doesn't try to do crazy things like installing packages or making up new paradigms - I usually tell it to do those things when I need to

Maybe this is security cope but at this point you'll have to pry unrestricted yolo mode from my cold dead hands. Maybe I'll change my mind when I pwn myself accidentally

I have a tough time with computer security because it's generally inconvenient and results in a worse developer and user experience

I can totally see a world where a small team of PM + engineers can recreate internal business tools, you need to run the numbers to see if paying these people is significant cost savings relative to paying for the tool

The reality for most enterprise apps is that customers are using a small fraction of all available functionality and are paying for much more than the featureset they are using

So if a business can identify this featureset and give a team empowerment to build and maintain this featureset, it could work

Running a business is an optimization problem though - if you are spending resources on internal tooling, and people are more expensive than money, are you taking away from those resources being spent on things that drive revenue?

Plus, this falls apart when you start dealing with anything involving compliance. Part of paying for an app is you offload the risk of maintaining compliance to that app

Once you need to get legal/compliance/accounting involved, it's unlikely to be worth the cost anymore, so it depends on the data being processed by the SaaS

> How do you structure a brand new project? Scaffolding, git init/ignore? Repos? Initial commit strategies?

Don't overthink it. Use whatever bootstrapping tools your project framework comes with (rails app? use `rails new`)

> How do you keep stuff out of the context window that you don't want in it?

Don't overthink it. Just use one chat per general topic. New topic -> new chat. Save anything relevant to the project that the agent doesn't pick up in new chats in AGENTS.md

> How do you "layer" your work so it's much more about the context and integrity of the structure

Save project specific needs/requirements in AGENTS.md or docs/ or skills or whatever and tinker until it works

> Do you switch models

Nowadays just for code review. Recently gpt5.5 has felt very good for general dev

> What other tooling do you have alongside basic agents/environments?

Neovim for code browsing (don't write much code anymore but the code editor is still useful for reading code) and various plugins/tools i've built up over the years

Honestly, there's no blanket solution. The best engineers I've worked with all have different tools custom to their workflows

> know I'm hitting a ceiling. My workflow is naive and nonpro, a lot of tinkering and bashing my way through code generation, context drift, manual fixes, etc.

Hit a ceiling? Fix it. Typically it's

- do work

- notice something annoying about your workflow

- fix it systemically - research different solutions - sometimes it's writing a small script (agents are great for this), sometimes it's finding a new tool, sometimes it's overhauling your entire system, it just depends

- do work

repeat...

there's really no one stop solution for a perfect workflow

Everyone is QA at a startup. I hope y'all are using your own product regularly right? You should have a nice simple way to raise these issues, maybe a slack channel or something with a convenient way to turn a screenshot into an item in your todo/work system if you have one. Encourage product ownership.

Alternatively, if you don't really care about the product, everyone is also customer support at a startup - you should be quickly be able to solve regressions that customers raise. I hope that at least you are talking to your customers and are very responsive to them at a startup.

Alternatively, consider the person is disabled and is physically incapable of driving.

I currently am mid 30s and 10 years into my career. I have no interest in joining a union right now, simply because I am confident in my skill and my ability to increase my earnings and career progression without being a member of a union.

Maybe when I hit peak earnings and no longer get a sizeable raise when hopping jobs every 3-4 years and the personal progression is no longer satisfying, I'd be interested in a union.

Notably, I have never been laid off and I have enough savings/investments to keep my family fed and housed for years if I am without work.

When I stop caring about career progression, about learning and growing, and just want to receive a paycheck for minimal effort until I can't be bothered showing up at work anymore, I'd be more than happy to join a union to ride it out. Until then, for purely selfish and individualistic reasons, I'd rather be solo.

Likely what would happen is by the time I want to join a union, it's no longer feasible for one reason or another, but I'll have enough savings by then (or we're all screwed anyway) to be fine.

I think this is company culture. You're asking how to make your engineers give enough of a damn about their output to spend the extra time understanding it.

Did they do this before AI? Does the company really, truly care about software quality or are they just trying to ship features?

Things like

- in depth code reviews

- encouraging sharing knowledge and helping others

- dedicating time to address technical debt

- giving engineers freedom to explore technologies and solutions

- following best practices for software dev

- hiring the right people

This is one of those things you can't enforce, but your leadership can encourage it by setting examples. If your company does not care about understanding the software by carving out time and explicitly encouraging it, then employees won't either.

I've found two jobs from that thread, and have been offered a third I turned down. I usually just ctrl-f for the tech I use and apply if I see something interesting that matches my skillset. It's quite targeted. I think I have like a 50% success rate with applying via HN.

Why not a childfree tax instead? It's not going to be popular, but for societies with low birth rates - contribute to the next generation either via human bodies or via cash. But I doubt society's ability to put this tax towards the next generation.

Just have claude (or gpt maybe) do an architecture review and request a multi-phase refactoring plan. This is probably better to do incrementally as you notice the balls of mud forming but it might not be too late. Either way, if it does something you don't like, `git checkout` and start over