4 ms·

Junior developer probably opened a Jira ticket, saw a UI of a permission dialog, and did exactly that task with nobody senior enough to know better. That's how

by benoau 2y ago

Junior developer probably opened a Jira ticket, saw a UI of a permission dialog, and did exactly that task with nobody senior enough to know better. That's how you reproduce the bugs that were in-fashion 15 - 20 years ago in my experience!

bugtodiffer 2y ago
Seems like a solid development cycle. Junior tries something -> hit production I do not see multiple issues with this.
- Ntrails 2y ago
  Hey, it worked on my machine
- intelVISA 2y ago
  9 out of 10 PMs love this one hack to boost velocity they were probably thinking what a 10x engineer they'd found to be so rapid at delivery...
  - XenophileJKO 2y ago
    This is so true. I've seen this so many times. The darling of product, who can deliver so fast. They leave a trail of smoking rubble and half working features behind them.
    - blitzar 2y ago
      Why can't you be more like darling of product over there. What do you even do around here; all you seem to ever do is take darling of products code and make a few changes (which I don't understand) and committing it as your own work. It appears you are either trying to take credit for darling of product or are sabotaging their amazing 10x work.
      - dfedbeef 2y ago
        Are you my manager
tuyiown 2y ago
There two new front end guys in the team, understaffed backend, but manageable, nothing as dramatic, but I constantly have to remind the benefits of doing as much things as possible in the backend and keep the logics high level on the front is aggravating.
_xiaz 2y ago
Also no review or planning anywhere in that process. I'm semi-confident that if a Junior were to talk to another Junior before starting about things to look out for, and then the code was reviewed by say a third Junior, they would not have this bug. Call me naive, but I don't think Juniors are as oblivious as they are made out to be
- _xiaz 2y ago
  I should add this works best if you hire with some diversity, such as one Junior with a preference for security topics. If you go up to the counter and yell "10 React devs please", don't be surprised
  - rfc2324 2y ago
    As a long time engineering manager, I have significantly benifited from this: leveling me up in WCAG/ADA, strcmp timing attacks, performance timing. Many managers start younger than we maybe should, and the burnout that I had in my early years pulled me out of my passion to learn more about comp sci. It was the random enthusiasm of younger folk that, in those times, was my exposure to topics I hadn't dived in to yet. I have witnessed hiring, listening, and supporting early-career enthusiasm has significantly improved every startup I've had the joy to be a part of.

by benoau 2y ago

bugtodiffer 2y ago

Seems like a solid development cycle. Junior tries something -> hit production I do not see multiple issues with this.

Ntrails 2y ago
Hey, it worked on my machine
intelVISA 2y ago
9 out of 10 PMs love this one hack to boost velocity they were probably thinking what a 10x engineer they'd found to be so rapid at delivery...
- XenophileJKO 2y ago
  This is so true. I've seen this so many times. The darling of product, who can deliver so fast. They leave a trail of smoking rubble and half working features behind them.
  - blitzar 2y ago
    Why can't you be more like darling of product over there. What do you even do around here; all you seem to ever do is take darling of products code and make a few changes (which I don't understand) and committing it as your own work. It appears you are either trying to take credit for darling of product or are sabotaging their amazing 10x work.
    - dfedbeef 2y ago
      Are you my manager

tuyiown 2y ago

There two new front end guys in the team, understaffed backend, but manageable, nothing as dramatic, but I constantly have to remind the benefits of doing as much things as possible in the backend and keep the logics high level on the front is aggravating.

_xiaz 2y ago

Also no review or planning anywhere in that process. I'm semi-confident that if a Junior were to talk to another Junior before starting about things to look out for, and then the code was reviewed by say a third Junior, they would not have this bug. Call me naive, but I don't think Juniors are as oblivious as they are made out to be

_xiaz 2y ago
I should add this works best if you hire with some diversity, such as one Junior with a preference for security topics. If you go up to the counter and yell "10 React devs please", don't be surprised
- rfc2324 2y ago
  As a long time engineering manager, I have significantly benifited from this: leveling me up in WCAG/ADA, strcmp timing attacks, performance timing. Many managers start younger than we maybe should, and the burnout that I had in my early years pulled me out of my passion to learn more about comp sci. It was the random enthusiasm of younger folk that, in those times, was my exposure to topics I hadn't dived in to yet. I have witnessed hiring, listening, and supporting early-career enthusiasm has significantly improved every startup I've had the joy to be a part of.