3 ms·

What’s wrong with the finance team (vibe) coding a janky prototype for planning?

by highfrequency 5mo ago

JohnMakin 5mo ago
prototypes/mvp's often become the production version
- sandeepkd 5mo ago
  This seems to be the default path which is encouraged/suggested lately, only happy path until you acquire customers
  - JohnMakin 5mo ago
    I think it’s fairly normal at least in my career - rush to ship something, lots of “we’ll polish this later,” two years go by, get called into vp/cto/whoever’s office when the debt comes calling like “what the fuck why is this like this???” and I have to say “that ‘later’ we decided is now I guess”
    - sandeepkd 5mo ago
      The script I have fairly seen being played is where the one doing MVP gets rewarded and moves on with a promotion. The weight of completing and stabilizing the MVP falls on some one else who is not vocal enough in terms of influence. Ironically the flashy MVP does not includes monitoring, logging, security, edge-cases, CI-CD, DR, scaling which is why vibe coding is getting so popular and everyone seems to be under the impression that engineers are not needed anymore.
- auspiv 5mo ago
  And their spreadsheets don't?
  - JohnMakin 5mo ago
    [dead]
- KellyCriterion 5mo ago
  ...and are often still in place when the "magic guy who built it" left long time ago...
redsocksfan45 5mo ago
[dead]
thisisit 5mo ago
Because the next email is going to be "we demoed the app to our CEO and he loved it and he wants it in production". I have never seen the team back down from their ideas. And also, I have been in similar sounding scenarios multiple times. They talk big when everything is going smoothly and nothing is on the line. The day shit hits the fan, they will furiously message me on Teams and insist that I support them in finding out issues. So far it has been about mostly about shitty design choices. This is at whole new level. They want to vibe code an app which will be used to plan and guide company's direction for the next year.

What’s wrong with the finance team (vibe) coding a janky prototype for planning?

JohnMakin 5mo ago

prototypes/mvp's often become the production version

sandeepkd 5mo ago
This seems to be the default path which is encouraged/suggested lately, only happy path until you acquire customers
- JohnMakin 5mo ago
  I think it’s fairly normal at least in my career - rush to ship something, lots of “we’ll polish this later,” two years go by, get called into vp/cto/whoever’s office when the debt comes calling like “what the fuck why is this like this???” and I have to say “that ‘later’ we decided is now I guess”
  - sandeepkd 5mo ago
    The script I have fairly seen being played is where the one doing MVP gets rewarded and moves on with a promotion. The weight of completing and stabilizing the MVP falls on some one else who is not vocal enough in terms of influence. Ironically the flashy MVP does not includes monitoring, logging, security, edge-cases, CI-CD, DR, scaling which is why vibe coding is getting so popular and everyone seems to be under the impression that engineers are not needed anymore.
auspiv 5mo ago
And their spreadsheets don't?
- JohnMakin 5mo ago
  [dead]
KellyCriterion 5mo ago
...and are often still in place when the "magic guy who built it" left long time ago...

redsocksfan45 5mo ago

[dead]

thisisit 5mo ago

Because the next email is going to be "we demoed the app to our CEO and he loved it and he wants it in production". I have never seen the team back down from their ideas. And also, I have been in similar sounding scenarios multiple times. They talk big when everything is going smoothly and nothing is on the line. The day shit hits the fan, they will furiously message me on Teams and insist that I support them in finding out issues. So far it has been about mostly about shitty design choices. This is at whole new level. They want to vibe code an app which will be used to plan and guide company's direction for the next year.