948
Vibe coding in a nutshell (europe.pub)
submitted 1 year ago* (last edited 1 year ago) by to c/programmer_humor@programming.dev
43 comments fedilink hide all child comments
 

Disclaimer: these tweets aren't real.

you are viewing a single comment's thread
view the rest of the comments
[–] 9 points 1 year ago (1 child)

I’ve been programming for over half my life now, I actually like vibe coding with Claude these days.

It basically gets me through the hump of “ugh this task is going to be annoying as fuck to do” which is where I personally lose most of my efficiency (I have a lot of difficulty forcing myself to do something I don’t want to).

It’s like when I had interns and I’d give them tasks. Describe the work, scope it, add some guard rails to keep it directionally okay, and send it off to get reviewed later. And that works great with modern agents.

I will say vibe coding is damn good at debugging, way better than I am, so I use it for that a lot now.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago (3 children)

    I've been a Jr coming up to two years. When working on tasks I have a rough idea of what I want to achieve and some steps on the way there, but don't know how to actually implement it. I've found using copilot useful to fill in some of the gaps and give me ideas and direction.

    I'm concerned that there are skills I am missing out on developing, but at the same time if AI is being pushed so heavily is it not something I should lean into to be better equipped in working with it?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 3 points 1 year ago

    I used to have a program that would search docs and I'd read stack overflow all the time. Back then it was RTFM or GTFO, so stack overflow meant I wasn't learning right.

    I think you'll be fine. Sometimes it's good to read docs, sometimes it's good to just see how things work in practice and up to AI that last part was hard to come by.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 1 year ago (1 child)

    I have a rough idea of what I want to achieve and some steps on the way there, but don’t know how to actually implement it.

    That is literally what the job is. If you can't do that then you aren't an engineer.

    I’m concerned that there are skills I am missing out on developing, but at the same time if AI is being pushed so heavily is it not something I should lean into to be better equipped in working with it?

    I'll tell you what I told my nephew: Yes, everyone is going to use AI to one degree or another. So why would I hire you over anyone else? Or, more pointedly, why would I hire someone at all?

    Getting to that interview gets harder and harder every year (every month, really). But engineers (and even many managers) can immediately tell someone who knows their shit versus someone who "vibe codes" all the "hard parts".

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago (1 child)

    why would I hire someone at all?

    AI doesn't get everything right, and you need someone capable of validating that and pivoting it in the right direction. But also AI cannot currently do everything, so you need someone to fill those areas. Where I work there is a push to engage with AI more, probably to train it.

    So why would I hire you over anyone else?

    This is like any other job really, people aren't hired based purely on their skillset, but other factors too such as their capability to learn, their personality, will they mesh well with the existing team, have they got drive to make things better, do they have soft skills to position themselves to become better, is the person adaptable - are they able to use new technology to their advantage or are they stubborn and stuck in their old ways?

    I want to be in a position to know and understand all the fundamentals, but is the bar for what is considered fundamental shifting? Once upon a time those who were writing low level code would have said what they do are the fundamentals, but as time went on we got new levels of coding and so knowing how to write low level code is no longer a required skill.

    Apologies if I've misunderstood what you're trying to say. But thanks for responding, these kinds of discussions are helpful.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    But also AI cannot currently do everything, so you need someone to fill those areas.

    And who is going to be able to fill those gaps? Probably not the person who "knows what I want to achieve but (...) don't know how to actually implement it".

    Which ties in to

    their capability to learn, their personality, will they mesh well with the existing team, have they got drive to make things better, do they have soft skills to position themselves to become better, is the person adaptable

    is the bar for what is considered fundamental shifting?

    If the bar is "I know how to ask a magic box to do my job for me" then there is genuinely no need for previous training and experience and a company won't be hiring engineers or spreadsheet gandalfs or marketing experts. They'll hire the cheapest "prompt engineer" they can, underpay them, and then replace them the moment they ask for a cost of living increase.

    And... the companies considering that really aren't the ones with any longevity. Yes, yes, any port in a storm. But they will RAPIDLY run into that wall and have no way to move past it. Whether that is getting the senior engineer in cargo shorts to do it or curating training data to improve the model.

    but as time went on we got new levels of coding and so knowing how to write low level code is no longer a required skill.

    And that is another barrier that MANY companies have run into.

    The average coder? Yeah, they don't need to understand how to optimize a loop. But when there are forty tools on the market that all just call pytorch? The one company that knows how to optimize a critical path function suddenly looks REALLY good with their 10% performance (and thus power) savings.

    Again, these tools are incredibly powerful and I regularly use chatgpt et al to generate a first draft of a utility script. And I've been using editor plugins for... sweet Eothas over two decades now, to generate docstring stubs and even a lot of unit tests. And people SHOULD know how and when to use these tools.

    But you also have to consider what you can get out of it. "AI" generated documentation is pretty much worthless outside of checking off a box that you have documented every function in the code. Your LLM won't understand what that function was trying to achieve or why "it is wrong but that is because this library is wrong" and so forth. Any documentation that is actually meant to be referenced still needs a proper pass from whoever drew the short straw in Engineering.

    Same with testing. AI can generate tautologies. AI won't stress test your code because it doesn't know what you think that code might do in the future. By all means, generate the boilerplate, but you are still going to be the one who has to go in and add that really weird corner case that TOTALLY didn't break prod lats month.

    And... you know who historically did those tasks? Interns and junior engineers. The same ones who are adamant that their entire job can be done by chatgpt and lamenting that they don't know how to move from idea to implementation. And guess how you learn how to do that?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago (1 child)

    Thanks, it's interesting to read your thoughts on this.

    If you were a Jr entering the job market now, and have management encouraging vibe coding because they want quick results, how would you go about getting the experience and building the right skillset?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago

    There are two layers to that.

    The first is how to develop skills. And you do that the exact same way everyone before you did it: you actually do the work. Calculators are awesome but you still learn how to do long division and the like because it gives you insight into how to approximate things. Same with sims/solvers versus actually solving PDEs.

    The other is... if your boss wants you to feed everything into an LLM then you won't have a job much longer. So you can either look for a new one or work toward more advanced tickets/tasks. Make it clear that LLMs have limitations and that some stuff will need a proper coder and that YOU are that proper coder.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 1 year ago

    Ten years and counting here, fuck if anyone knows at this point. My personal (maybe a bit cynical) take is that it really doesn't matter as the amount of coding skill you use maxes out in the first few years of your career (for 90% of us anyhow), after that cat herding skills and pragmatic system architecture is what's important. It becomes more important to know what not to do rather than the opposite.

    So it doesn't really matter how fast you are at leetcode if you can navigate the particular brand of spaghetti your workplace is cooking, plus points if you are able and willing to grok new kinds so you can hop jobs because raises are so last century.

  • permalink
  • fedilink
  • source
  • parent