Technology

59578 readers

3420 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

884

AI-Generated Code is Causing Outages and Security Issues in Businesses (www.techrepublic.com)

submitted 2 months ago by RmDebArc_5@sh.itjust.works to c/technology@lemmy.world

179 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] henfredemars@infosec.pub 3 points 2 months ago (1 children)

You know you’re Sr. when it doesn’t even bother you anymore. It amuses you.

[–] sugar_in_your_tea@sh.itjust.works 7 points 2 months ago* (last edited 2 months ago) (1 children)

My boss comes to me saying we must finish feature X by date Y or else.

Me:

We're literally in this mess right now. Basically, product team set out some goals for the year, and we pointed out early on that feature X is going to have a ton of issues. Halfway through the year, my boss (the director) tells the product team we need to start feature X immediately or it's going to have risk of missing the EOY goals. Product team gets all the pre-reqs finished about 2 months before EOY (our "year" ends this month), and surprise surprise, there are tons of issues and we're likely to miss the deadline. Product team is freaking out about their bonuses, whereas I'm chuckling in the corner pointing to the multiple times we told them it's going to have issues.

There's a reason you hire senior engineers, and it's not to wave a magic wand and fix all the issues at the last minute, it's to tell you your expectations are unreasonable. The process should be:

product team lists requirements
some software dev gives a reasonable estimate
senior dev chuckles and doubles it
director chuckles and adds 25% or so to the estimate
if product team doesn't like the estimate, return to 1
we release somewhere between 3 and 4

If you skip some of those steps, you're going to have a bad time.

[–] henfredemars@infosec.pub 3 points 2 months ago* (last edited 2 months ago) (1 children)

In my experience, the job of a sr. revolves around expectations. Expectations of yourself, of the customer, of your bosses, of your juniors and individual contributors working with you or that you're tasking. Managing the expectations and understanding how these things go to protect your guys and gals and trying to save management from poking out their own eyes.

And you may actually have time to do some programming.

[–] sugar_in_your_tea@sh.itjust.works 4 points 2 months ago (1 children)

Yup. I actually only take a 50% workload because half of my time is spent in random meetings telling people no, or giving obscenely high estimates that essentially amount to "no." The other half of my time is fixing problems from when they didn't listen when I said "no."

Such is life I guess. But occasionally, I get to work on something new. And honestly, that's fine, I've long since stopped caring about my name showing up on things.

[–] henfredemars@infosec.pub 2 points 2 months ago

Not all heroes wear capes. You're saving their butts, and they don't know it.