Farid Yusof's Blog

It started with a message from the DBA team. Our shared Postgres host was carrying 79 idle connections from a single service, ours, and they were capping our role at 20 until we sorted it out. By the time I read it, things were already worse: a database migration wouldn’t even start. FATAL: too many connections for role. Our own app pods had eaten the entire allowance, leaving nothing for the migration that was supposed to fix things. We were locked out of our own database by ourselves.

Hey! I just want to share my personal opinion on AI, vibe coding, and its effect on software engineers. A friend from a UK company asked me:

I don’t know in which direction it’s going (the AI). But overall what do you think about the software industry moving forward?

First, I wasn’t sure whether he was asking about the “industry” or “software engineers.” And honestly, I don’t think AI would hurt the “industry” — as a matter of fact, it’s actually empowering it.

Early Feedback Loop

At most places I’ve worked before, we were conditioned to complete tasks entirely - PR, deploy to stage or testing environment - and only then would we get feedback from the “Product Team” / “QA” team.