I’d even go as far as saying that you should reject anyone applying for your startup if they claim to have vibe coding experience.
I find it hard to imagine why you would even put that on a resume. Isn’t it like saying “I DON’T KNOW WHAT I’M DOING”? But then I’m old.
Silicon Valley is already jumping on the trend and hiring Vibe Coders.
What the actual fuck are they on? Is this satire?
wtf
Tripled our ARR
I mean going from $100 to $300 is technically tripling. It just doesn’t mean anything
Putting in 12-15 hour days
Ultra hard pass…
I can’t code (well). I was hoping AI could be a kind of auto-didactic teacher for me. Dreams crushed, I’ll have to learn it all the hard way after all. Unfortunately “the hard way” is after I’m already fried from working all day…
Even still I’ve only ever used the term “vibe coding” ironically and I’d never try to use generated code in production.
AI can teach you to code, as long as you don’t switch off and stop using your own brain. Use it as a search engine instead of a teacher, always confirm original sources.
My problem is that I can’t trust it not to hallucinate something that I can’t catch it on. If it tells me something wrong, and I don’t catch it, that might stick and be really hard to unlearn. It’s more like a study guide that’s only semi-reliable, and I don’t like unreliable information.
What exactly are you trying to learn by the way? Web dev or more backend stuff? Systems and infra programming?
There are a lot of guided resources that can take you through learning that don’t involve generating a lot of random text.
That’s probably part of the issue too - no direction. I think I’d enjoy working with databases, so I’ve been thinking about DBA; I just have no idea what the day to day looks like for a database admin and the unknown is scary. I’m quite familiar with HTML already at an intermediate level, but I think I want to stay away from having to write JavaScript for production, so almost definitely not web dev 😅
I worked as a DBA for a while, I got into it by getting into a niche database system (Apache Cassandra) at a startup for a PoC and then the local megacorp was desperately needing someone with that experience.
The day-to-day was mostly these things:
- Organizing and educating outsourced teams in India for routine maintenance tasks, mostly by writing “do this then this” style docs for them
- Act as L3 support when stuff broke - this one was rare, I was once paid a day of overtime because someone messed up a migration, took the whole global system offline, and I had to sit there see stuff come back again when they fixed it
- Write automation for automated deployment into Microsoft Azure, imagine writing Ansible code and Terraform
- Make architecture diagrams and plans and help debug developers’ harebrained attempts at using the database for things that it was not made for, but they wanted it on their CV
It was a very slow job, with nothing to do all December - since there was a code freeze - for example. That said, it’s essential to understand Linux on a deeper level to be a DBA, like one interview question was “you have a 2TB disk with 400 gigs of data on it, yet the OS is complaining that the disk is full, what is the likely issue and how do you debug it”.
Thank you for that write-up! Understanding Linux more deeply isn’t a barrier to me. I’m now quite certain DBA is my next goal - it really does sound like an evolution of what I’ve been doing so far. I’ll look around on Coursera for some certs that might convince my current employer I’m serious about helping manage the database.
Also, since it was offered I’ll take it as a bit of practice:
- fsck
- reserved space (e.g. system files, backups, hidden partition)
- hidden or deleted files that are in use
- incorrect mount
- simultaneous access from multiple mounts (?)
- Permissions (?)
Question mark against things that seem like possible causes, but I’m not sure if they are. Most of these would probably show the space as used rather than free, but did I miss checking anything major that I wouldn’t find with a bit of searching?
You are bringing up good approaches and you would have been hired if you could explain how you would start to troubleshoot some of those issues.
The answer to the problem that this team ran into was that you can actually run out of inodes in a filesystem if you have a very large number of relatively small files, and that might show up as failed writes that can make a program like a DBMS say “the disk is full”.
Regarding getting hired though, I have no idea about the market and pay nowadays especially wherever you are. I hope it’s good for you, it was certainly good for me in the 2010s in Eastern Europe, but I’ve heard it’s shit everywhere these days.