Details
-
AboutMagical processor fairy; part-time misanthropic bane of idiots. 🧚♀️🏹
-
SkillsRuby ❤, js/es6, css, react, sql. VB and PHP can die in a fire.
-
LocationSlaving away for retards
Joined devRant on 2/25/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
-
@Demolishun How have you not gotten banned?
-
I’ve spent the day fixing someone else’s “I wrote a bunch of scripts to automate all the dev env setup for all the microservices, and kept it up to date!” bash scripts.
Some of it points to gitlab, some points to a self-hosted gitlab. Answering “No” to optional prompts just repeats the prompts. Some of the steps have error checking and retry, some of just assume everything works (it doesn’t). And starting the script over doesn’t check for progress, but wipes things out and remakes/reconfigures them, fucking up all your existing dev envs.
It’s such a giant pile of unmaintained shit. I’ve attached a picture for reference. -
@Grumm Server is already created; this is just deploying new code on top of it. (And recreating the data from daily sanitized prod data)
But yes. This whole dance routine takes forever. -
It’s just the 5G over-the-air monkey pox vaccine updates
-
I forgot to add:
• Schedule a UAT demo with the product team -
Tickets at $work have lots of dance steps:
• Move ticket into sprint, set to in-progress, set “dev resource”
• Negotiate release date w/ QA
• Read ticket; talk with stakeholders for details
• Add est. story points
• Do the work
• Revisit with stakeholders
• Write specs
• Manually start CI
• Spec+CI iteration as needed
• Copy CI results to Jira
• Open PR; do self code review
• Ask in Slack for a code reviewer; babysit
• Write detailed steps for QA, w/ sample data, screenshots, expected results, gotchas
• Write detailed application security + data security notes in Jira
• Write up technical implementation summary
• Find avail. testing server and claim it in Atlassian; ask QA to approve server
• Deploy to testing server; test again; release server
• Babysit ticket through QA
• Update branch as it stales
• Get release approvals
• Update Atl. release page
• Notify sysops of migrations
• Ensure ticket isn’t lost during QA / release building -
@retoor I agree, though $work really killed that for me.
-
@Lensflare Let’s just hope it won’t feature you doing pushups for misgendering a bandit or for being a problematic xenophobe and thinking a Daedra is hostile.
-
@jestdotty hahaha
So it’s not just me! They’re gorgeous, they treat me well, the food is gorgeous too, but when they try to have a conversation… it’s just. It’s like I’m leading them around on a leash. I can’t do it. Chiseled features and yet so squishy in the head. It’s depressing. -
@cprn I applied to some companies in Spain, Ivory Coast, and Norway before for that very reason. All remote of course, though I’d love to visit Spain.
The Ivory Coast people refused to hire me because they thought it was too weird that I’d take a job for such low pay. I just wanted things to be interesting! Ah well.
And … I kind of hit on the Spanish interviewer. So I didn’t get that one. He was just so unbelievably attractive I couldn’t help myself. 🤦🏻♀️ It was probably for the best I didn’t get the job. -
@antigermgerm @retoor I still haven’t joined that. I really ought to before this place disappears.
@cprn I’ve done basically that contacting … eight people from devRant. It wasn’t as bad as you outlined though :) -
I should probably use something like this.
I don’t have time to work on personal projects anymore, and I’m currently only committing to gitlab (and have been for quite awhile), so I’m getting no commits at all. Probably why I’ve been getting almost no application responses. -
@Demolishun Likewise. I almost reacted with one, but didn’t want to be political here either.
-
@retoor It’s a work lappy, not personal. I’m years overdue for a replacement, and I really don’t care if they have to pay for it :) But no, it isn’t damaged in any way; it’s just feeling abused.
-
@Demolishun I’ve been following it all morning (though not on Reddit; yuck). The memes are delicious.
I might take a look. -
@retoor How do you go about this?
-
That’s so cool. I want to do that.
-
Okay.
-
… and I’m burned the fuck out and can no longer care enough or put in much mental effort. I get stuck on something minor and give up for hours or longer because i simply can’t anymore.
-
@retoor Yes, but not officially here. At my last job I was the lead developer. Likewise for the job before that.
While interviewing, during hiring, etc. at $work, the hiring managers and the VP all said ”we only hire senior engineers” (in various phrasings), but the company didn’t bother with titles at the time, so everyone was just whatever (code monkey, make mistakes and fix them, I make shiny things, dev, etc). Official titles came years later, and HR slowly rolled them out, and not everyone had their title “corrected.” There was no official process, it just kind of happened at random. Now the company hires various skill levels and assigns roles on hiring. All new titles are earned exclusively through promotions (which are handed out primarily to dei employees).
Doesn’t matter that I have more years of experience than most of the “principle” engineers (and a few of them combined), or routinely fix their bugs. To $work I’m just a “software developer.” -
At $work I’m a “software engineer.” Not a junior, not a senior, not a staff or principal or whatever. Just a software engineer.
Nearly everyone else there is a senior or principal dev. Not because they write elegant and performant code, architect well, understand new things quickly, etc. In fact, to my knowledge not a one of them with these titles are particularly skilled. What they all have in common, however, is a) having a high minority score, or b) being hired after HR decided to use titles.
In the former case, promotions are easy and readily available; in the latter, titles come by default. For those whom these two cases do not apply… promotions are neigh impossible.
So no, titles do not always mean much, either. Nor do years of experience, certifications, references, attributions, etc. I’ve seen many a useless yet highly-decorated developer.
Talk is cheap. Show me the code. -
Dark chocolate (85%+).
Gummies of all kinds.
Cherries, especially with dark chocolate.
The life energy and motivation of my enemies.
Cherry energy drinks (Bing) with limoncello. -
@Demolishun Probably because of the uncanny resemblance. With her limited mental faculties, she likely considers them to be members of her own species.
-
@retoor That’s why I don’t unless I must. I’m not allowed to refactor, so.
(Why? “It clutters git history” and “it makes code reviews confusing” and “if it isn’t specifically spelled out in the ticket, it’s off limits”. Uh-huh.) -
No. But maybe if you’re a far-too-clever junior.
-
Hire a professional to write your shit.
-
Google.pdf
-
@rudinskiz it’s all about brain damage and money, eh?
-
My current manager is impressed if I…
• Tell people every single thing I’m doing as I do it
• Do someone else’s job in addition to my own
• Never complain, and compliment everyone
• Compliment him
• Do what he and his managers ask “from on high” without question
• Post lots of things about what I’m doing in the team’s Slack channel
• Give demos even if they’re boring and useless to everyone else
• Appear online early and late even if I’m not actually there
• Give detailed weekly status updates describing every little thing I did on each of my projects
And of course
• get complicated tickets done really quickly, even if poorly -