Details
-
AboutSoftware Engineer
-
SkillsGoLang Ruby lang Bashism ECMAScript Java lang or whatever
-
Github
Joined devRant on 8/13/2016
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
-
We were once tasked to create a 3-part Flash game to advertise the upcoming release of an album by a very famous band. Every part used a different gaming engine which we had to build from scratch (one of which was like a simplified version of the OG GTA game - top down driving with zooming in etc). On top of this we had to deal with user registration and score submission.
We had 4 weeks to do it in. We were 3 people.
We did an illegal number of hours to get as much done as we could, and we still didn't manage it in time because, frankly it was impossible.
Pretty good game though.1 -
Migrate and entire fucking ERP system in NINE DAYS.
"It's just copy and paste!"
Yeah, if both systems worked exactly the same. And if they do, why switch?5 -
Most unrealistic deadline I've had?
The client gives us a project with A 3-month deadline. All good, at first.
3 days later they told us that they're cutting out the funding and they gave us two options: Either stop the project right away and get paid for the work so far, or somehow finish the project in 7 days and get paid for the 10 days worth of work.
My idiot boss chose the second.
Saturdays and Sundays were declared working days, everyone screaming at each other, devs running around scrambling code to make the webpage render and keep it responsive.
Forget unit or automation testing, we only did not null and undefined testing and submitted the project.
Yeah, I hauled my ass out of the company just after that.4 -
Once, I overheard a conversation between my former PM and a client during a phone call.
Client: I will send the final draft of the project by Thursday.
PM: That's great to hear!
Client: When can I expect the updates to review the changes after the draft is sent? I need to present it at a meeting this weekend.
PM: It should be ready by Friday without fail!
Client: Excellent! Thank you. I will be expecting it.
PM: Sure, goodbye.
(After the call, PM joined the team.)
PM: So, team, the client for Project-A will be sending us a new draft for review and updates. They are putting a lot of pressure on us and need it to be ready by Friday at the latest. We need to treat this with a sense of urgency.
(After hearing this, we felt compelled to respond.)
Me: There's no way they would expect us to deliver an unseen draft within a day. Both the backend and Figma team members were forced to work last weekend, on Saturday, because you mentioned that Project B was behind schedule and the client needed an update by Monday. We simply can't continue working like this.
Backend guy 2: I also worked last Sunday on Project B.
Me: We overheard you telling the client that they should expect an update by Friday. It seems like you're the one directly putting the team under pressure, even though we still have three ongoing projects with tight deadlines.
(The office fell into an uncomfortable silence.)
(PM left the office without saying a word.)
Later on, I heard that he contacted the client to reschedule the expected time of arrival (ETA) after receiving the draft.7 -
My CTO told the COO and CEO i'd be finished SOC2 compliance by the end of December... On December 14th.
It takes 3 months to do the audit, let alone all the actual work. I hadn't even started yet.
He was fired shortly after that.7 -
Current workload as dev lead:
- 1% actual development
- 2,5% waiting for SaaS to load
- 2,5% cursing company server network connectivity issues
- 5% switching VPNs
- 7,5% pkg management & deploys
- 10% writing JIRA and support tickets
- 12,5% filling in timesheets
- 15% coaching & reviewing a bot coworker
- 19% doing 2FA, refreshing expired passwords
- give up and spend the remaining 25% doing something meaningful8 -
Why 95%+ devs are bad ???
Just did a recruitement for a post opf Principal Engeneer with possibuility to be CTO.
375 candidats at first interview.
Only 8 remaining for second phase
Our of 8, only 3 managed to complete a small code test.
Outr of 3, one asked for (I shit you not) 700k$ salary (lolz).
Out of 2 remaining, 1 just decided "I did for lolz to see if I get an offer so I can boost my current work salary",
Leaving us with only 1 candidate...
So fucking time consuming.....18 -
I told you. I told you that adding this fancy library to the project was going to bring problems but nobody cared.5
-
- Hey, I need to do X and I need your department to do it.
- "We can't do X, this is against company policy!"
- Oh, sorry, I didn't know. But I will have to justify it to my boss, can you point me to where in the policy it says you can't do X?
- "No I can't, it won't be there. It is just common sense"
- Wait, what? You saying you can't do something because it is against the company policy even though there is no restriction against it in company policy?!
- "Other companies don't do it either"
- I will need you to say that in writing, I need to explain it to my boss.
- "Our email server is FUBAR"
- It can be hand-written
- "I can't give a declaration in name of my department!"
- Wait, so you can interpret company policy any way you want, make decisions regardless of what the policy actually says but you can't own up to it in writing?!?
- "..."
- ...
(Some context: I've been emailing them about X for more than a week. Just got crickets for a response. Not even an evasive coward response, just no answer at all. And calling them leaves no paper trail. Fucking oxygen thiefs)
For fuck sake, are non-tech departments always filled with complete morons?!? Does anyone have ever worked with smart, or at least minimally-coherent non-tech people?!?!
Seriously, does anyone there have some story about some non-stupid non-tech/analog/muggle coworker?!?
I'm inclined to think that anyone who can think systematically is either working in tech or not working at all.6 -
Have you ever been pair coding with someone who uses shotgun debugging? I am about to claw my eyes out! What is shotgun debugging you ask?
Code doesn't work... What do we do?
I start thinking about possible flow, how to go back to what works, where to insert debugging statements. My partner interrupts my thought and says - what if we change this variable name?
...uh what?
What if that fixes it
It won't!
Well how do you know if you don't try?
I change the variable name - of course nothing works and now I forgot the possible solution I was thinking about...
Starting over... I again start coming close to the idea... Interrupts me again. What if we comment out this random line?
Why what's your reasoning?
Answer: *Shrug* idk might work...
...rinse and repeat
WHAT IS WRONG WITH YOU???!
I literally started muting my computer sound so I can not hear him while I think and that helps tremendously. This is programming not magic, people!!! Stop throwing random "what if" suggestions!13 -
User: - I'm seeing a redcircle with a white dash.
Me: - What is a "redcircle with a white dash".
User: - It's like a stop sign.
I hope I won't meet this user on a one-way street.2 -
So today our CFO stepped into IT and angrily proclaimed someone using tech@ e-mail and fake name is defrauding company funds buying themselves... "used female lingerie with extra virgin juice" (sic!).
I work for an IPSP, we handle finance for commercial services (think PayPal but smaller). One of our clients is a big platform where girls can sell items like bath water, used socks and more. CFO demanded our admins found out who and when connected to that website, what URLs and so on.
As mentioned, said platform is pretty big, hence, from time to time we help them with their service when they ask us to, that's why we have a tech@ account. Last month there was a minor issue with one of the banks, someone fixed it and, as per usual, made a small payment of €1 topping up the account wallet to make sure everything works. It was an intern whose will to live is still strong and unencumbered with experience so she jokingly wrote "panties juice, extra virgin" in the payment note. What she *didn't know*, however, is that admins on that platform used the very same account to test new billing system they've implemented and our CFO received an invoice.9 -
Dev: I think we should send Dev2 for some training and certification
Manager: We do not train people or have them certified. When you train people and especially if you have them certified they always leave the company for better offers so we no longer do that.
Dev: So the plan is to have a the company operated by a bunch of untrained uncertified people?
Manager: 😡 You are being disrespectful again20 -
Manager: Hey what was that that you closed on your screen just now?
Dev: That popup? That’s NVIDIA letting me know that a new driver for my GPU is available.
Manager: Isn’t that for video games?
Dev: I mean that’s the reason many people opt into having a GPU but It’s not the on—
Manager: You are NOT allowed to play video games on your work computer!
Dev: This is my personal computer. It’s just an older GPU I popped onto this computer since otherwise it was just sitting in a drawer. My work computer is out of commission.
Manager: Well where is your work computer? How come you are not using it?
Dev: …Because of that blue screen of death issue we talked about yesterday.
Manager: Ok but that doesn’t give you permission to play VIDEO GAMES on your *WORK* computer.
Dev: …26 -
Given a couple of lines of code, I can predict with an 80% accuracy which of my team mates wrote it.9
-
Manager: I can’t believe you use Linux, that is such an outdated operating system. You need to get with the times and move to a more modern one like Windows or Mac. Literally NOBODY uses Linux anymore, do you still go to Blockbuster Video too? Ha!
Dev: …
I’m starting to realize that 80% of my job is resisting the urge to punch this guy in the face. Thanks goodness for remote work.33 -
Most successful project... What is success?
My first computer at 8 years old was a Commodore64. There was no internet yet, so I used the manual to learn about BASIC and assembly, sound and sprite registers, and created a pretty elaborate RPG. Mostly text, some sprite art, soldered some eeprom cartridges, optimized the code. Spent almost a year on it. An enthousiast magazine picked up on it, revised, QA'ed & published the game, sold a little over 10k samples. I got ƒ0.25 per sale, and I was completely overwhelmed how much candy one could buy for ƒ2500 ($2k corrected for inflation).
More recent:
I was employee #3 at my current company, started when it was worth nothing and the website redirected to a set of Google Forms containing all the logic. I wrote a large part of the first, monolithic backend.
Now there's teams in a dozen countries, and an estimated revenue of a quarter billion.
So obviously my current "project" is more successful.
Still, my current job sucks, the company turned into a desolate passion-free wasteland full of soulless fake hipster zombies and managers who seem to derive sexual pleasure from holding extremely ineffective meetings, endlessly rubbing their calendars together in their bureaucratic orgy of ineptitude.
So, I'm more proud of my C64 game.2 -
Thinking of starting an OnlyFans where I post all the atrocious shitcode that I find to make my fans miserable….6
-
I was today years old when I figured this.
Whoever named the app and designed the logo is an absolute fucking genius.10 -
My first contact with an actual computer was the Sinclair ZX80, a monster with 512 bytes of ram (as in 1/2 kbyte)
It had no storage so you had to enter every program every time and it was programmed in basic using key combinations, you could not just write the commands since it did not have memory enough to keep the full text in memory.
So you pressed the cmd key along with one of the letter keys and possibly shift to enter a command, like cmd+p for print and it stored s byte code.8 -
When I self-published my first indie game on steam and people actually started buying it.
Remember sitting on the floor with a bottle of vodka trying to tell my girlfriend like that lunatic dotconnecting on a whiteboard meme guy, this is really bad because too much people bought it.
They should spend their money on something useful instead of me, I felt like a fraud.
It turned out good in the end tho, made some updates for it that made it better so i felt better about it, plus got a job from a publisher because they liked my game 😃6 -
Be more passive
I always get involved in everything, at every company. Not to further my career through ass-kissing and overperforming.
I regularly piss off people. When C-level has a discussion about strategy, I'm usually ahead of them, ask too many questions, criticize every detail they've missed, cause frustration by making them look incompetent.
Can't help it, when I see retards destroy a great product I have to intervene.
Some people appreciate it. I often defend both devs and end users, when others don't dare speak up.
But fuck it, I'm getting older. I'm gonna coast a bit more. Sit back, relax.
If a product manager doesn't prepare enough tasks — that's cool, I still have a Factorio savegame to work on.
If another team designs an incredibly stupid feature — they'll discover the issues eventually by themselves. Maybe I'll warn once, just to be nice.
*Pours another chocolate milk*
Also gonna spend at least 4h/d with my daughter. She's a better human than most of my coworkers, and the work we do using her Legos is honestly more important for humanity than the Jira backlog.20 -
Dev: Hey our current server is starting to chug a bit. Can I get approved for $1200 additional spend to double the speed?
Manager: *Sharp inhale*. We need this project to cost as little as possible, we really can’t justify spending any additional money for any reason right now.
*2 days later*
Manager: YOU ARE APPROVED FOR $100,000 TO IMMEDIATELY IMPLEMENT SOMETHING RELATED TO NFTs IN ANY OF OUR APPS. THE BUSINESS NEEDS TO EXPAND INTO THE METAVERSE ASAP IMMEDIATELY. I NEED AN ETA BY EOD AS TO WHEN THIS CAN BE ROLLED OUT.
Dev: …16 -
Tech startups, an analogy:
After 18 years going from help desk teams to NOC teams, telecom engineering and all manner of startups in between I have concluded the following:
Imagine wanting to start an aerospace company because you know how to fold a paper airplane, but not how to actually design and engineer an actual craft that will pass basic air worthiness checks.
That’s 99% of “tech” companies.
Discuss. I’ll make drinks.9 -
This guitar looks heavily worn, yet it’s brand new. It’s called a “relic” — the guitar is artificially aged. Relics always cost crazy amount of money compared to regular guitars.
Relics were invented by Keith Richards, when he said “bash ‘em up a bit” to a guitar master builder from Fender, the guitar company.
With one phrase, Keith created a billion dollar industry.7 -
On my former job we once bought a competing company that was failing.
Not for the code but for their customers.
But to make the transition easy we needed to understand their code and database to make a migration script.
And that was a real deep dive.
Their system was built on top of a home grown platform intended to let customers design their own business flows which meant it contained solutions for forms and workflow path design. But that never hit of so instead they used their own platform to design a new system for a more specific purpose.
This required some extra functionality and had it been for their customers to use that functionality would have been added to the platform.
But since they had given up on that they took an easy route and started adding direct references between the code and the configuration.
That is, in the configuration they added explicit class names and method names to be used as data store or for actions.
This was of cause never documented in any way.
And it also was a big contributing cause to their downfall as they hit a complexity they could not handle.
Even the slightest change required synchronizing between the config in the db and the compiled code, which meant you could not see mistakes in compilation but only by trying out every form and action that touched what you changed.
And without documentation or search tools that also meant that no one new could work the code, you had to know what used what to make any changes.
Luckily for us we mostly only needed to understand the storage in the database but even that took about a month to map out WITH the help of their developer ;)
It was not only the “inner platform” it was abusing and breaking the inner platform in more was I can count.
If you are going down the inner platform, at least make sure you go all the way and build it as if it was for the customers, then you at least keep it consistent and keep a clear border between platform and how it is used.12