Details
-
AboutGoogle it
-
SkillsJava, Python 2 & 3
-
LocationYes
-
Website
-
Github
Joined devRant on 12/29/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
-
Before I left for vacation two weeks ago, I busted my butt to build out another portion of my frontend testing framework and get it in place (and spec’d) to unblock a coworker on a semi-high-priority ticket. I sent him detailed notes on which areas of the product it covers, how to use it, and copied one of his (blocked) tests over and updated it to use the new methods, pattern, namespacing, etc.
I came back today and discovered … he hasn’t even touched it. Everything is exactly as I left it.
Wheeeeeee.12 -
2010: having so many toolbars intalled in the browser you can barely see the actual webpage.
2024: having so many banners and popups in the webpage you can barely see the actual webpage.10 -
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 -
I thought my code wasn't great until I saw this project marked for decommissioning by end of 2024.
Holy shit.
These people basically wrote their own JS full stack framework because they don't like frameworks.
In one of the files, there are over 150 console logs.
I also found two database names. I wonder if I keep digging, I might find a full database query string with login credentials in plain text.
I have to provide support if needed because they're firing the contractor. Wise Decision, methinks.7 -
I'm reviewing a PR and it's easy to detect which functions were created with an AI: the ones that have comments.4
-
My TEN YEAR OLD twin girls came to me with a TIMESHEET and PIE CHARTS to explain to me why "Our household would benefiter (sic) a Nintendo Switch".
They... actually did what for an intern would be a passable data storytelling job (orthographic errors aside).
They explained how they would share the videogame between themselves (because it is not allowed at their school, not that we would let them bring it there anyway) in a colorful timesheet spanning four days a week.
They even put a pie chart showing how most of the time nobody will be using it.
I feel at the same time immensely proud, scared, and a wee bit freaked out that they came with all that to me but with their mother they just talked. Do I seem so distant that they feel they can't convince me without data? I gotta watch out for using work jargon at home.
Anyway, first "interns" that I have ever seen using a pie chart with the appropriate number of classes (even if highly biased).11 -
Manager: We do not identify as a tech company so don’t expect tech company salary increases this year
Dev: Well don’t expect me to bring a tech work ethic then
Manager: !!5 -
There has got to be a vetting option for this shit. The number of green dots asking for easily googleable shit is getting far too annoying and y'all dumbasses answering them in an effort to get upvoted is fucking pathetic.
Google shit, most basic and long term producing ability of anyone in I.T
We are not here to give you pointers, solve homework or teach you shit.
This platform is for pro devs bitching about their workplace.
Tired of mfkers that learn how to hello world and get here
Fuck off.17 -
Professor in Programming 1 & 2, 54 years old, divorced, has two kids in our age, golf player
Every time, he came in, we started with the lecture, than he started to talk about politics, greta, the stupid young people, specially the women, always the women. While he was talking to himself or asking us students very personal questions to judge us and recommend how we should do it better, he was talking himself into rage. We never learned something about cs or java longer than 10 minutes, the other long hours he only talked and talked about personal stuff or politics.
One day he asked us about the method of training a dog. You train a dog with pushing his face into his own pee. Than he said with us it is more difficult and that if he would be allwoed he would use methods like this and other very effective stuff on us.
He always starts his emails with
Dear humans
To make fun about gendering.
Another day a student came 1 minute to late, the prof stopped talking became very angry, first he went to a armchair and was sitting there for 15 minutes without saying a word, than he left without a word the room for 30 minutes and when he came back we had to listen to one of his monologues for some hours like usually.
And these are only some samples, he always acted like a little kid, but our university is very poor and i dont think they can effort a better professor for this.9 -
Oh damn....I just realized that I am working with a scammers' company. They wanted us (new employee) to create an app behave like keylogger for Android(not in Google play , because Google with ban this one).
Today I asked the manager about our salary. He said that our salary are based on commission. So look what happened, one of my colleague disappeared since yesterday (as in not coming to work without warning)14 -
In 2018, while working in Tokyo for a Fukuoka-based startup, one of my co-workers insisted that he wanted an SSL certificate installed on his local dev machine, but he didn't know how to do that. So I created and self-signed one for him. When our CEO came to visit our Tokyo office from Fukuoka, the coworker proudly showed him how his browser would display that green lock icon when visiting localhost:3000. This apparently impressed my CEO, because a few days later the coworker was invited to work at the HQ in Fukuoka while everybody else at the Tokyo office (incl. me) was let go.
This coworker would also only copy whole open source repositories, foo/bar/g all occurrences of the project name with our company name, and tell our CEO that he wrote that code.
I don't know how to deal with this bullshit.9 -
OMFG!! I just discover a fucking bug in a library used by thousand of people in scientific community!! 🤩🎉
Started when my program outputting strange result. I was in a huge fight with my supervisor about one of the function from the library. My hunch was telling me that this function is the source of the problem, but he insisted that no such bugs could exist in the library that has been used by thousands of people.
I couldn't reproduce the bug so I just stayed silent at that time,
But now, I finally got the bug showing. Yeah I am gonna shove it to his face next week.✊
I will also let the people who maintain the library know.
Feels so good being able to be a contributor PR to this famous library 😎
The downside is now I can't use this function, I have to implement by own function.5 -
My boss is still forcing us to support IE11. Recently, we started having even more bugs with one of our vendors on IE. We filed bug reports with the vendor to fix it, and they came back with "no. Why would we fix anything for IE11? Not even Microsoft is fixing anything for IE11." Boss's answer: well, let's make a separate component for IE11. Probably using flash and/or silverlight. We asked about redirecting IE traffic to Edge, he said that's "the nuclear option." So, doing the thing that Microsoft suggests, that involves not much work at all is "the nuclear option"; ignoring industry standards and recommendations, introducing well known security vulnerabilities, losing money, and trying to circumvent the vendor that serves out our major product, however, is totally reasonable. Our IE traffic is less than 3% of our users at this point.24
-
Two mobile devs were talking for 10 minutes in this zoom meeting whether "the component on the bottom should be hidden, or made sticky".
I just could not contain my laughter any longer when they showed an animated mockup comparison, and the product manager yelled excitedly: "Oh yeah, I love the one where it's very visible and sticky! But could you make it bigger for me?"
Sorry HR. I will never become a grown up boy.5 -
DO NOT let employers demoralize you into staying with the company.
I've been with this one company for about 2 years. Everything was great, despite being underpaid, and having a lot of responsibility (I was the only front-end developer maintaining 4 big eCommerce sites).
One day about 2 months ago, I got a better offer. Better pay, more freedom, and way less stress (Customers screaming in your ear vs. no customers at all).
I talked to my team lead since I wanted my company to have a fair chance to counteroffer - I was fairly comfortable after all, and I felt like it would be a nice gesture.
If my team lead had just said "No, sorry, we can't counter that offer", there's a big chance that I would have stayed with them anyway. Instead, I got a fairly uncomfortable and personal rant thrown back at me.
He basically said that I should be happy with my salary, that he didn't feel like I had much responsibility, and that "I wasn't the type of person companies would hire for that salary".
He ended by saying I might as well stay, as there was no going back if the new place didn't work out - basically trying to tempt me with job security.
I told him that I would think about it. The worst part is that I actually did, since his rant really made me feel somewhat worthless as a developer. Luckily I came to my senses, and sent my resignation the next day.
I talked to an old coworker today, and they are still unable to find a developer who wants to take the job. I see that as justice :)
tl;dr: If a company tries to make you stay by demoralizing you - Run.17 -
PEOPLE. DO NOT LIE ON YOUR RESUME. IT. IS. NOT. WORTH. IT. Ok, backstory.
We had a guy apply for this position at work. It really needed to be filled but also required someone with just the right certifications, so hiring the first schmuck to come along Was not an option.
We search high and low and as time passes without an acceptable applicant we become more desperate and open to negotiation. Basically, you name your price, we’ll agree to it at this point.
So finally a guy comes in, got everything we need but one minor certification. No problem. He can get that on the job, he doesn’t need it to start. He’s hired.
So he quotes us a salary 10% above our top range of what we’d usually pay a guy for this position, we don’t care. He gets it. Plus a housing allowance.
So we’re getting him registered with a place to handle his certification process and they call his four year institution to verify his transcript. We work with hazardous materials and a four year degree in a relevant field is required. It’s standard for the certification training institution to check. Especially when it’s a prestigious big name place like this guy had. And here I used to think that was paranoid of them.
They call and tell us the school says they have no record of him. We do some digging. He was never registered there. I’m like “that’s not possible, his professor is a listed reference. We call that reference.
He worked on a project with this man, he never taught him. Is very fascinated to learn this man has been presenting himself as though he attended the university. Asks to be delisted as a reference.
So long story short it comes out this guy did have a degree in this field, just from a less prestigious university.
The insane thing is, he would’ve still gotten the same job and salary package if he’d been honest about his university!
It is a loss for all involved. He doesn’t have a job. We don’t have anyone working in this position. It’s really unfortunate. Don’t lie on your resume people. Your employer will find out and the risks are not worth the benefits.12 -
I. FUCKING. HATE. MOBILE. DEVELOPMENT.
I already manage the data, devops, infra, and most of the backend dev.
We had a mobile guy. He was great. I never had to think about it and kept moving quickly on my work. #SpecializationOfLaborFTW
He left. Why? Because they wouldn't give him a small raise despite being one of the best mobile engineers in the firm. WTF.
I made the mistake of picking up just enough slack on this workflow in the interim such that I'm, apparently, the fucking god-damned release manager, fixer of pipelines, fixer of build configs, fixer of anything where someone just needs to RTFM for a half-hour to not fucking break things.
Now, 8 months later...and, apparently, Fortune 500 companies are too fucking god-damned cheap to pay for someone who actually knows WTF they're doing for a very reasonable thing to have at least one dedicated set of eyes for.
I never wanted to be a mobile dev.
I never will want to be a mobile dev.
And I certainly don't want to manage your HALF-FACE-FUCKED detached expo configs.
There's a reason I never intentionally involved myself in mobile. All the way down, it's just shitty cross-compilation, transpilation, dependency-hell, brittle-as-fuck build processes so we can foot-gun and mouth-gun react-native and expo and babel and whatever the fuck else cargo-culted horseshit into the wild.
And why? What's the actual fucking root cause? The biggest white elephant that ever fucking elephant-ed? It's because Apple and Google decided to never collaborate on a truly-native cross-platform SDK--where engineers could write native code that compiles to native binaries that's simply write-once, run-everywhere. They know they could have done that, and they didn't. So what'd they get back? Expo--a too-cleverly-designed backdoor/hack--more-or-less a way to circumvent the sane release process software has usually followed: code -> executable -> deploy. Or code -> deploy (for interpreted langs). Expo's like "keep your same executable, we're just gonna to do updates by injecting new code into it whenever we want". Didn't we learn anything with web? Shit gets messy real quick? Not to mention: HEY EXPO, WE WERE ALREADY BUILDING NATIVE APPS, YOU SHORT-SIGHTED FUCKS. THANKS FOR LURING OUR CTOs INTO FORCING EXPO DOWN OUR THROATS W/ THE IMPLICIT (BUT INCORRECT) TOO-GOOD-TO-BE-TRUE PROMISE THAT WE CAN HAVE WRITE-ONCE, RUN-ANYWHERE WITHOUT ANY BUY-IN OR COOPERATION FROM THE ACTUAL TARGET PLATFORMS.
And, we just, like, accept this? We all know it's garbage engineering. The principles we learned in the classroom aren't just academic abstractions--they actually yield real-world results--and eschewing them yields real-world failures. Expo is tightly-coupled to high-heaven, with leaky abstractions six-ways-to-christmas, chock-full of foot-guns, and fails the most basic test of quality: does it, "just work?"
Expo is fucking shameful and it should fucking die. Its promises are too bold, its land-mines too many, its future-proof-ness is alway, always, always questionable as fuck and a risk to every project that uses it.
You want a rant? This is my fucking venue, 'tis not? Well, then this is a piss and vinegar rant straight from my blood-red, beating fucking heart:
EXPO FUCKING SUCKS. AND IF YOU'RE A FAN, YOU FUCKING SUCK TOO.27 -
I once worked until 8am to get a demo ready for a client of the client. I knew the client was a bit thick, so I made some comprehensive video demos and sent them over to him, to save him trying to demo it himself. I wake up at 11am with him screaming down the phone at me:
“It doesn’t work, none of it works!”
“What do you mean?”
“I go to login and I can’t enter anything.”
“I haven’t sent you anything to log into...wait, are you trying to log into a video? Tell me you’re not trying to log into a video of a login page.”
“Uh...oh hang on, it just worked. Ok no pr-“
“No wait, what do you mean it worked?”
“I logged in fine.”
“It’s a video. You can’t log into a video.”
“Uh...alright, bye mate, thanks!”
The moral of the story is: never assume any level of intelligence on the part of a client, even if they exhibit signs of it at first. If they are paying you they will forget how to tie their own shoelaces.10 -
So I told my wife one week ago: "Yeah, you should totally learn to code as well!"
Yesterday a package arrived, containing a really beautiful hardcover book bound in leather, with a gold foil image of a snake debossed into the cover, with the text "In the face of ambiguity -- Refuse the temptation to guess" on it.
Well, OK, that's weird.
My wife snatches it and says: "I had that custom made by a book binder". I flip through it. It contains the Python 3.9 language reference, and the PEP 8 styleguide.
While I usually dislike paper dev books because they become outdated over time, I'm perplexed by this one, because of how much effort and craftsmanship went in to it. I'm even a little jealous.
So, this morning I was putting dishes into the dishwasher, and she says: "Please let me do that". I ask: "Am I doing anything wrong?"
Wife responds: "Well, it's not necessarily wrong, I mean, it works, doesn't it? But your methods aren't very pythonic. Your conventions aren't elegant at all". I don't think I've heard anyone say the word "pythonic" to me in over a decade.
And just now my wife was looking over my shoulder as I was debugging some lower level Rust code filled with network buffers and hex literals, and she says: "Pffffff unbelievable, I thought you were a senior developer. That code is really bad, there are way too many abbreviated things. Readability counts! I bet if you used Python, your code would actually work!"
I think I might have released something really evil upon the world.29 -
so I have a junior who merged in a fix for an issue yesterday, and it was tested today and there was an issue with his "fix".
so he comes to me and says "hey this is an issue" and i'm like "yeah, remember i told you about that yesterday when i tested your changes? why did it get merged?"
so i tell him "its because of <reason> and that's why i specified the approach that i did in the ticket originally"
so he's like "ok i'll try that" and before doing that i leave him with "you will probably want to do <thing> because of <reason> with that approach"
so fast forward to like 10 mins ago. literally half the fucking day has gone by.
"hey, so i can't get this to work"
"yeah its because <reason> but what you /can/ do is <same fucking thing i told him to do this morning>"
"oh ok, ill give that a shot :thumbsup: "
and yet he's had this chip on his shoulder since reviews because he feels like he should have gotten a bigger raise and he's worth more than he's paid. and wonders why after 3 years he still hasn't been promoted from a junior.
and don't fucking say 'that's above my pay grade' all the time like you aren't fairly compensated, and then struggle to employ the same fucking patterns in a code base you've worked with for 3 years now.4 -
- We need an android app. Can you do this?
+ Never done that, but I can try.
- Do you even know Java?
+ Not really, but I'll learn fast!
- Any OOP experience?
+ Well...I know CPP.
- 😐
- Will you give me a prototype tonight?
+ Don't know. How about tomorrow?
- Ok.
...
+ *makes a prototype in couple of hours, becomes a Java developer*
Just like that.8 -
IDK, man, it feels like the LB might still be caching. How 'bout throw yet another no-cache? Just to be sure.7
-
A few of you have used the big-screened TI calculators. Like 1 of those people knows I write demos for the monochrome 6MHz Z80 ones.
I have news for that person.11