It feels stupid to see a simple google dork returning the list of your mistakes.

When your gf isn't a Dev but still tries to surprise you on your birthday with an HTML cake. But your OCD is killing you because of the mistakes

Src: IG - developers_team

This is some nevt level phishing. I wrote the guy who was listed in WHOIS an E-Mail, correcting his mistakes.

Dev: *Recieves email from manager with several typos/grammar mistakes asking to open attachment with strange name and click on tinyurl style link*

Dev: *Flags as phishing*

Manager: Hey how come you didn’t action my email?

Dev: That was actually from you?

Manager: Yes.

Dev: …

Code Completion. Face it, you would've probably made a lot of mistakes if you didn't have it.

It was great to see Gitlab not only being transparent, but also being so empathetic towards the employee and not bashing them at all. Instead they said the more things you do the more mistakes you make. And the system/process should have contingency so that human mistakes have some tolerance margins.

That is a great workplace!

"A computer lets you make more mistakes faster than any other invention in human history, with the possible exceptions of handguns and tequila." - Mitch Ratcliffe

That moment when your too busy and concentrated programming and your wife asks you for the credit card and you give it to her .... to later realize she never cam back with that glass of juice and you remember today is black Friday..... ohh shit!! 😲

Aaaah...I just got back from a meeting because of a production data problem caused by an analyst who keeps making mistakes that screw up client data. I wrote a program to automate most of it and everybody initially accused me of having a buggy program, only to find out she wasn't using it, never did.

"Why aren't you using the program then?" was asked. "Oh, well, I just understand my way better," she replies, "When I make a mistake at least I understand why."

Pause....

"Then, um, if you know you're making a mistake, why don't you fix it?"
"Because my process is so manual and labor intensive sometimes it's not worth it to go back and fix it, because I'd have to do everything over again, and you guys are much better at fixing this stuff than I am."

I indicated that everyone is too busy to stop and fix her mistakes, to which she then asks:

"So if you can't fix my mistakes, what am I supposed to do?"

I am not experienced enough to make sins, I make mistakes.

Whenever I feel bad, I go and help random people with their code.

I also randomly offer to help teach people Java so that they can learn best practice and perhaps not make the same small mistakes.

Such is life. My method of coping with sadness.

For the small mistakes 😉

Client said: "And you promise there won't be any caterpillars in the app...",I gave him a strange look, he continued: "or how do you call that mistakes in apps".

He meant bugs...

Learning javaScript on monday
Damn

This is for all the developers out there. Keep learning and keep going!

"No matter how many mistakes you make or how slow you progress, you are still way ahead of everyone who isn't trying."

We all make mistakes, right Google?

1) Give every challenge a try.
2) failure is always an option.
3) learn from your mistakes.

This is like the hundredth time that I fucking forgot the motherfucking "s" for "props" 😠😠😠

It is fucking props, props, props

That you should always admit you make mistakes and learn from them, instead of acting like you know everything arrogantly.

Appreciate how lucky we are. We get to say "It's a bug" instead of "I've made mistakes". Suddenly it's not our fault.

"An experienced developer is one who doesn't make any new mistakes, but repeats the same old ones over and over."

When I find silliest mistakes in my code :|

My dear diary,

Today, the guy that convinced the boss to completely replace our functional CMS website (marketing used to update it) with a static one he was writing from scratch in PHP + jQuery, has published our MailChimp Api Key on StackOverflow, because he couldn't make the API to work.

Boss didn't complain, but I don't think he understood what happened. Just asked the guy for not doing that again.

It was a crazy day.

At my old job, me and a colleague were tasked with designing a new backup system. It had integrations for database systems, remote file storage and other goodies.
Once we were done, we ran our tests, and sure enough. The files and folder from A were in fact present at B and properly encrypted. So we deployed it.
The next day, after the backup routine had run over night, I got to work and noone was able to log in. They were all puzzled.
I accessed a root account to find the issue. Apparantly, we had made a mistake!
All files on A were present at B... But they were no longer present at A.
We had issued 'move' instead of 'copy' on all the backups. So all of peoples files and even the shared drives have had everything moved to remote storage :D
We spent 4 hours getting everything back in place, starting with the files of the people who were in the office that day.
Boss took it pretty well at least, but not my proudest moment.

*Stay tuned for the story of how I accidentally leaked our Amazon Web Services API key on stack overflow*

/facepalm

> Amazon like website - 9 dollars
> Webdev homework. - 50 dollars
> Spelling mistakes. - have no price

Freelancing can be so bizarre, I'm 50 bucks wealthier now tho.

Nobody proof reads anymore. It pisses me off. News sources with obvious spelling and grammatical mistakes. It seems that it is acceptable on the internet to not give a fuck.

!rant

Finally finished the blanket I’ve spent a month crocheting without a pattern after teaching myself to crochet at, like, the beginning of the month. It’s huge (this is it laying on a King sized bed) and I made so many mistakes that seem super obvious now, but I’m still weirdly proud of it.

"Senior Engineer/Dev/etc." is just the title for the guy who's learned from making the most mistakes.

SELECT * FROM VISA_CARDS

...yes, every bit as bad as you imagine

(and yes, there were other tables for other card providers. Insult to injury... in like.. a fractal of mistakes)

I’m so tired of egocentric lying management executive types.

Executive: You should be thinking about how you speak to the “leadership”.

Me: How about stop lying, blaming me for your own mistakes, and then blackmailing?

Guy has never heard ‘no’ in his life.

Seriously, иди на хуй.

Paycom is utter dogshit.

Clunky, error prone, junior mistakes on every page, and filled to the brim with HR doublespeak and legalese.

A roving gang of quadriplegic interns could do a better job if the requirements were written in cuneiform and they were paid, up front, in cocaine and whiskey.

Don't be afraid to make mistakes, they're the key to learning code/anything.

A wise man once said:
"The only difference between a master and student, is that the master has failed more times than the student has even attempted"

There was a time I made an update on one of our client's e-commerce website sign-up page. The update caused a bug that allowed new users to create an account without actually creating an account.

The code block meant to save user credentials (i.e email address and password) to the database was commented out for some reasons I still can't remember to this day. After registration new users had their session created just as normal but in reality they have no recorded account on the platform. This shit went on like this for a whole week affecting over 350 new customers before the devil sent me a DM.

I got a call from my boss on that weekend that some users who had made purchases recently can't access their account from a different device and cannot also update their password. Nobody likes duty calls on a weekend, I grudgingly and sluggishly opened up my PC to create a quick fix but when I saw what the problem was I shut down my PC immediately, I ran into the shower like I was being chased by a ghost, I kept screaming "what tha fuck! what tha fuck!!" cus I knew hell was about to break loose.

At that moment everything seemed off as if I could feel everything, I felt the water dripping down my spine, I could hear the tiniest of sound. I thought about the 350 new customers the client just lost, I imagined the raving anger on the face of my boss, I thought about how dumb my colleagues would think I was for such a stupid long running bug.

I wondered through all possible solutions that could save me from this embarrassment.
-- "If this shitty client would have just allowed us verify users email before usage things wouldn't have gotten to this extent"
-- "Should I call the customers to get their email address using their provided telephone?... No they'd think I'm a scammer"
-- "Should I tell my boss the database was hacked? Pffft hack my a**",
-- "Should I create a page for the affected users to re-verify their email address and password? No, some sessions may have expired"
-- "Or maybe this the best time to quit this f*ckn job!"
... Different thoughts from all four corners of the bathroom made it a really long bath. Finally, I decided it was best I told my boss what had happened. So I fixed the code, called my boss the next day and explained the situation on ground to him and yes he was furious. "What a silly mistake..!" he raged and raged. See me in my office by Monday.
That night felt longer than usual, I couldn't sleep properly. I felt pity for the client and I blamed it all on myself... yeah the "silly mistake", I could have been more careful.

Monday came boss wasn't at the office, Tuesday, Wednesday, Thursday, Friday not available. Next week he was around and when we both met the discussion was about a different project. I tried briefing him about last week incident, he seems not to recall and demands we focus on the current project.

However, over three hundred and fifty customers swept under the carpet courtesy of me. I still felt the guilt of that f*ck up till this day.

Why can't we just fucking use Ctrl + Z for our life mistakes?

When you spent the whole day programming in Swift and your mom says that she fucked up her windows 7 machine and you gotta make a clean install (I hate fixing stupid mistakes made by non tech users)

1. My senior told me that my code is crashing.

2. I check the code and told him that it is not my doing. As there was lots of nested if-else as I prefer to keep a variable and update it in if conditions. Like a filters rather than trees with branches. What I say, I knew my coding style.

3. Then he show me my git commit and I am having existential crises.

Am I missing days? How can I? I mean was I abducted and in mean time some alien took my place and they placed this memory of me coding?

Ah! man I think I am possessed by some inexperienced developer. I seriously need some fucked up crash to exorcise him.

Every year my team runs an award ceremony during which people win “awards” for mistakes throughout the year. This years was quite good.

The integration partner award- one of our sysAdmins was talking with a partner from another company over Skype and was having some issues with azure. He intended to send me a small rant but instead sent “fucking azure can go fuck itself, won’t let me update to managed disks from a vhd built on unmanaged” to our jv partner.

Sysadmin wannabe award (mine)- ran “Sudo chmod -R 700 /“ on one of our dev systems then had to spend the next day trying to fix it 😓

The ain’t no sanity clause award - someone ran a massive update query on a prod database without a where clause

The dba wannabe award - one of our support guys was clearing out a prod dB server to make some disk space and accidentally deleted one of the databases devices bringing it down.

The open source community award - one of the devs had been messing about with an apache proxy on a prod web server and it ended up as part of a botnet

There were others but I can’t remember them all

Everyday I wake up, I just think where did humanity go wrong? What mistakes were made? How the fuck did we end up with IE? And why do people still use it?

!rant
Just finished my CNC.
Lots of problems but it works... More or less.
Need better steppers and other drivers. But I did it, learned a lot, did lots of mistakes, and don't get me started on debugging hardware...
Z axis unfortunaly can't even pull the motor up lol.

FUCK! agshdklgdahgisdahl;k!

I just spent 45 FUCKING MINUTES debugging try to figure out WHY THE HELL a function that is supposed to return either a pointer to a valid object OR ZERO if a valid object is not found, was RETURNING FUCKING EIGHT!

Then I saw it... I typed:
nodeList[index];
instead of:
return nodeList[index];

It took me looking at a stack trace and a disassembly of the function to realize this.

Can't wait for this three-day weekend...

It officially happened...
Accidentally used rm -rf /*
(Actual command was a bit more involved, but it did pretty much the same thing)

Laptop doesn't boot now. Saved my home directory though.

Hooray.

A tip to tech folks from my personal xp.

If you fuck up and make an impacting mistake in your company, like taking PROD down, noone is going to fire you on spot. Assign some more mandatory trainings - maybe. So you'd be more careful next time.

See, it's not worth getting rid of someone who made a mistake. You should be seated down and insisted to fix it. If you don't - then they might consider firing it. If you do fix it [with help or alone] - you become a more valuable asset to the company as you prove you are responsible for your actions and you take it seriously. You show that you can clean up your own shit and you don't need a babysiter next to you.

If you simply make a mistake and they replace you with someone else, that someone else is likely to be unaware of your mistakes and is doomed to repeat them. It's just bad for business.

Ofc if you making mistakes becomes a tendency rather than an exception, it's also a red flag for the business.

Don't get too laxed! And always answer for your shit. Never hide a fuckup - always alarm about it asap so that corrective actions could be taken by respective organs of the company while you are fixing it.
Come up with an action plan, announce it. Estimate resources you need [like help from others] - announce that too. Update concerned parties every half an hour or so about the status. If you find you need anything else while fixing it or you come across some blockers/delays/change of impact - always announce asap. Do avoid false alarms and disinformation.

// inspired by someone's rant today

I think in this field mistakes at low level are easy to miss and can cause big problems later on

I used to think my coworkers are stupid. Now I believe they are purposely making mistakes just to piss me off.

The best thing about being a consultant is that you keep learning from the mistakes of people who follow your advice.

tfw you compile another time cause even though the code doesn't run, you're sure you made no mistakes

I was about to use the Duolingo but I think it triggered me to hard. 2 mistakes in a row.

1. I have Portuguese origins and they used the Brazilian flag

2. I was born in Luxemburg and they just used our flag for The Netherlands (I know they're pretty similar but cmooooon)

We all make mistakes

Mark admits to mistakes on Facebook

Remember people:

If you never make mistakes, nobody will know what you do in a company.

#storytime When I was in my apprenticeship and learning to code I often did make the same mistakes over again so my colleagues and I found names for them and they just had to say 'potatoe sack' and I knew what was going on. It actually help to never make these mistakes again #throwback

!rant
Our biggest mistakes are the ones we never committed 😔😔

Men. Live with it.

(Stupid mistakes that kept me from sleeping.. 🤦🏻‍♂️ Lesson learned: Sleep.)

“One of the biggest mistakes engineers make is spending time on optimising something (a component) that shouldn’t exist in the first place” - Elon

I’ve been guilty of this a few times 😅

Lately in school...
A teacher of mine tried to put an HDMI Cable into an USB-A Port. How can you screw up something like this? It's as simple as a geometric puzzle like the one in the picture. Apology for my grammar mistakes.

We need to be learning from other's mistakes. A good weekly topic would be "a time you really failed as a dev, and what you learned".

* had to share * read it on a tutorial website *
Remember that everyone makes mistakes.
Programmers are like magicians who fool everyone into thinking they are perfect and never wrong, but it's all an act. They make mistakes all the time.

I did some grave and irreversible mistakes in my life

- Never gathered enough courage to mingle with women when I was younger and now the hope is lost

- Compromised my values and mental wellness when I met a narcissistic bitch

- Did not invest money wisely when markets were sailing low and allowed that good sum to sit in bank

- Did not plan health and term insurance at early age when premiums could have been low

- Out of fear, did not follow my gut to purchase gold because my father was acting crazy (or else my money would have been doubled)

- Did not plan my taxation well (or until now would have paid almost zero tax)

- Did not define strict boundaries and allowed people to overstep (or else I would have better friends and family relationships)

- Did not quit my job early and stuck with low paying shit with negative learning, for years (or else I would have grown exponentially)

Thankfully few things I did right are, spending more time with my mom and learning from my mistakes.

I hope I don't make such stupid life choices again.

- hold yourself accountable for your mistakes
- keep track your mistakes and learn from them
- put thought in what you do
- be organised
- become comfortable asking for and offering help
- realise that some problems have no universal solution
- don't just copy what others do, but also think for yourself
- learn to be patient

During interview...

Interviewer: Do you know what is JQuery?
Applicants: Yes?
Interviewer: what is JQuery?
Applicants: am.... (in a couple of minutes thinking, the right answer that could be)
Applicants: JQuery is Java Query?

a pretty honest mistakes where the applicant do not know the answer and looks confident during interview

#AgileTip: Hiring smart people is pointless if they aren't allowed to make any mistakes.

...and I just deleted 2 tables of client data 😮😭😭😭 😑

Leave no stone unturned. The biggest mistakes are the silliest ones

Developers too lazy to google search/read the README.md yet too proud to admit their mistakes.

They create disasters that I need to clean up later because they took a vacation.

Tried thinking of worst coding mistake ive made....realized how many there were....shivering...

Small design flaw maybe...

Worst advice about programming...
My discussion with my company sistem admin :
Me : you must always think that users are dumb and will make mistakes (like putting letters when db saves as number)
He : users must learn, if they make such mistakes its their fault.

My claim: I learned early in school to always assume that users are stupid and will always find bugs and exploits by coincidence. So protect your code from bad imput

The final verdict is out. After almost 3.5 years im getting fired. Im relieved because i’ve been expecting this already since december. No matter how hard i try my mistakes aren’t excepted anymore.
Good thing there are three other companies i have interviews with.
Let’s hope for a new offer and smooth transition soon!

Who else has done it.

Today at work I found this in the code...

if (argCount < 2 && argCount > 3) {
// log invalid arg count
return;
}

And this passed code inspection and has been sitting there unnoticed for about a year and a half... 😂

Whether it's mixing up and with or, or forgetting a semicolon, we've all done it at some point! 😊

I was watching Ryan's talk on YouTube about "10 mistakes he regrets in Node " then on a point about node_modules he pulls this one up 😂

By still having the balls to continue making mistakes and learn from them

I'm having a Linux crisis... Do I reinstall arch linux and fix some of the mistakes I made... Or do I go back to the warm comforting boosum that is Ubuntu...

Fellow web developer loves to blame any css mistakes on the users "browser" or my favorite, "oh that must be a PC thing it looks great on my Mac"

*Facepalm*

Making mistakes

Using a library with a terrible API.

Manage to convince management to purchase new library.

Using new library.

Slowly creeps in that new library has a terrible API.

University, Italy
We have sent our code to the professor for correction.

Professor : Who wrote the code with comments in english?

Proud student : me !

Professor : you failed to write the algorithms, and also made mistakes with a lot of English words.

Failure is not the problem.

Problem is not admitting and accepting that you failed.

Problem is not learning from your mistakes.

Problem is causing the same damage over and over again.

What's worsens the situation is defending the dumb act.

If you cannot handle failure then not only you stagnate your growth, but you also negatively affect people around you.

Mistakes make you perfect only when you fix them.

Do you ever wonder if you got promoted to senior developer too early? I keep making stupid mistakes that get picked up by more junior developers at code review I need to up my game

What are some mistakes you can make as a programmer that will get you fired immediately?

People:
- human brain is imperfect, makes too many mistakes
- let's make a computer that could perform perfect precise calculations
- computers are imperfect, require a set of clearly predefined rules [by human] to operate
- let's create a computer that behaves like human brain - an AI
- ...

Guess what's gonna be the next entry :)

An expert is a person who has made all the mistakes that can be made in a very narrow field.
Niels Bohr

Failed my driving exam for having turned right instead of left.... FYI this examiner always fails 90% of students for minor mistakes like this... wasted money and time but oh well, new chance next month!

>Gets a new CPU for desktop (yay, went from R5 1600 to R5 3600X)
>Spends half a day flashing new MB BIOS (Needed to flash individual major versions in order, couldn't just go 1.10 to 6.40)
>Finally finishes preparations and goes to replace the CPU
>Cleans the old one and packages it to give it to a friend
>Has issues inserting the new one as the orientation arrow on the motherboard was very hard to make out
>Spends 30 minutes applying thermal paste, worrying about optimal spread
>Forgets which side the CPU fan goes on
>Finally boots back up... CPU fan is suddenly loud AF under load, but eh, temps under stress are sub-60, so, good

~~Next day~~
>Loud CPU fan is too annoying, opens the case again
>CPU fan is on backwards
Ugh
>Takes the fan off, turns it around and fastens again, puts PC back together and boots
>Is quiet again, nice
>Goes to work on the PC
>2 hours later randomly checks temps because no fan noise is weird
>CPU at 75dC, crap
>Opens the (live) PC, CPU fan is not spinning
>Has put the header on one pin to a side
>Unplugs and replugs it correctly
>Fan suddenly starts spinning very fast and cuts my finger
>Finally closes the case once more. All issues resolved

...Its situations like these that make me wonder... What would happen it I had to work with servers in person, physically lol

So I was logging into google today and my password is very long so I often make mistakes while typing it so I went to inspect element to change input type to text so that I can check the password and I see that Firefox is storing my password already as plain text. Wtf Firefox???

Hooked up a monitor directly to a server that wouldn't boot. Fixed the server. Unplugged the server instead of the monitor. At least it was already out of the load balancer? Oops.

How could this happen to me
I made my mistakes
I’ve got no where to run
The night goes on
As I’m fading away
I’m sick of this life
I just wanna scream
How could this happen to me

!rant

Just wanted to share this beautiful development miracle. Hello Games has proved to us that it's never the end, and you can always come back to fix your mistakes as long as you don't give up on yourself. Follow your dreams motherfuckers :D

Apparently I'm not dishonest enough about my mistakes owing up to my mistakes too much when interacting customers. Fuck me for being honest, I guess?

Mistakes by startup...

We are probably reading alot of "this co-worker was so bad because blah blah blah..." from people who actualy were the real shitty co-worker and are still blaming others for his/hers mistakes.
Not a week rant that i can trust...

I just want to make it clear to all of us here...

Not every goddamn thing is a bug from X or a bug from Y most of the time I, Us, We as programmers fucking make mistakes or don't know the issue because it's vague!!! IT'S NOT A FUCKING BUG!!!

YOU ARE YOUR OWN TEACHER. The failures I got in the past , failed to build a simple app , I get to where I am today because I failed many times.

My best teacher for this will always be my mistakes , my mistakes are the greatest teacher

Scrolling through devRant, seeing spelling and grammatical mistakes, feels at 127.0.0.1

ChatGPT implementation details leaked !!!

This explains everything:
- slow response typing
- occasional nonsensical answers and factual mistakes
- delays before answering
- sudden and random network errors
- "servers" over-capacity
- responses with an Indian accent

Being non existant.

But at least he won't do any mistakes that way 😀. (I'm so lonely in this city!)

people always complain about semicolons but I don't think I've ever had a semicolon issue cuz of ide's. but I'm plagued by tons of other stupid mistakes, like forgetting to initialize my ArrayList<>'s in java from null to empty..

I just wrote a function that creates a configuration struct that is stored in a Singleton struct, but to create it I called the Singleton to get a connection to the database.

This created an infinite recursive function that maximized connections on the database, as the Singleton never got fully initialized. Not a good idea.

So to fix this I created the configuration after the creation of the Singleton, still calling the singleton from within the function. This worked.

Then I remembered that I could have just passed the connection as a parameter to the function. Like I've done a million times before...

It's time for the weekend, I need a break

Stop putting spelling mistakes into code!

i remember doing this stupid thing in java which would instantiate some object every frame or something like that which would make your computer run out of memory in a few seconds

do you want to know what my genius solution was

run System.gc() every frame

i was like 8 fucking years old i didn't know what i was doing

Have to finish this code today but only slept four hours last night, coffee isn't working anymore, making the most stupid mistakes and constantly dreaming away while looking at my screen because I can't focus anymore. Also, it's around 25 degrees here and the vents aren't working that great... fml.

Fast Internet connection always distracted me to streaming youtube about technology or tutorial, but normally end up with 100% unrelated videos like how to sharp your knife using mug or watching top 10 mistakes in Harry Potter 😖😖😖

You know what really pisses me off?

Arrogant/Condescending people doing rookie mistakes.

If you are like that but delivers I suck it up and let it go, but if you don't? Lol... Be ready for the shitstorm.

That moment when you start spotting mistakes in blog articles regarding some new topic you're currently studying

Looking at my SO questions from 5 years ago, and still making the same mistakes now...

!rant

I see a lot of crap about junior vs senior devs nowadays. I think the distinctions are small.

In reality senior devs have been burnt more in the past by their own mistakes or have seen mistakes by other people. That's about it.

What other distinguishing characteristics have you found?

A colleague just committed his username and password in git. When I kindly informed him, he told me that there are a lot of things on whiteboards around the office that should not be there. Oh, if that's the case, committing your credentials to git is fine.

We all make mistakes. But your response to them is everything.

Developing a notification API, sends emails to subscribers, email API can take only 100 IDs at once, so partitioned the email list and send mails in blocks of 100.

Forgot to reset the list after every block, so each new partition got appended to the existing list and kept going on.

Ran it against a test DB, which was recently refreshed with near-prod data !!! Thousands of emails went out of the app server in one shot and everybody receiving numerous duplicate emails. Especially the ones in the very first partition.

Got an incident raised by the CEO himself reg the flurry of emails. But, things were out of our hands, quite literally. All emails are queued up in the exchange server.

Called up the exchange server team, purged​ the queued emails. No other emails were sent/received during this whole episode.

Thanks to Iterables.partition in the present day.

Backend API developer that doesn't admit his mistakes. Damn, he's annoying the whole team.

Basically crashed the whole app by messing up the settings for the CORS policy, and still doesn't admit it. When he fixed it, the only reply we get was "I erased the thing and put it back and it works".

WOW!

AWS write awful docs. The .Net SQS example code has spelling mistakes, bits missing and doesn't work.

Also would be helpful if it highlighted that the .Net Core implementation is fundamentally different.

Jerks.

The moment when you edit your code and run it but nothing changes and you try looking for the mistake in yor code but the only mistake is that you forgot to compile it first...

Management: Our internal app must be 100% rigid so that we users follow predefined process flows exactly so no mistakes are made while also being 100% flexible so that users are free to go about their business in whatever way they feel is appropriate for their own unique needs. These are the requirements!

Dev: …

Any tips for a Dev who never contributed to an open source project before? What sorts of mistakes do first time contributors normally make? Most importantly what can I do to not annoy* fellow contributors?

!rant && Thanksgivings++

I am truly thankful to be a programmer for it is the only job on Earth where doing mistakes is the profession itself.

Think about it. We make more mistakes than other professions on DAILY basis. If a doctor miss a step during a diagnosis or an operation, a fucking human being might die. Engineers, lawyers, teachers you name it. They are not allowed to make mistakes.

Us? We are earning money from other people for all the hours we spent fixing the mistakes which we made in the first place.

Not a rant but I spent 30 minutes writing a fix for 2 integration tests while screen sharing. Ran the tests and they both pass first try, no exceptions, typos or silly mistakes. 2 additional unrelated tests also started passing. It felt good.

"Learn from the mistakes of others. You can’t live long enough to make them all yourself. " - Eleanor Roosevelt

Man, making scripts for random shitty tasks is so god damn nice. Like pushing a new version in a repo. Throw together a script to find metadata and kubernetes files and identifies and update versions automatically, then commit, tag and push. Simple script, not even 100 lines of bash, but saves so many silly mistakes.

My foolishness of giving into an almost impossible dream seems to be finally setting in.

So the client, who is also my relative is launching an hotel. He wanted a website for the hotel with booking facility. The budget was plenty for that requirement and I was okay. In my calculations 20% of the proposed budget seemed fair to charge.

Few months in, it turns out he now wants a hotel booking platform where other hotels can also be listed. The reasoning was he wants to avoid the commissions charged by popular booking sites and also feature his own hotel in the booking platform that was about to be build.

I was skeptical about his intentions and my skills in developing it. I was also concerned whether he understood the responsibilities and overhead costs of running such a platform. He talked like it'll be fine. I calculated my billing to about 50% of the budget. I left the other 50% intentionally because I knew it would need for keeping up the site.

Time goes by, i am now 90% into completion of the new requirement.

Few weeks ago, i had informed about server pricing and I quoted a starting price of $15 per month. He seemed quite shocked. His reaction shocked me too and I got concerned whether I would even get rest of the payment ( already got 10% of proposed budget ) as advance.

Just few days ago, he now has a new requirement. He wants to show the hotel pricing from the booking site in Google Maps search. I tried to understand him that those are Ads and I was pretty sure price of running those ads are beyond his budget and probably negate any savings he is trying to make by competing popular booking platforms. Signing up for Hotel Ads as a booking platform is quite challenging. I don't think it'll happen.

I am now concerned he might bail on the project, so I have not informed yet. I just hope I get paid for the work I done and I'll inform then. :P

Anyways, the journey of it's development was quite insightful and challenging experience. I fell in love with a language I knew existed but never really bothered about and a framework whose only thing I knew was that it's name sounded cool to say.

The problem with sawing laminate is that there is no ctrl+z.

1) Apply Vue.js to a real life project
2) Make a CMS for a private school (unluckily, they don't want a standard CMS)
3) Learning wisely of the mistakes I made this year with clients ("what if we added this?")

Relentless, thankless routine of coming in every day and everybody hating the software team despite working our ass off to help everybody and fix mistakes that upper management has caused.

Duolingo used to be better. New updates and restrictions are shit. Specially the whole "take a heart away for a mistake, five mistakes and you can't use the app for hours". Like, I get it, you couldn't manage the traffic. But this is ridiculous. Also, where did the lesson overviews go?

Common mistakes(choosing programming is one of them)

No matter how frustrated I get, I always try to remember: Machines don't make mistakes

Thank you, instagram, for making me feel better about my programming mistakes

I get that people mess up sometimes but their mistakes make it in to production...

When you realize that the solution for a bug in your code is putting
if (somecondition)
but then you put
if (!somecondition) by mistake and try to figure out why is the bug still there :-(

Why can't every programming language have the same syntax? Imagine how many fewer mistakes you would make...

I'm currently at this state:
I'm balancing out two things!
- being an idiot and doing obvious mistakes.
- being skilled and creating smart tricks to speed up development.

Everytime I learn more tricks I also get more opportunities to do obvious mistakes.

I became good enough to be hired as a developer by reinventing lots of wheels and making mistakes. A lot of mistakes.

Moving to camelCaseJava from underscore_c and it peppers me with silly mistakes.

Beginner mistakes?
Putting two single quotes together instead of a double quote

Scared Christians like to say “God doesn't make mistakes” when discussing trans people. Well, you're right: God doesn't make mistakes, so he made me trans to test your ability to love.

Want to read a book that can help me avoid newb mistakes and can help me write beautiful code ?

Pragmatic programmer(1999)
Or
Clean code
Or
any other book ?
Help me !!?

I am bad in english. and good in code. I do many mistakes in my rants and comments.

Sorry Advance.

On other hand. I am cool headed person. so I never mind about things.

It's a real nice feeling when you figure out the answer to your own stackoverflow question as you're typing it out.
Not gonna make myself look like an idiot this time! No-sir-ee.

Just made one of those mistakes so obvious that you can't find it for 3 hours

That feeling when you’ve got a reputation of preciseness etc, and the code you just submitted for review has so many silly little mistakes you just want to do that ostrich thing. Gosh, how can I suddenly suck at my job this bad?

Okay, the changes affect EVERYTHING in our codebase (a major change in core business logic), and there is no way I could’ve tested every possible case by myself without a decent coverage of automated tests - which we obviously don’t have. So yet another argument for it (damn management, won’t you listen?!)… but still, some of the mistakes found during code review make me seem like a complete idiot.

Even Google can make mistakes.

go to gmaps.de and have fun with an nginx error sponsored by big G.

Normally, it should redir to the Google Maps page

Remember my friends

Fuck 2019. I still have one photo of 1/1/2019 on my instagram profile as my first photo with hopes to achieve what i was planning to achieve. But life happened. Things went wrong. Murphy's fucking law took over. Fuck you

Start fresh 2020. Learn from the mistakes. Expect more mistakes because they are inevitable. But do your best to NOT repeat the old ones.

We are going into the new decade. No more 201X year.

-Delete all negative energy
-Cleanse all BULLSHIT
-Remove everything weighting you down
-DETACH FROM THE PARASITE PEOPLE
-Stay with the real people
-Stay with family

2 more weeks until 2020

🙏🙏🙏

Poking at Linux is like playing with fire. You think you've got the hang of it, then a load of smoke happens.

I did a lot of mistakes repeatedly. I want to restart life. Seriously!

When you're dead tired and keep making stupid mistakes...
git commit -m "ugh..."

Told to sanitize a large collection of PowerPoints of customer data. Found one resolvable IP address and about 200 typos and other mistakes. Deleted the IP address.. mission successful!

Religion is ruined by people.
God's bugs are our mistakes, the platypi, and turtle penises.
Nature is so much better without us, I enjoy programming but the users are polluting, wasteful, selfish useless beings removing resources from the Earth.

Sometimes I want to become a hacker and ruin rich people's lives.

The reason why I like to code alone in the dark is so that people cannot see my dumb mistakes such as 'forgetting to hit run after compile and wasting 10 min wondering why my code didn't show on the console'.

: /

Git is good. Even when I do stupid things like reset a commit I wasn't supposed to, it gives me the chance to fix those mistakes.

(Oops. !rant)

By pointing out everyone else's mistakes

It makes me feel good to hear of all the mistakes people make - reminds me that if I make a mistake its actually not as bad as I think 😃

Sometimes you just make the stupid mistakes

My team mate is so fucking bad that I use his mistakes as interview questions for internship positions. So I really make sure I don't have a second Ouistiti in my team.

I have made 2 mistakes today.
1. Upgrading from Fedora 23 to 24 on a busy work day - it's taken over 2h now...
2. Trying to switch to a new TTY and launch GDM while it's updating - I now cannot see anything and live in fear of restarting.

Conclusion don't try and be clever with Linux, it will win

Don't be afraid to make mistakes. Making mistakes is the only way to learn from them and grow. F*ck sh*t up and build it back up again but better. Fall seven times stand up 8!

So my senior visited some of my very old code today to make some changes on his own, then asked me to explain flow since he wasn't understanding it.

Me after looking at code for 2 minutes:
"When I was writing this, only God and I knew what it meant. Now, only God does."

At last the moment of UPDATE with no WHERE came for me

By making mistakes

That joy of finally having them all passed.
I had stupid mistakes like: insertNewItem, but inside I use update T_T

project still fairly new, but this time I decided to write unit tests as I go instead of delaying till the end and writing nothing lol

Even seniors make mistakes. In case you were ever doubting yourself - just remember that.

I just had a very senior level programmer on my staff add a function to a production system that issues an SQL UPDATE query without a WHERE clause. Fortunately, only the 1st entry succeeded and the rest failed due to "duplicate record" errors. Clearly he had intended to do a SELECT to check if an entry was present. If it was present, do an UPDATE, otherwise do an INSERT (think UPSERT - but done manually). However instead in the insert part they were both UPDATE's. The first update was normal looking but the second UPDATE was just this weird malformed-looking thing where he tried to do an UPDATE but to every field including the key fields. Clearly he was thinking about an insert but actually writing it as an update. Every now and then I need to remind myself that these things happen. The guy's not dumb - just made a mistake.

I'm just happy it "failed unsuccessfully".

Just for fun

"Mistakes are the portals of discovery. " - James Joyce

Someone once told me the following:

Processors, as good as they are, will always make mistakes.
When processors (i3, i5, i7, ...) are tested before distribution, they are categorized on the amount of mistakes they make. An i7 7700k for example which makes very few mistakes is labeled as a 'Type A', while another i7 7700k with the exact same name and specs makes a little bit more mistakes, and is labeled as 'Type B'.

All the 'Type A' processors are used and sold in business class laptops and workstations while the 'Type B' ones are sold to consumers.

After some research I couldn't find anything on it on the internet.

Anyone know if this is true or straight up bullshit?

I upgraded eclipse with devStyle. The next time I started eclipse a quote showed up. I'll post it here 'cause I think it's totally true:

"Experience is the name everyone gives their mistakes".

It's so freakin' on point...

2009: "this Autocorrect feature will guess all your mistakes and correct them."
2019: *has to guess what autocorrect might messed everywhere*

The fear of making mistakes and overthinking, and thus, staring at a black screen for hours until I start doing anything.

My Neural Network is learning more from its past mistakes than me. Fml

Fuck I've been making a bunch of simple mistakes lately. It's like I'm having issues thinking clearly.

How often do you guys make mistakes? What was your last mistake?

I have a professor at my university that teaches front end. He still mistakes between / and \
fml

No, making me fix mistakes you are too lazy to look at is not a "good first issue"

All time I try to find any interesting bug in my code but when ever I debug I find only stupid mistakes :/

Sometimes it’s the rookie mistakes that are the most frustrating.

when you work on a bug about fixing mistakes made on a story completed by somebody else

you then get approached with having to do petty unrelated UX stuff in the neighbouring area and the administrative nonsense with it

fuck u jira

To all the masochists who spent hours debugging misspellings:

1. Learn your tools
2. Learn good practice

Every IDE should point out when you're not using a variable you've initiated or using an uninitiated variable as well as at least highlight, if not simply list, every occurrence of the variable under your cursor and let you find all references or even display the number of references next to a variable at all times, and finally, every IDE should autocomplete for you so when it doesn't you know you've messed up. Good IDE makes all the easy mistakes hard and all of the hard tasks easy. Including running tests. If you don't know how to configure your IDE to do all these things take time and learn it. If you still can't figure it out, replace your IDE maybe...?

Also use the debugger. Preferably one that nicely integrates with your IDE. If you don't, check point 1.

Also write tests and *run them*.

Also if your misspellings tend to consist of a missing `s` at the end of a plural noun just call it `entityCollection` instead of `entities`. And read up on more good programming practices and naming conventions.

im new to programming and teaching myself the more i learn the discouraging it becomes. P.S do the guys at stack overflow hate noobs or 'rookie mistakes' because for a community that is supposed to be about answering questions they sure do seem to hate it when I ask them

L1 support requested to terminate an EC2 instance on which one of our apps seemed to be misbehaving. The node was terminated after few min.

L1 later realized that that instance didn't belong to that app, but instead it was one of the RabbitMQ nodes.

Then, after some panicking we remembered that HA was enabled, so nothing should've been lost.

Later, we realized that the recent RMQ upgrade necessitated a new cluster on which HA was NOT enabled!

Dev-tip of the day:

Always make sure that your database table fields are long enough to hold the entire third-party API client reference ID, so that the last three characters won’t be cut off..

I’ve been “crying” here while debugging for the last hour because my API function and everything else worked, but the result wasn’t showing up in the third-party application (their API returned a 200), but when I tested it with their API sandbox application, it did show up..

Tomorrow I'll have my Java exam. Teacher sent us a code example and I analyzed it, it works correctly but it's full of mistakes about polymorphism. I'm fucking afraid

Always always always always always keep writing tests as you implement features. TDD is good thing but not necessary but tests are really necessary. I thought I'll write tests later now the code is so tightly coupled I can test things independently. 😑😑

Sometime my code is so wrong that I can almost hear the mother of algorithm crying out loud.

I just want to remove that piece of code from my project....no, from my mind, my life.

!rant && story

tl;dr I lost my path, learned to a lot about linux and found true love.

So because of the recent news about wpa2, I thought about learning to do some things network penetration with kali. My roommate and I took an old 8gb usb and turned it into a bootable usb with persistent storage. Maybe not the best choice, but atleast we know how to do that now.

Anyway, we started with a kali.iso from 2015, because we thought it would be faster than downloading it with a 150kpbs connection. Learned a lot from that mistake while waiting apt-get update/upgrade.

Next day I got access to some faster connection, downloaded a new release build and put the 2015 version out it's misery. Finally some signs of progress. But that was not enough. We wanted more. We (well atleast I) wanted to try i3, because one of my friends showed me to /r/unixporn (btw, pornhub is deprecated now). So after researching what i3 is, what a wm is AND what a dm is, we replaced gdm3 with lightdm and set i3 as standard wm. With the user guide on an other screen we started playing with i3. Apparently heaven is written with two characters only. Now I want to free myself from windows and have linux (Maybe arch) as my main system, but for now we continue to use thus kali usb to learn about how to set uo a nice desktop environment. Wait, why did we choose to install kali? 😂

I feel kinda sorry for that, but I want to experiment on there before until I feel confident. (Please hit me up with tips about i3)

Still gotta use Windows as a subsystem for gaming. 😥

Arrgh. The web interface for DevRant sucks, so I post using my phone.

Why do I always notice the auto-correct generated mistakes after it's too late to fix them?

Why is there a time limit to edit my posts?

I used to love JS until I learned it properly. Shit is a fucking hodge-podge of concepts. Still not as mature as I thought it was. And each new iteration is just fixing the mistakes of its past. Fucking language is a mistake in itself!

Time spend with coding: 2 hours
Time spend with branching, merging, fixing merge mistakes and check if systemnis building again: 4 hours

What a miserable day...

3days later i have an interview in a company, i messed up first one😂😎
but i study more again i hate making mistakes.

Culture.

Everybody seems to fuck it up. (Most ignore it entirely)

Everybody seems to undervalue it’s importance. (Its value cannot be overstated)

Everybody seems to think it is a luxury for successful companies. (Instead of being a major part of what got them their success)

Everybody seems to think having beer in the fridge is culture, or some other perk. (I like beer and shit, but that’s not culture unless your company makes fucking beer!)

Everybody seems to think that a value statement is culture. (Your employees don’t give a fuck if you want to “provide value to X industry)

And guess, fucking, what...

Everyone is wrong. That’s why 9/10 startups fail, because the founders and CEO are dumbasses.

Here’s some pretty simple advice for life...

“Don’t be a fucking dumbass”

- Me

Round off error happen in the app. Find a piece of code .
$rootScope.isRoundoffEnabled?2:2

Revision numbers don't matter at all?

Then you can't figure out why your build is broken?

Now after 10 hours I have until 8 am to fix a months worth of other people's mistakes. How awesome!

I code for 2 1/2 days straight, I'm in the zone, no comments, because I'm not in some comp sci beginners class, finish up, test it the only problem is with... All of it... Just considering writing another program to comb through that one and find the mistakes for me

Is it just me or is what susspose to be the tech giants, making more and more n00b mistakes lately... Apple's latest update "best release of iOS yet" bricks the phone, Samsung phones are blowing up...

Things are continously prematurely released to try and beat everybody in the market place which just leads to unimpressive and dangerous product releases.

What is the smallest, most innocuous mistake you've made that had huge consequences later?

I'll start: today I made a one-letter typo in a configuration file, which set off a ridiculous comedy of errors that culminated with me tearing down and rebuilding a whole AWS account.

Fighting what I call "FTS" (Fuck This Shit) syndrome.

Most of my mistakes or challenges caused to my future self can be attributed to succumbing to FTS.