Joined devRant on 7/12/2018
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
After what amount of time after leaving your previous job, where you were deeply involved with client side infrastructure and deployment, would you expect the credentials to stop working / be changed ?
I should state that the credentials are not service accounts, but also not distinct for every dev / devops.
I might also add that the clients involved are courier services, service providers and ... Oh yeah ... A financial institution
Also everyone is based in the EU, so GDPR and all ...6
rant && !rant
so my company just relocated to another part of the city.
it took about 2-3 months of searching for a space till the management found a suitable place. then about one more month for settling on the details (price, when we move, etc). then another month of just waiting for the space to be ready ...
the actual move took 1 day ... just one day ...
so the new place
- is better placed (for me at least)
- has lots of nice pubs / restaurants around for lunch or just relaxing after work
- has great views from every office
- lots of extra space for everyone
- ok people (so far) working at the other companies in the same space
- everyone seems so much more relaxed and easygoing and happy at the new place
- the ac is still not working (32 degrees Celsius outside, and our office is facing the sun almost all day)
- for the first days we were lacking blinds at the windows
- office was full of little stinky bugs and they still keep showing up when we open up the windows
So, overall pretty great ... so (rant part??) WHY DID IT TAKE SO LONG TO MOVE HERE ??? (both before it was decided to move, about 4 years at the old place, and after)
also, relating to the topic of the week ... nothing code related was learned, much was gained, and a life lesson was obtained: if you don't like something, just change it as soon as you can
Mid - senior dev (L from now on) comes in on a project to help out. Starts working on creating a dashboard for the application. Work is progressing, new ideas come in, team lead (TL) is ok with everything, business analyst (BA) is also ok. The dashboard even gets thru testing (T), everything is great. In comes (A), a (probably bored) junior backend dev.
A little backstory about (A):
- seated right next to (TL)
- most discussion about every developed feature take place at (TL)-s desk, right next to (A)
- (A) was also present when discussions took place between (TL) and (BA) about dashboard
- (A) could have easily heard any number of the other team members (over 15) talk about the dashboard
Well, (A) comes into the picture ... and the dashboard (first page after login, big shiny new thing, working just fine ...) breaks. Well, breaks is a little understated. Disappears would be more exact. Cause (A) commented it out. NOT deleted from code. JUST commented out the code.
But why you ask? Because he didn't know what it did and why it was there.
No asking around, no looking up history in repository, no looking up tasks that might be related to that ... no nothing.
He's a backend dev, there's something new and unknown in the backend, the new thing has to go.
(L) didn't scream, (TL) didn't scream, (BA) didn't scream, (T) didn't scream ...
I almost screamed. This didn't happen to me, or (A) would have screamed!3