Details
-
AboutSoftware Developer
-
LocationPacific North West
Joined devRant on 10/18/2017
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Yesterday a colleague was debugging some piece of typescript code for memory leaks as chrome and firefox were hanging at a certain page.
Her real brainfuck was that everything seemed to be working fine with edge. Microsoft, somehow, finds a way to fuck with developers. -
Today I felt sorry for my boss.
Story behind it:
My boss always encourages me to do the right thing. One of those right things is to enforce quality gates in our build pipelines which, as many of you know, means that the build fails if certain quality parameters are not met. Now an external vendor team merged the code this past thursday for a large feature that they had been working on and our build failed majestically throwing out the statistics and the offending files and lines of code.
All hell broke loose and there were escalations and what not and people working extra hours and over the weekend to try and get it right. So, I get a call from my boss earlier today to explain to me how important it is to release the feature and how it's going to be very bad if we don't. He was trying to justify his ask which was to lower the quality criteria and let the build pass for this week. Of course the dev in me was furious but then I realized it's not him but the corporate culture. Why would he or anyone would risk losing their jobs over the quality of code?
If you work at a place where IT is a support function of the company's primary business, I understand the moral compromises you guys have to make sometimes to keep the ball rolling. Thank you for your effort to make the world a better place.
So, thank you boss for all your support. I know it's not always up to you to decide on things but keep up the good work.4 -
To the people who empty the coffee pots in the break room without remaking, may you get an extra nasty defect for each time you commit this heinous crime.
-
Someone seems to be running a script. I don’t think this is humanly possible within 2 minutes.
@notroot6 -
You wake up early on Saturday to pee and you have a bunch of alerts in your inbox about failing dependencies in production. But you haven’t gotten any call or text from your boss. What do you do?
Well, I started browsing devRant while waiting for the next scheduled alert hoping my brethren on the other end of the systems resolve it and I wouldn’t have to login.1 -
I recently read that great programmers care more about algorithms than code. I hope I can find more time to devote to learning algorithms than spending it on yet another framework. #springboot.js1
-
I think the worst thing I’ve seen from devs is lacking the curiosity to know how some software library works before using it which then almost always leads to bad design and code.
-
Agile Coach: you need to take part in the next quarter planning of the work. Work with your business team to create a healthy backlog. Provide your input to the user stories. It’s a collective effort.
Me: why tf it’s not a collective effort when code breaks and only one dev is trying to fix it while taking in all the heat.
Of course I can’t say that out loud without getting fired.4 -
I recently recommended that we fix a gap in the current CSRF implementation.
I’m asked by a fucking business guy that if we haven’t seen an issue till now, why is this a priority?
Should I demo the vulnerability? Why can’t they fucking trust the people that they hire? It’s not like I wanna do it for some selfish motive. -
Competitiveness in technology. 10 to 15 years ago, a handful of companies controlled how the world would develop software (fuck you Oracle and IBM). Now there is a lot less monopoly.1
-
Sit in a reclining chair, put my head back, close my eyes, take a deep breath and whisper to myself,
“Fuck this shit. It’s not worth it.”
Gets me through the most stressful moments. -
So, I spent the last two days hunting down a bug about some of the static assets not getting versioned.
It turned out to be a mistake by some newbie missing a quote in html. The html parser responsible for versioning the assets broke once it ran into that bad html.
Somehow, I don’t feel satisfied. I guess I shouldn’t hope for big reasons for seemingly big problems. -
Fuck you, webdev.
I had to explain to a new web developer about an Oracle database and Toad. Anyone remember Toad? I still remember not too long ago, developers knew the basics of relational databases and available client tools. -
TFW you’ve already ranted about something and you run into the same motherfucking situation again so you need another way to vent.1
-
For fuck’s sake, Git is not SVN. Get over your fucking svn mindsets and learn the damn thing before coming to me to help with your conflicts.1
-
Refactored a legacy source file and reduced it from 2.8k lines to 300 lines.
Mixed feelings: happy that it is much simpler now and sad that my current project team members never go back to delete unused code.
Testing pending though 😜7