HackerTrans
TopNewTrendsCommentsPastAskShowJobs

Datahenge

no profile record

Submissions

Show HN: dbconform – stateless schema drift repair, no migration history

3 points·by Datahenge·25 दिन पहले·0 comments

comments

Datahenge
·पिछला माह·discuss
I've thought a lot about this over the years, but especially in the past 12 months.

The solution greatly depends on where you live.

I live in the United States. The problem here is that, legally, we only have "enterprise bargaining" — the union represents workers at a specific employer. So there could be a Tech Union that can represent Google workers, Amazon workers, or Microsoft workers. That's all covered by the National Labor Relations Act.

But there cannot exist a universal union to protect tech workers in general. That's "sectoral bargaining" (where one agreement covers an entire industry). There are approximately 5 European nations where that exists strongly for IT/technology.

USA tech folks could certainly form some kind of organization that tries to be influential. But it wouldn't have any legal rights. It couldn't negotiate with employers, couldn't implement strikes, represent employees at court, that sort of thing.

Just one more reason why I'm frequently jealous of European workers.
Datahenge
·पिछला माह·discuss
I'm handling this through a combination of Tests and documentation-driven development ("scribe coding" instead of vibe coding).

* If it's important, it gets written into documentation somewhere. Functional requirements, technical requirements, ADRs, Lessons Learned, etc.

* Code comments and docstrings point back to documentation. Especially for bug fixes.

* Finally, bug fixes usually get new Unit Tests. The tests make sure if the bug resurfaces, it gets caught immediately.

I absolutely believe what you're describing: I've seen heard other people talk about this. I just don't experience it myself (I'd like to hope because of the extra steps I'm taking)
Datahenge
·पिछला माह·discuss
Four months also. The struggle is real.
Datahenge
·पिछला माह·discuss
I don't feel AI assisted coding has removed the need for framework adoption.

Instead, I feel it's enabled us to more freely choose what frontend framework(s) we want to implement. Based on the problem we're trying to solve.

There's only so much that 1 human can become an expert at. Before AI assistants, we had to make some choices: I cannot become an expert at React, Vue, Angular, Svelte, SolidJS, Quik, and Astro/Alpine/HTMX simultaneously. Too much. So I must pick one or two that I think are best-suited for me. Learn them deeply. Then apply them everywhere.

With AI assistants, there's more freedom. I'm not an expert at Svelte. But if there's a web problem I feel Svelte would solve best? Then that's what I can use. If I really need React's virtual DOM? Then go that direction. If what I'm building is so simple that a static website with basic HTML and JS and a CSS framework is sufficient? I can go that direction.

Granted, there are absolutely risks for relying on AI assistants to write code you don't comprehend or understand. There are times I'm okay with it. And times I am not.

But as for your question, am I less-likely to use frontend frameworks now? No, I'm actually using them more than I did previously. I'm just being choosier about what I truly need, versus what's overkill.
Datahenge
·3 माह पहले·discuss
I love the use of color and the retro-style UI. Your INSTRUCTIONS.md was comprehensive.

Appears to be CPU-heavy sometimes in the browser (spiked one of my CPUs to 100%), so could be an opportunity for optimization later.

I've often wanted to show my clients how risky their brand-new VPS is without proper firewall configuration. Your Knock-Knock tool would be a great way of helping them visualize that.

Very nice app; great job!