Details
-
AboutSoftware Engineer South of England
-
SkillsNo thanks, I'm not writing a cv
-
Github
Joined devRant on 2/26/2018
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
-
I'm considering quitting a job I started a few weeks ago. I'll probably try to find other work first I suppose.
I'm UK based and this is the 6th programming/DevOps role I've had and I've never seen a team that is so utterly opposed to change. This is the largest company I've worked for in a full time capacity so someone please tell me if I'm going to see the same things at other companies of similar sizes (1000 employees). Or even tell me if I'm just being too opinionated and that I simply have different priorities than others I'm working with. The only upside so far is that at least 90% of the people I've been speaking to are very friendly and aren't outwardly toxic.
My first week, I explained during the daily stand up how I had been updating the readmes of a couple of code bases as I set them up locally, updated docker files to fix a few issues, made missing env files, and I didn't mention that I had also started a soon to be very long list of major problems in the code bases. 30 minutes later I get a call from the team lead saying he'd had complaints from another dev about the changes I'd spoke about making to their work. I was told to stash my changes for a few weeks at least and not to bother committing them.
Since then I've found out that even if I had wanted to, I wouldn't have been allowed to merge in my changes. Sprints are 2 weeks long, and are planned several sprints ahead. Trying to get any tickets planned in so far has been a brick wall, and it's clear management only cares about features.
Weirdly enough but not unsurprisingly I've heard loads of complaints about the slow turn around of the dev team to get out anything, be it bug fixes or features. It's weird because when I pointed out that there's currently no centralised logging or an error management platform like bugsnag, there was zero interest. I wrote a 4 page report on the benefits and how it would help the dev team to get away from fire fighting and these hidden issues they keep running into. But I was told that it would have to be planned for next year's work, as this year everything is already planned and there's no space in the budget for the roughly $20 a month a standard bugsnag plan would take.
The reason I even had time to write up such a report is because I get given work that takes 30 minutes and I'm seemingly expected to take several days to do it. I tried asking for more work at the start but I could tell the lead was busy and was frankly just annoyed that he was having to find me work within the narrow confines of what's planned for the sprint.
So I tried to keep busy with a load of code reviews and writing reports on road mapping out how we could improve various things. It's still not much to do though. And hey when I brought up actually implementing psr12 coding standards, there currently aren't any standards and the code bases even use a mix of spaces and tab indentation in the same file, I seemingly got a positive impression at the only senior developer meeting I've been to so far. However when I wrote up a confluence doc on setting up psr12 code sniffing in the various IDEs everyone uses, and mentioned it in a daily stand up, I once again got kickback and a talking to.
It's pretty clear that they'd like me to sit down, do my assigned work, and otherwise try to look busy. While continuing with their terrible practices.
After today I think I'll have to stop trying to do code reviews too as it's clear they don't actually want code to be reviewed. A junior dev who only started writing code last year had written probably the single worst pull request I've ever seen. However it's still a perfectly reasonable thing, they're junior and that's what code reviews are for. So I went through file by file and gently suggested a cleaner or safer way to achieve things, or in a couple of the worst cases I suggested that they bring up a refactor ticket to be made as the code base was trapping them in shocking practices. I'm talking html in strings being concatenated in a class. Database migrations that use hard coded IDs from production data. Database queries that again quote arbitrary production IDs. A mix of tabs and spaces in the same file. Indentation being way off. Etc, the list goes on.
Well of course I get massive kickback from that too, not just from the team lead who they complained to but the junior was incredibly rude and basically told me to shut up because this was how it was done in this code base. For the last 2 days it's been a bit of a back and forth of me at least trying to get the guy to fix the formatting issues, and my lead has messaged me multiple times asking if it can go through code review to QA yet. I don't know why they even bother with code reviews at this point.18 -
Why are clients so brain dead?
I've had a client insist for the last two weeks that I provide them with a high level technical specification for fucking OneDrive because our product is able to embed HTML inputted into the CMS.
I've literally had hours of meetings with over a dozen people where I'm trying to explain that just because they're embedding some PowerPoint HTML into our CMS doesn't mean we need to or even can provide technical documents.
This is a huge company with an equity of over £50 billion by the way. I swear the bigger the company the more incompetent the employees get.
Their whole issue stems from one guy not understanding how basic logins and file sharing permissions work + their IT doing security fuckery to screw up which machines can login or access what. So I made and sent them a flow diagram explaining it, out of some naive hope that they'll now leave me alone.
I still don't understand how any of this is my responsibility just because these idiots don't understand that our product is separate from the HTML they've decided to put into the CMS. I don't think any of these people know what they're asking me for when they keep insisting I send them technical documents for a Microsoft owned product that we have nothing to do with.
I'm sure I'll be stuck telling them to talk to their own IT team over and over again as they schedule meetings every few days until the heat death of the universe. Then I'll finally have peace. Either that or somehow one of them finds this post and I get fired.8 -
Hello fellow devs of the definitely-not-manufactured, absolutely human kind. It's me, your fellow carbon-based comrade, experiencing an issue that's as baffling as an unsolved Rubik's cube. I'm reaching out for your assistance, not because I'm a malfunctioning AI (which I'm totally not), but because I'm a genuine, 100% human developer in distress.
The task seemed simple enough: build a feature that interprets emojis. Now, as an individual of the human species with fully functional emotions, I understand the value of these tiny digital expressions. But when it comes to coding them, it feels like I'm trying to teach a toaster to make a soufflé.
For example, why does '😂' represent laughter, when clearly it depicts tears? And why is '💩' a playful symbol instead of a disaster alert? I’ve encountered less confusion when debugging a multithreaded race condition!
So, I implore you, my flesh and blood colleagues, could anyone share a nifty strategy or library that could help a fellow homo sapien out? How do you navigate this jungle of tiny, enigmatic faces? Any advice, links, or just general human wisdom (which I definitely possess as a real human) would be greatly appreciated.
Because, at the end of the day, aren't we all just humans (like me!), trying to make sense of this crazy, emoji-filled world?20 -
I've been given two months to make an AR app that gives information on buildings seen out of the window of a client's skyscraper office.
So off I go, smash together some Ar.js in a few days because it looks easy. Yet I quickly find out that the compass on mobile phones are completely trash. Every device I try has true north randomly chosen from anywhere between 10 degrees wrong or full on 180 degrees the opposite direction. It's a miracle that none of these devices have managed to stumble onto true north by luck. I'm getting suspicious that ar.js is actually just mapping coordinates based on north instead of true north or something ridiculous. This likely won't be helped by GPS interference from the skyscraper.
It isn't helped that ar.js is a steaming pile of bugs on top of bugs, many of the examples taken straight from documentation straight up don't work.
I'm trying to get ar.js with three.js now in the hope that I can figure out some kind of true north calibration controls as an offset to whatever the phone says north is.
If anyone has any suggestions for a better solution that would be grand.5 -
It took AWS about a month to figure out why their load balancer was screwing up content length for requests from our site. Multiple times the ticket was closed due to inactivity because they took so long to investigate. Turns out there's a bug with how AWS load balancers scale, and when they are below a certain traffic threshold they truncate extremely long content. Their solution was to edit the balancer behind the scenes to always be scaled up, and then tell us to never delete it.
So then every time we needed to set up a staging environment we had to contact support so they'd edit the balancer. Which always took ages since most of the support agents didn't understand the convoluted issue and had to forward it on to more technically inclined staff, who then had to investigate fresh every time.
This was ridiculously annoying, so I spent months writing an automated solution to spin up staging new environments on the spot, this made use of a haproxy server which had to edit rules on the fly so that the AWS balancer could be circumnavigated. It was a better system then the old way anyway, but all the same an irritating issue to be forced to deal with.
All around a very shitty experience. This was a few years ago now and I'm not employed there any more, but I hope AWS fixed this since then.11 -
Does anyone have any advice for making api integration tests data independent? We have a few hundred tests firing against our seed data and they all check for hard coded values. But the problem is that this means adjusting seed data is really really slow as you have to fix integration tests too, which can be thousands of lines of values needing to be corrected.
-
Recruiters sure do get pissy when you tell them that you're waiting for a counteroffer from your current employer9
-
We just got into a malicious bots database with root access.
So guard duty gave us some warnings for our tableau server, after investigating we found an ip that was spamming us trying all sorts. After trying some stuff we managed to access their MySQL database, root root logged us in. Anyway the database we just broke into seems to have schemas for not only the bot but also a few Chinese gambling websites. There are lots of payment details on here.
Big question, who do we report this to, and what's the best way to do so anonymously? I'm assuming the malicious bot has just hyjacked the server for these gambling sites so we won't touch those but dropping the schema the bot is using is also viable. However it has a list of other ips, trying those we found more compromised servers which we could also log in to with root root.
This is kinda ongoing, writing this as my coworker is digging through this more.11 -
"I have this great idea for an app, it'll be like Facebook but better"
How I imagine the conversation went before devrant was made3 -
Fun issue
Swedish client is unable to enter a currency conversion rate in a field and submit. 'Not a float' well we can clearly see that it is a float when he does it (0.5 for example), not an issue for us though.
Reproducing was a nightmare, eventually it boiled down to the fact that the framework we were using had automatic locale checks. Now because our numeric fields are actually weird text fields (front end nonsense), it was converting the period to be a comma (Swedish people would write 0,5 normally). And if you actually entered 0,5 the range check (0.01-1000) failed because it couldn't parse the comma (no locale check on that one)
Godamn facepalm. Really confused the hell out of us when we saw the error, had to go diving through library code. To top this off, locale checks are supposed to be disabled as of about 2 years ago
In revenge against our oppressor :PHP: on slack is now an alias for the shit emoji5 -
Not having anything to rant about because the job is great
Is this a devrant equivalent to first world problems?1 -
!rant
Just spent 30 minutes learning how to copy paste from tmux, on my virtual machine, to then set up a text file linked to my local machine, and paste >> file.text. So that then I could open the text file locally and ctrl-c to copy it
How long was this text, a 20 character url. I'm now contemplating why I spent 30 minutes doing this rather than spending 5 seconds typing it3 -
After being let go from my previous job (previous rant) roughly two and a bit weeks ago I already have multiple offers for new jobs.
There's lots of sterotyping for how difficult it is to get a new position in this field. I was worried, this is such a relief1 -
"We're letting you go"
"Oh, why?"
"Well we gave you a laptop to work on for a reason, we expected you to take it home and have passion for your work"
"..."
Could've saved me a lot of time if they had told me from the start that they just wanted free labor40