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
Search - "burning bridges"
Never have I been so furious whilst at work as yesterday, I am still super pissed about going back today but knowing it's only for another few weeks makes it baerable.
I have been the lead developer on a project for the last 3~ months and our CTO is the product owner. So every now and then he decides to just work on a feature he is interested in- fair enough I guess. But everything I have to go and clean up his horrendous code. Everything he writes is an absolute joke, it's like he is constantly in Hackathon mode "let's just copy and paste some code here, hardcoded shit there and forgot about separation of code- it all goes in 1 file".
So yesterday he added a application to the project and instead of reusing a shared data access layer he added an entirely new ORM, which is near identical to the existing ORM in use, for this one application.
Being anal about these things, the first thing I did was delete his shit and simply reference the shared library then refactor a little code to make it compatible.
WELL!! I certainly hit a nerve, he went crazy spamming messages on Slack demanding I revert as it broke ONE SINGLE QUERY that he hadn't checked in (he does 1 huge commit for 10 of everyone else's). I stuck to my principals and explained both ORM's are similar and that we only needed one, the second would cause a fragmented codebase for no benefit whatsoever.
The lead Dev was then forced to come and convince me to revert, again I refused and called out the shit quality of their code. The battle raged on via the public slack group and I could hear colleagues enjoying the heated debate, new users even started joining the group just to get in on mine and the cto's difference of opinion.
I even offered to fix his code for him if he were to commit it, obviously that was not taken well ;).
Once I finally got a luck at the cluster fuck of shit he had written it took me around 5 minutes to fix and I ever improved performance. Regardless he was having none of it. Still the demands to revert continued.
I left the office steaming after long discussions with the lead Dev caught in the middle.
Fortunately my day was salvages with a positive technical discussion that evening at a company with whome I had a job offer from.
I really hate burning bridges and have never left a company under bad terms but this dictator is making me look forward to breaking the news today I will be gone in 4 weeks.4
Many years ago I had a job as web developer at a small promotions company. The owners loved micromanaging their 7 employees, down to the minute. Work started at 9am, if you were even 1 minute late, you were deducted 1 point. (Even if the weather was bad) Once you were at 10 points, you were disciplined by being given an unpaid vacation day. (Thanks for the day off!). At 12 points, you were fired.
It only took me about 8 months before getting my day off. Somehow I was able to time it perfectly to a job interview at a large company.
Luckily I got the job, and purposely was late the next two days so when they told me I was fired I could tell them I already got a new job (thanks to their 10 pt rule) and I'm out anyway.
At the new job, I'd often drive home and nap on my lunch hour. No one would notice if I came back an hour and a half later.
The owners of the 1st company divorced a few years ago. The husband and I have actually kept in contact over the years. He's a cool guy when you don't work for him. He invited me to a Green Day concert over the summer. Probably makes the above story a little less cool, but at the moment, I was burning bridges!1
I've had a client for 3 months now and they still haven't paid ($100 just for the site) and are surprised at the monthly cost (they wanted site hosting and maintenance which comes out to $75/month) and I want to fire them without burning bridges since the main person is a friend.15
I've found a better job offer; shorter distance, but salery is low, not that is a big issue tbh.
What is the right approach to quit your job?
Or to say, nicest way to avoid burning any bridges.9
Now that this drama shite is calming down, here's my tuppence on how connections management should be implemented.
We really need something that is in between blocking and doing nothing. This, in my opinion, is temporary silencing. Having the ability to mute a person or rant, or notifications altogether, for a set period of time would be very useful when a situation needs de-escalating. As this social network (let's not beat around the bush, this is a social network) grows in size, this will be a handy tool for calming storms without burning bridges permanently.
To sum up, I think it would be a good idea to have three available options for notification muting:
- mute notifications/this person/rant for 24 hours
- mute notifications/this person/rant for 7 days
- mute this person/rant forever
As for implementation, I'd wrap up the call to the user's notification assembly like so:
And use a date field in the DB to handle timescales.
Also, I suggest the addition of this tag specifically for suggestions, just so we're not all using different tags