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
Search - "biggest mistake"
-
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 -
Sooo, in my 5 years of high school, I had 5 different IT teachers...
Now, in Italy Highschool goes from 14 to 19 years old, I started programming some days after becoming 13, and "programming" classes begin on the third year, so I had quite a headstart on my classmates...
Now, for the third year, I had an awesome teacher, he noticed I was ahead and... Bored, so he gave me some extra stuff to study, he's the only teacher I've learnt anything from, it was awesome, very stingy with grades, but getting a perfect score with him was so satisfying.
Fourth year, the new guy was old, very old, at least 70, his lessons were just him talking about how programming was when he was young.
But then... During the second half of the fourth year I changed class due to bullying under a teacher's advice, and HE happened...
My new IT teacher, one of the most ignorant, awful people I ever met...
He's literally the reason I only went back to that school once, because another teacher needed help with a course...
One day I made the HUGE mistake to say that his "while(i <10000000000000);" wasn't very efficient for making a delay, because it didn't free the CPU, and since then:
- I never got more than 7 out of 10 at his tests
- He insulted me in front of the whole class
- He sabotaged the oral part of my final exam, shouting that he hated D'Annunzio when he saw he was in the literature part of my thesis (needed him to connect to WW2, and the Memex, that then allowed me to start talking about PCs and programming, my thesis was about the influence of lisp on modern programming languages), loudly chatting with other teachers when I was trying to keep calm (a teacher who knows me quite well, and was there to see my "performance" thought I was going to snap at some point), distracting the english teacher when I was exposing the english part of my thesis and pressuring the commission to give me 99 instead of 100 out of 100
So yeah, he almost made me hate the only thing I'm good at, undervaluing my work and my skills, undervaluing and humiliating me as a person, and I think that if I meet him again I might spit on his face...
So yeah, my biggest "programmer enemy" was a person that then did everything in his power to make my last year and a half of highschool hell
Now I can gladly say that with the help of my tutoring, some of my university colleagues are starting to appreciate programming, and my engineer friends ask for my help when they need advices about their code, and it's giving me motivation to keep doing it and becoming a better programmer to keep up with their expectations4 -
This is a rant I had 12 years ago but somehow forgot to post it.
In the middle of one of the biggest economy crash, I received an offer letter from a very big tech corp in NJ. This was my first job in 2009. I did all the hard part. 4-5 rounds of interviews, then graduated on time to waste no time and start my job.
On the first day, I went to HR finished orientation, got my laptop, started installing my regular tool chain. My manager was supposed to take me out for lunch and introduce me to the team. He came to my desk and said HR needs a copy of my passport as I am an immigrant and there is always additional paperwork.
HR tells me there was a very horrible mistake on their side and cannot hire immigrants for that role and need a green card/citizen. That was it. They apologized, took my ID card, laptop back and gave my passport back to me.
I took a yellow cab back to my dorm room which was I about to vacate in a week as I found a new apartment.
On that day I decided never to work for a financial organization again in my life.2 -
My biggest mistake in my life.
Boss: So when are you gonna finish this?
Me: I'll finish it today,
Me: Finishes task and submits pull request
- The Next Day-
Team Lead: Oh bro you gotta put this on a separate file, this change this too, and that, don't use that shit use this instead, oh and yeah, you can probally use this 'totally awesome typescript decorator' here for that.
Me: Refactors code intensely
Boss: You said this going to be finished yesterday
Me: FML11 -
TLDR: SAP sucks. Don't ever work with it. Run away from it. Delete it from your memory. If your company works with it, quit. It's the best you can do.
A couple of weeks ago the group rant was "Story of your best/worst career choice" and I talked about the contract I signed. Even tho that is still true and I still feel like that, I think I got a new worst choice:
WORKING WITH SAP.
When I got this job I knew it would be SAP, but I didn't know what SAP was. I just thought "it's programming, how bad can it be?" OH BOII.
If only I would have done some FUCKING RESEARCH I would know this would be a mistake!!
And I knew I didn't want to work with this, I knew I wanted to be a web developer, but I STILL ACCEPTED THE JOB OH MAN WHAT WAS I THINKING I'M SO MAD.
Were I live we all have the same mentality when looking for the first job, which is to just accept anything you can get, because it's your first job, you need to work and to get experience, even if it's a bad job or if you know you won't like it. When my intership was ending, I told my parents I didn't want to stay there because they treat their employes like shit, and the salary is terrible. They told me to still accept it if they offered because I still need a job (this one was web tho) and experience.
So, of course, since I was looking for my first job, was told this my entire live, always thought like that and they were the first to contact me, I accepted it.
BIGGEST FUCKING MISTAKE!! DON'T THINK LIKE THIS!! AND STOP TELLING KIDS THIS!! IT'S NOT A GOOD MENTALITY!!!
ALSO DON'T WORK WITH SAP! EVER!24 -
"We chose Android Native as our dev stack because we all got experience in Java"
- The biggest mistake I've ever made in a group project7 -
I just don't have words.....
Yesterday I had message from our CEO, that one of our biggest and most important project's CEO have told her that there is spelling mistake in my email signature and people there will judge because of that.
PS: I had Enginner instead of Engineer in such small font that even no one even noticed in entire year not even me.(I don't even feel ashamed for that it was not intentional and it does not make me bad at what I do at my work)
I just want to ask you guys are people really that bad they judge based on spellings? and not on work and their dedication?
I think there will be thousand of people who can't even speak or write English but are more innovative.11 -
Not a Story about an actual hack, but a story about people being dumb and using hacks as an excuse.
A few weeks ago my little cousin would reach out to me because "his Account was hacked...". Supposedly his League of Legends account was hacked by a guy of his own age (14) and this guy was boasting about it.
So i asked the usual things: "Has the email account been hijacked? Did anyone know about details to your acvount access? Etc..."
Turns out that one if his "friends" knew his password and username, but suppsedly erased these Informationen. And that was the part i didn't buy.
This was the point where he lost. Just because i am a programmer does not mean i can retrieve an account he lost because of a dumb mistake that could have easily been avoided. And that guy who was boasting about hacking LoL Account was coincidentally freinds with the friend who had the user credentials and password.
Moral of the Story? The biggest security weakness is almost always the user or a human in between... -
I recently got a project for scaling multiple wordpress sites for around 5k req/s
The biggest mistake I made is that even though it's wordpress I accepted it, fml!
Even aws load balancer gave up.5 -
Biggest mistake I've made in my life is assuming other people knew more than me and asking for advice and integrating their advice. I suffered many years being tortured by terrible advice that had no actual relation or usefulness in reality but caused me stress to have to follow, and I was too inexperienced to know any of this.
The other problem with bad advice is; how do you know it's bad advice? If you got the advice when you were naive, and you followed it, never strayed from it, you will still be naive in that area, because of the dutifulness by which you stuck to that advice. You literally imprison yourself, forever, especially if you are very good at putting effort in and have high conscientiousness, reliability. You will never know you were wrong.8 -
@Owenvii made a post over at (https://devrant.com/rants/2359774/...) and I want to write a proper response.
The biggest thing you have to look out for as a new dev is the jobs which you accept to begin with.
This isn't minimum wage no more, this is "big league", well, maybe not apple or google big league, but it's not $9.25 an hour either.
Basically you don't want to work anywhere where 1. your labor will be treated as a highly disposable commodity. 2. where the hiring manager doesn't know how to do the job themselves.
The best thing you can do is, if you're new, and just breaking through (and even if you're not), is ask them common questions and problems/solutions that crop up doing the work. If they can answer intelligently that tells you the company values competence (maybe), enough to put someone in place who will know ability from bullshit, merit from mediocrity, and who understands the process of progressing from junior dev to a more involved role.
It also means they are incentivized to hire people who know what they're doing because the training cost of new hires is lowered when they hire people who are actually competent or capable of learning.
Remember, an interview isn't just them learning about you, it's your opportunity to interview *them* and boy, you'll be making a BIG mistake if you don't.
Ideally you want them to ask you to pair program a problem. If your solution is better than theirs then they aren't sending their best to do interviews, and it tells you the company doesn't fire incompetents. The interviewers response can tell you a lot too, if they critique your work, or suggest improvements, and especially if they explain their thinking, that is an amazing response to look for, it says the company values mentorship and *actual* teamwork (not the corporate lingo-bingo 'teamwork' that we sometimes see idolized on posters like so much common dogma).
Most importantly, get them to talk about their work and their team. If they're a professional, it'll be really difficult to pry anything negative about their co-workers out of them, but if they're loose-lipped and gossipy thats a VERY bad sign, regardless of what they have to say.
Ask to take a tour and do a meet n' greet of who you will be working with. If they say no, then it's no thank you to a job offer. You want to take every opportunity to get to know everyone there, everyone you'll be working with, as much as possible--because you'll be spending a LOT of time with these people and you want to rule out any place that employs 'unfireable' toxic assholes, sociopath executives, manipulative ladder climbing narcissists, and vicious misery-loving psychopathic coworkers as quick as possible. This isn't just one warning flag to look out for, it's the essential one. You're looking for the proper *workplace culture*, not the cheesy startup phrase of "workplace culture", but the actual attitudes of the team and the interpersonal dynamics.
Life is really short, and a heart attack at 25 from dipshit coworkers and workplace grief can and will destroy your health, if not your sanity, the older you get.
Trust and believe me when I say no paycheck is too grand to deal with some useless, smarmy, manipulative, or borderline motherfuckers at work constantly. You'll regret it if you do. Don't do it. Do you fucking do it. Just don't.
Take my words to heart and be weary of easy job offers. I'm not saying don't take a good offer that lands in your lap, I AM saying do some investigating and due diligence or the consequences are on you.1 -
Joing a company was the biggest mistake i ever made!
Wondering what was wrong with my career as a free lance android dev that i decided to accept the project ???
All those beautiful days coding all day long without any stress or deadline now gone!
GONE !!!2 -
Am I the only one worried with the OS wars lately? Microsoft and Apple trying to gain even more control on everything and Linux remaining at less than 2% on the desktop. People are oblivious to the fact that their personal freedom is at risk, and don't you dare tell me otherwise. Companies knowing what we search or what files we have on our computer, having the ability to control us and force us to follow their rules. We have a choice, and I'm not talking about destroying the economical system a la Mr. Robot, but moving to the Open Source world, not because it's more secure, faster or some such shit, but because it's the only way to ensure freedom on one of the biggest part of our lifes, the digital part. My concerns may be exceeding the normal, and I'll hate it to be right, but I'm afraid that if this goes on, in a few years, we'll understand that we made a big mistake...21
-
My biggest mistake was that I didn't check the file extension of a uploaded file. Or more correctly forgot that I turned it off for debugging and pushed the app to production.
Somebody noticed an uploaded a hacker php script and got access to all the files on the server. Including some semi sensetive clients information.
A talk with the client that followed was not a pleasant one4 -
YikYak will probably be used as a lesson in app development on what not to do. They killed their entire app in a single release. Biggest mistake was never listening to their users.7
-
So im pretty sure I made the biggest/dumbest fuckup for the year already...
Deleting the majority of our RHEL server's root partition.
Blonde mistake for sure.
Technically i didn't actually delete it... just fucked up the block device so it's no longer recognised as existing.
I could go fishing for data and put it back together... but since i have the boot par and all the uset account configs... plus i actually documented all remarkable server updates cuz im trying to get better at the whole 'having a team' thing... im just gonna play it safe and go through it all like old school video games when you die right before the checkpoint so you need to go through the same paths again and again... but not too fast or youll fuck up somewhere easy and itll drive u nuts when u gotta reiterate again.
@jestdotty here you go. Always saying I just mention positives about myself... cant get much worse than this.10 -
Repeat/repost:
Unfortunately I do not own a drop of what is conventionally known as confidence or ego. It applies to everything; work, skills, relationships, friendships, you name it. I can estimate my chances of succeeding, and sometimes be pretend-delulu for a purpose (you gotta admit, sometimes showmanship is the biggest asset) but I don't understand confidence. In my opinion, it's just a gross overestimation of one's chances.
So this project/paper thing, I feel like I'm blind and running in the forest. I am not counting on my boss, nor am I counting on anyone in the dept to give me clarity or decent feedback. ("Cutting edge" research issues. Not anybody's fault.)
And I guess, in the worst case scenario the paper will be rejected, which would be a setback but not a full failure.
... Actually, that's not the worst case. The worst case would be someone running a peer review and finding that I made a tiny mistake and all my results are bullshit. 🤦
... Anxiety is eating me alive rn. 🤢4 -
Worst was with ionic and ios. Havent really worked with either and got mac that wasnt updated in ages and also they didnt give charger. Dealing with sudos and not using sudos then trying to work with xcode and free licenses took me a good time until i got first successful build for iPad. Biggest time consuming mistake was that i had to logout of itunes before i could make another account. It only gave me error and said try again later. Made me furious but after i got setup working everything worked quite nicely. Loved the safari developer view.5
-
I work for an big company that owns a social media website. One day I worked on the CSS of that side an changed...
[read more]3 -
Worst was getting head hunted into my current role at this terrific company.
Three months later I’m done with it.
It’s not shit shitty codebase, or the lack of direction that self governing teams have. It’s not the megalomaniac company owner. It’s the bullshit team mobbing and 8 hours of video calls a day.
The best part.
Come he’ll or high water I’m getting myself out before the end of the year.
I’d rather be busy and have f’k all chance of promotion than any more of this. At least the day will fly by.
Just hope I don’t make the same mistake twice, that’s become my biggest worry now. -
I did my biggest mistake of my coding life today (I've been coding for two months).
I did a program in my coding class. I said to myself : "I will try when it will be done". After 3 hours of coding, I finished the code. I tried it and... almost all of my script was trash. Best feeling ever.2 -
I subscribe to many copywriting newsletters. Here's an article that shows how it's like on "the other side", marketers struggle, too.
How Kevin's Massive Mistake
Completely Changed His Life
Kevin H. made a huge mistake.
The biggest, he would say, if he could tell you himself.
And he knew it immediately.
It was, he said, "instant regret."
Within milliseconds, he was asking himself "What have I done..."
Kevin, see, had just jumped the rail of the single most popular suicide spot in the world, the Golden Gate Bridge.
On average, the site gets another distraught jumper every two weeks. Kevin was one of them.
It wasn't like he hadn't tried to quiet the voices in his head. Therapy, drugs, hospitalization.
Time to die, those voices still said.
And yet, in the minutes his bus dropped him off at the bridge, he hesitated and paced with tears in his eyes.
"I told myself if just one person comes up to me and asks if I'm okay... if one person asks if they can help... I won't do it. I'll stop and tell them my whole story..."
But nobody did, so he jumped.
It was in those next milliseconds, he would later say, he knew it was the biggest mistake of his life.
He didn't want to die.
But now, he was sure, it was too late.
From its highest point, it's a 245-foot plummet into the icy bay waters below.
Out of the 1,700 people that have jumped from the bridge since it first opened in 1937, only 25 have survived.
Kevin, against all odds, would be one of them.
He slammed into the water like hitting concrete. Three of his vertebrae instantly shattered.
When he surfaced, he couldn't hold his own head above water. But, incredibly, a sea lion kept pushing him up.
The Coast Guard soon arrived and pulled him out.
From there, he began a long recovery that required intense surgery, physical therapy, and psychiatric care.
While still under treatment, a priest urged him to give a talk to a bunch of seventh and eighth graders.
Afterward, they sent him a pile of letters, both encouraging and full of their own pained thoughts.
He also met a woman.
Today, Kevin lives in Atlanta and he's been happily married for the last 12 years.
And he tours the country, sharing his story.
So why re-tell it here?
Obviously -- I hope -- you don't get lots of copywriters looking to snuff it after a flopped headline test.
Just the same...
We've talked a lot in this space about the things one needs to get by in this biz.
My friend and colleague Joe, over at the publishing powerhouse Agora Financial, likes to list requirements.
You need intense curiosity...
You need a killer work ethic...
And you must, MUST have... resilience.
Meaning, you must have or find the capacity to bounce back from failure and flops, even huge ones.
Now, again, Kevin's story is an extreme and in this context -- I hope -- a hyperbolic example of somebody giving up. In the worst way possible.
It is also, though, a metaphor.
See, I get a lot of notes from some of you guys... and at conferences, I get to talk to a lot of people...
And I often get the sense, from some folks, that they're feeling a little more overwhelmed than they let on.
Some are just starting out, and they've got a lot on the line. For some, it's everything. And some are desperate to make it work.
Because they have to, because their pride or livelihoods or a family business is at stake, because it's a dream.
And yet, they're overwhelmed by all the tips and secrets... or by piles of confusing research or ideas...
For others, even had some success, but they're burned out, feel antiquated, or feel like "imposters" that know less than they let on, in an industry that's evolving.
To all those folks... and to you... I can only say, I've been there. And frankly, go back there now and again.
Flops happen, failures happen. And you can and will -- even years and decades into doing this -- make the wrong choices, pick the wrong projects, or botch the right ones.
The legendary Gene Schwartz put it this way, according to a quote spotted recently in fellow writer Ben Settle's e-letter...
" A very good copywriter is going to fail. If the guy doesn't fail, he's no good. He's got to fail. It hurts. But it's the only way to get the home runs the next time."
Once more, nobody -- I hope -- is taking the trials of this profession hard enough to make Kevin's choice.
And believe me, I don't mean to make light of the latter. I just want to make sure we hit this anvil with a big hammer. To drive home the point that, whatever your struggle, be it with this biz or something bigger, that you don't want to give up. Press on.
As Churchill put it, "Success, is the ability to go from failure to failure without losing your enthusiasm."
Or even more succinctly when he said, "If you're going through hell, keep going."
Because it's worth it.
.
John Forde -
Sometimes I think that getting a degree was the biggest mistake I have ever done.
When professor wants to know why you did the work the way you did and you disagree as polite as you can, he calls you Arogant.. Like what the fuck, if you ask me 4 times why I did not expand the assigned task and I 4 times repeat that I want that shit as abstract as I can get. I already have it 5 times bigger as others god damnit, If you want me to focus on details, ask me to bring a tent..
A little bit of time later another professor assigns you a "Social network for schools"... Like wtf? U want facebook clone for free and in 4 weeks... What is this bullshit? You have mistaken uni for freelancer..
Because fuck you sideways... How dare you to have another classes?
Note for self... Next time open up a hotdog stand..1 -
I overheard this mid level dev discussing a new task with a senior dev. They're discussing compile error in cmake. I realized that the mid level dev asked so many basic stuff that are easily google-able. Mind you, our codebase is cmake based, how come she didn't know even the basics and yet survive in our company for years?
I felt bad for the senior dev, as I knew he's busy with his work. He couldn't do his job because he had to do hand-holding with this dev.
My biggest mistake is often trying to solve things by myself which will take hours instead of just asking a senior. But asking other dev for every little things are also annoying. Why can't you just google shit up or RTFM?1 -
I'm developing an app for a client, but they are responsible for the APIs.
Which turns out is the biggest mistake of my life...
I don't know whether data types are unknown to them or they are just playing a sick game with my emotions.
They have a different data type depending on how they feel, e.g.
- a boolean can be true, false, 0,1 or 2...
- an array can be an array or just a single item...
Who in their right mind can do this?4 -
So let's do a "community building" exercise.
What was your biggest tech pet peeve?
I'll start:
I hate it when people (especially teachers) give us a printout with a link to a website (like a good docs link) without shorting it.
I mean, we have to type out that 100+ character string of random numbers and letters. Then you make a mistake and have to retype it. (I.k,. First world problems)
Let's here yours. It can be about employers, teachers, or anyone else you can think of.3 -
The biggest mistake my colleague done is -
update query for admin_reports table without where clause in mysql in production db. Right after that no admin reports. More than 1000 rows affected.
Glad we luckily we have some data in staging machine.. I don't know Why TF our devops team not taking backup. Hope they will from now.
Nom I'm using python to dump the data from staging and save it local file and then export to production.
#HisLifeSucks
#HeartBeatsFast -
My biggest mistake was i'd ignore the whole documentation / flow how the new function should work on a existing module
-
The biggest mistake we all make right now is we get comfortable with the least level of effort during a time which has been made pointless