830
Vibe coders don't know shit! (europe.pub)
submitted 1 week ago by to c/programmer_humor@programming.dev
156 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 9 points 1 week ago* (3 children)

My workflow is :

Step one: write down a bunch of nonsense, massive block comments of old code in case the new code is worse, and cludges in one massive file.

Step two: rewrite the whole thing: breaking it down into classes so it's readable and maintainable ...

Step 3: come back later and wonder where the hell anything is. Go to step 1

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 5 points 1 week ago (2 children)

    Step 4: realize the shit was simpler and better without the classes.

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

    I do a lot of fairly complex data processing that benefits from any abstraction I can get.

    E.g. "Take these 50,000 data points, identify and apply the best set of filters for each sections, then produce the best curve fit for each section." It's massively complex and (hilariously) produces multiple equally massive data sets while working -- acceleration and velocity plots, for example.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 1 week ago

    In the early 90s I coded up a fairly massive data analysis suite entirely in C.

    Around 1997 I translated it to C++ - the resulting data analysis ran at 1/2 the speed of the C code, but was 300% faster to modify, expand and maintain. And processor speeds were doubling every 9 months anyway.

  • permalink
  • fedilink
  • source
  • parent