My company is increasingly pushing prompt engineering as the single way we "should" be coding. The CEO & CTO are both obsessed with it and promote things like "delete entire unit test file & have claude generate a new one" rather than manually address test failures.
I'm a 'senior engineer' with ~5 years of industry experience and am considering moving on from this company because I don't want
1. Be pushed into a workflow that will cause my technical growth to stall or degrade 2. Be overseeing a bunch of AI-generated spaghetti 2-3 years from now
Feel free to address my specific situation but I'm interested in more general opinions.
Comments URL: https://news.ycombinator.com/item?id=44468375
Points: 10
# Comments: 9
Inicia sesión para agregar comentarios
Otros mensajes en este grupo.
Article URL: https://www.reddit.com/r/AO3/s/67nQid89MW
Comments URL: https://
Article URL: https://www.tinytransistors.net/2024/08/25/adxl345/
Article URL: https://privateisland.tech/betsy
Comments URL: https://news.ycombinator.c
Article URL: https://www.datagubbe.se/amix/
Comments URL: https://news.ycombinator.com/i
I built tinykv because I kept reaching for simple persistent storage in Rust projects but found existing solutions either too complex (sled) or unmaintained (pickledb).
tinykv focuses on simplic
