AboutPhysics/astronomy grad, likes making things, maybe too into science fiction. Also into computational geometry and data analysis.
SkillsPython, C++, some C#
Joined devRant on 12/29/2016
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
I stop doing things I don't care about.
If it's low motivation to do my job, I look at why. Am I tired? Do I dislike the kind of work? Does it feel like it's not going to help?
First, I make sure I'm actually doing alright. Usually, I'm just tired or maybe sick. Then I'll raise my concerns to management. There's a good chance that I'm not working on something meaningful and that we should change that.
So, I worked away from our software teams and directly with engineers for a few months to examine the capabilities of a new piece of hardware we expected to integrate with. It wasn't necessary that I be shut out from all the other software projects, but my boss decided that I shouldn't go to them. When pressed, he said he didn't want the meeting to be too full.
I studied this hardware thoroughly, and even know the engineers who designed it personally. This is, in every sense of the word, my project.
... So when the product owner asks to meet to discuss another feature around it, my boss decides he should invite the rest of my software team to meet with the engineers. There's some non negligible engineering background behind the tool and associated workflow.
When asked why he invited them, despite me being concerned about lack of focus in the meeting, he said he "didn't want anyone to feel left out".
This is the same man that cost me an entire week of work (and is now costing me my time with the systems experts) because he doesn't want to hurt the feelings of my junior colleagues. He's shown repeatedly that he's just fine excluding me, but heaven forbid my junior colleague feel junior.
I don't think he'll ever realize how much he's playing favorites here. Ugh.
Good news: my department is great and furnishes the developers with a special dark space to work with big monitors in a small, quiet room.
Bad news: someone from sales is camped out in here and the glare from the all-white word documents they have open is causing my oh-so-perfect screen (in dark mode, of course) to be unreadable.
As an added perk, they brought in a laptop and are using that almost exclusively. There are dedicated laptop chairs away from my workstation they could use instead.
Also, the entire room smells like their body spray. My only salvation is that it's almost five and maybe they'll leave soon.3
I spent three hours making a custom color scheme for my instance of visual studio. Almost every color in it is a variation on hot pink. I've used it every day for the last three years.
The background is black, though, because I'm not a complete animal.8
Literally anything but work with computers, I think. They ask my brother to fix anything technical in the house and ignore it when he fails. They haven't been able to watch TV in six months. When I suggest that my (well-intentioned but mostly nonverbal) sibling probably shouldn't go into development, they tell me I don't know my own job. I suspect they're convinced I do graphic design.
I write C++ applications that run physical simulations and sometimes train AI models for pattern recognition and highlighting unusual incoming files.
They suggested I go to an undergrad program for data science. I already *do* data science for money and I already have an undergrad degree. 🙄4
I was at a college career fair and had a list of 20 booths to visit. There were maybe a thousand other applicants. I was the only one in pink (technically coral) shoes. I'd walked four miles in those heels and had blisters everywhere I could from them.
At my last booth, the guy says "Oh! Pink shoes! I've been noticing them all day! Nice to meet you, I'm X." I gave him my background and resume, talked about the kinds of problems I wanted to solve and was invited to interview with them.
On my way home, I walked barefoot through downtown despite the ice on the sidewalks just to get out of those damn shoes.
A few weeks later, I got the job.6
Every year, my company organizes an internal seminar week for its engineers and developers. I helped plan it this year and, since I also ran a few sessions, was absolutely exhausted by the end of the week.
On Friday of that conference week (after I'd spent four hours in our engineering building), I come back to my desk to discover that a coworker managed to, single handedly, get our boss to agree to shortening our release cycle to one that, without dramatic infrastructure changes, would require about 8x the developer overhead than today's. ...The test cycle I am supposed to pick up in a month.
When asked about it, he said he was so full of energy, why wait for automaton? What better way to inspire us to improve than to switch right now? The worst that can happen is just a few bugs.
I love my job, but I can't stand this guy. 😒4
I'm interrupted frequently during team meetings, usually by junior team members. I brought it up to my boss at a 1:1 and now he interrupts me more often than they do.
I wasn't giving you permission. 😒4
For the first time ever, I locked up a processor while working. Take that, 24 cores!
Unrelatedly, if someone is in the office, could you please power cycle my box? ...Thanks.3
I don't pay much attention to my local file system when developing-- that's what my operating system and IDE are for. ...So I've thought, at least.
Today, my code didn't compile. I'd been noticing some pesky 'running out of memory' notifications, and mostly brushed them aside. I've spent the last hour deleting various log files and defragging the drive.
I'm too lazy to set up a proper code review from a branch. Instead, I just make dozens of quickly obsolete tags. I should probably learn to use subversion better, but... ¯\_(ツ)_/¯
There is an electricians shop just outside my apartment. Their favorite thing to do is yell conversations across the parking lot in the hour after dawn.
They finally shut up an hour before I need to go into work, when it's too late to fall back asleep. Ugh.4
It's so cold in the office that I want to work under my desk, next to my foot heater. Can't see the monitor from there, though.3
When I started university, I was getting out of some really awful situations-- emotionally abusive parents, a boyfriend who was blackmailing me, a truly bizarre rape, etc. My life had been a little rough, and I was dealing with some PTSD.
My first computer science course was great. The professor was clear, patient, everything a sensitive student needed. I was able to concentrate on the curriculum without any problems.
The second 'intermediate' course, though? Not so much. The professor shouted his lectures during the entire class period in a relatively small classroom. Occasionally, he would clasp his hands and move around pretty unpredictably (like jumping out at the class), which spooked me a few times. He also always seemed like he was just hovering on the edge of madness, like he was just barely keeping it together, but he never broke.
I sat in the front row and was absolutely terrified during his lectures because it seemed like he was mad at me. I was half expecting him to start attacking me at any moment. Because, you know, PTSD.
I was also only getting a comp sci minor, so the other students looked at me like I wasn't supposed to be there, which also made me feel pretty uncomfortable, but such is life.
After most classes with him, I would need to take about an hour or two afterwards to calm down, stop shaking, and recompose myself. I looked forward to test days because he wouldn't yell. It was rough.
Later on, I learned that he used to be a gym teacher, which explains the jumping and yelling. Also, his wife, daughter, and dog all died within six months of each other the year prior, which might explain why he always seemed so on edge.3
What do you guys think about 'contempt culture' in development?
(for the uninitiated, here http://blog.aurynn.com/contempt-cul... is a (lengthy) article on it)1
Woah! Collabs! Nice.
I'm actually glad it's a paid feature. The sheer entitlement of people using free software asking for development help for free has always bothered me.
Cool idea, I hope it works out!
I've just received an urgent bug report email saying something like:
Stop sending [item] to destination. This should have been taken care of in the initial work, but we forgot to say so.
... The work they requested was that [item] gets sent to destination if the user checks a checkbox. If I wasn't supposed to build this, then what did they want me to build in the first place?!1
It seems like there are more lower-quality or duplicate comments on rants these days.
Please, save me some time and show a little respect for members of the community by ++ the comment you agree with instead of adding a nearly identical comment and tagging the commenter.
Additionally, comments like '@commenter 😂' when the great comment is still at +0 generally don't add to the discussion and should probably be downvoted.
Comment if you think you can add something, not just because you saw it.14
A few years ago, we had a developer who would come in early and leave by four almost every day. I can't remember how exactly it started, but we would put up a picture of a different dragon on his cube wall almost every night.
He was a pretty laid back/passive guy, so we took bets on how many pictures there would be on his walls before he took one down.
3 dragon figurines on his cube walls and 11 full color pages later, we had a winner.
I had code waiting in review for ten days, blocking other work. On the eleventh day, the final reviewer (who was standing behind me as I wrote it) says "I'm not sure that I agree with the design, here."
I get you, man, I can re-write the algorithm, but I am so not in that context anymore and you've just delayed release of the feature by at least a week. Ugggh.5
This week we had a live production issue that our staff were catching/fixing on the fly. We're a relatively small software team without any direct external customers, so this is not too unusual.
Unfortunately, the person in charge of dealing with these issues didn't resolve it during the work week, so we were stuck with it over the weekend. Said responsible employee left at 2:30 on Friday without figuring out how we'd deal with the problem without any staff in the office to intercept problem cases. Better yet, he drove all the way back, and was there from 3:30 to 4 and promptly left again without telling the rest of the team what was going on with the production issue. We asked how it happened, what it was, etc, but didn't focus on his fix (in hindsight, a mistake).
Since it's his job, I assumed that he would let us know what was up before he left on Friday. It turns out that he never addressed the production issue at all and just decided to leave.
A junior developer and I spent two hours contacting management (who, at this time are already at home with their families) to get clearance to either shut the system off or fix it. No one wants to give it and no one that's high enough up to approve the decision is available.
In the end, we asked the weekend mechanical support team (some friends of mine) to monitor the issue and they kindly accepted.
All of this could have been avoided if my coworker had either told us his plan earlier (so we could ask about the lack of coverage), gotten approval to shut it down for the weekend, or covered his own ass before he left for the day.
Ugggh. I get that we all make mistakes, but I really hope this guy shapes up soon.
A coworker of mine was asked to make a utility C# app to help with our internal testing. The idea was that the app would collect data and display the results.
He decided that it was very important that the app have a command line interface. He's spent far more time building the app from scratch for the command line than he would have if he'd used C#'s built-in GUI utilities.
Today was our demo day and he shows an internal command-line app in 2017 built in C#. I asked about the GUI and he said that the command line functionality was more important. I suggested that it was maybe less user-friendly and he proceeded to explain to me how "non-technical" people might prefer a GUI, but clearly any serious developer would just want a command line app.
I feel like, in one fell swoop, he trivialized my suggestion, didn't address any of the data visualization needs, and suggested I wasn't a "real developer". Am I right to feel a little outraged by this?5
A coworker changed the application deployment process. He told all three of the other developers who need deployments, but not me. We sit six feet away from each other and I've run/managed deployments for a year longer than him.
His new process doesn't work and he's blaming the dev ops team for not following it. The new process clearly doesn't fit their workflow and never could have.
The lack of deployments have caused production issues and he still won't ping dev ops to remind them about the deployment because "it's not in the new workflow".
He's been painting dev ops as incompetent at the last three retrospectives without having ever personally reminded the deployment guy.
WFH and I got up to get a mouse for my laptop. Five minutes later, I sit back down with a plate of fish. Dammit, brain, wrong animal.
I clearly define the day's goal, get beverages/snacks ready, get my hair out of my face, take my glasses off, answer any remaining email, take a deep breath, and dive in.
Sometimes I'll listen to music, but it depends on the ambient noise level.