A plain computer illiterate guy rings tech support to report that his computer is faulty.

Tech: What's the problem?

User: There is smoke coming out of the power supply.

Tech: (keeps quiet for the moment)

Tech: You'll need a new power supply.

User: No, I don't! I just need to change the startup files.

Tech: Sir, the power supply is faulty. You'll need to replace it.

User: No way! Someone told me that I just needed to change the startup and it will fix the problem! All I need is for you to tell me the command.

Tech support: 10 minutes later, the User is still adamant that he is right. The tech is frustrated and fed up.

Tech support: (hush hush)

Tech: Sorry, Sir. We don't normally tell our customers this, but there is an undocumented DOS command that will fix the problem.

User: I knew it!

Tech: Just add the line LOAD NOSMOKE <nosmoke> at the end of the CONFIG.SYS. Let me know how it goes.

10 minutes later.

User: It didn't work. The power supply is still smoking.

Tech: Well, what version of DOS are you using?

User: MS-DOS 6.22.

Tech: That's your problem there. That version of DOS didn't come with NOSMOKE. Contact Microsoft and ask them for a patch that will give you the file. Let me know how it goes.

1 hour later.

User: I need a new power supply.

Tech: How did you come to that conclusion?

Tech: (hush hush)

User: Well, I rang Microsoft and told him about what you said, and he started asking questions about the make of the power supply.

Tech: Then what did he say?

User: He told me that my power supply isn't compatible with NOSMOKE.

Talking to my son today about one of his CS classes, not sure which.

He says: "I missed the lecture yesterday, but I'm not going to bother re-watching it."

Me: "Why? You really should. You're paying for these classes AND you really need to actually learn this stuff."

Son: "Well, because I got 100% on my last assignment without going to class. I just Google'd everything and figured it out on my own from what I found."

My wife out of the blue: "DAMN IT, BUT THAT'S NOT HOW IT WORKS IN THE REAL WORK WORLD!"

Oh, you poor, uninformed summer child. I love her, but she just doesn't know that my son has already learned the key lesson he needed to learn from his schooling in order to get a job and make good money in this field! #ProudTechieDadMoments

I suddenly remembered this after being gone from my previous company for nearly a year.

So, I worked there as a tech supporter and Linux engineer.
What would often happen was clients calling with an issue regarding software of some sorts and about half the time, instead of LOOKING AT THE GODDAMN ERROR MESSAGE they'd just click it away fast and complain shit wasn't working.

I specifically remember this one case:

*big client mails complained that one of their clients' email isn't working. Screenshots weren't possible apparently so after emailing back and forth for way too long, we decide to do a screen sharing session (which we never do).*
(for the record, already emailing for hours, client very frustrated, me as well because the behavior of the software sounds impossible)

Me: alright, close everything, then open it again so I can see what happens.
Client: *opens mail client, error appears, client clicks error away faster than an arch user being able to mention they use arch*
Me: uhm.... I assume you already know what that message said and that it has nothing to do with the issue?
Client: it has nothing to do with the issue.
Me: okay... But have you at least looked the message?
Client: no but it has nothing to do with the issue.
Me: but, how'd you know if you won't look at it?
Client: it has nothing to do with the issue, okay?
Me: okay.... so, what's happening here?
Client: the user isn't receiving email anymore at this point!
Me: alright, have you checked the settings and everything?
Client: of course, all good
Me: okay but can we at least restart the software again to at least check the error message?
Client: FINE. *restarts client (pun intended, of course)*
Error message: username or password incorrect, can't connect to the server.
Client:..........
Client:............
Client:...............
Client:..................
Client:.....................
Client:..................
Client:...............
Client:............
Client:.........
Client: 😐
Client: 😶
Client: 😅
Client: 😬
Client:..... Right, I changed the password...
Client: *sets correct password*
*poof, error message gone*
Client:..... Thanks 💀
Me: you're welcome 😄

💀

When the madness known as "software development" gets me down, I visit DevRant to complain and read about people who have it harder than me.

I just wanted to offer my condolences... Ya'll are so much more fucked than I am. 👍

My whole team was a circus:
- Dev 1, the senior: he will be spent his days coding his personal projects and will convince management that everyone else needed to prove themselves so he will have nothing to do and we will do all the work.
- Dev 2, the junior: he was convinced that his mission in life was to be friends with his team. He's desk was far from the rest of the team so he will show just right after lunch EVERY FREAKING DAY with a list on his phone of random things he wanted to talk about like music, artists, art, news, etc., he really thought I didn't notice the list.
- Dev 3: the vegan: you will hear on every chance how she was so awesome for being vegan.
- Dev 4, the expert: if you ask him anything he will stare at you in silence to make you feel like you are a stupid for not knowing the answer and then turn around like nothing.
- Dev 5, the ghost: he will show early every day, code without mouthing a word and leave at 5pm, I think I heard him saying "hmmm" once but I might be wrong.
- Dev 6, the coder by accident: he was a graphic designer and ended up doing front end so he hated his job.
- Dev 7, me: the one who didn't care about anything but doing his job and leave.
- The project manager: she didn't knew anything about technology but will attend meetings with clients on her own, commit to deadlines and then inform us that the project that we estimated for 8 weeks will have to be done in 2 with new additions to the features.

You know the drill, here's your potato :/

fuck this year seriously

My favorite kind of interview question/challenge is anything that is highly practical for the job. At the current company I work, the coding test/interview challenge was to design and implement an API very similar to the core functionality of the actual product. It’s fair, tests for skills relevant to the job, and is much better than irrelevant silly brain teasers and cs questions, I feel.

In terms of specific questions, one of my favorites is one that one of my colleagues suggested I ask to potential candidates: describe what you think your biggest failed project/task was in your engineering career, and what happened/what you learned. I think it’s a good reflective question that can tell a lot about someone.

*Manager enters the room quickly*

Manager: Coffe2Code, we have a serious problem on the application, (We are working on a chat app).

Me: What? now just few hours before the Demo?, what is it?

Manager: when I send or receive a media message (audio or video) the sound is not playing, the file seems like corrupted !

Me: that's strange, let me debug it and see.

*Me spending an hour and could not even reproduce the bug..*

Me: Boss, I cannot see the bug, can I debug on your device quickly?

Manager: Sure, here it is.

Me: hold the fucking device, press VOLUME UP, IT WAS FUCKING MUTE. THERE WAS NO ISSUE MOTHERFUCKER.

Manager, oups ok good no issue then, thanks

passionately making love on Friday morning.

Cellphone buzzes for WhatsApp notification, ignored.
Call ignored, SMS ignored, again call, ignored.

She : whose that bitch calling you?
Me : it's no one important.
She : Checks WhatsApp, message from CTO, server crashed.
Me : Umm, darling, I need to fix this.

It's been 2 days she hasn't answered my call after she left.

I used vs code for a solid 3 years, but my friend has been using notepad. No color coding. No dark theme. No auto commenting. No suggestions. Just plain black text in a white box.

Like a psychopath.

I want to stop charging my e-scooter at around 85% because this will increase the battery life. To avoid always having to pull the plug at the right level, I made a stop circuit that goes between charging brick and e-scooter.

There's no processor involved, just a CMOS 555 used as inverting Schmitt Trigger which controls a power mosfet. Also two status LEDs and a start switch. The poti adjusts the cut-off level. Worked on first try, with only manual voltage and tolerance calculations beforehand!

The biggest mystery - SOLVED!

Nice surprise left on my desk at work today:)

Dude let his sister play a game for an hour, and his performance went to shit afterwards. Turns out she had somehow installed a new rogue AV going around and it did this shit to scare him into buying.
Edit: forgot to add that it's called "Segurazo"

One of my former coworkers was either completely incompetent or outright sabotaging us on purpose. After he left for a different job, I picked up the project he was working on and oh my God it's a complete shitshow. I deleted hundreds of lines of code so far, and replaced them with maybe 30-40 lines altogether. I'm probably going to delete another 400 lines this week before I get to a point where I can say it's fixed.

He defined over 150 constants, each of which was only referenced in a single location. Sometimes performing operations on those constants (with other constants) to get a result that might as well have been hard-coded anyway since every value contributing to that result was hard-coded. He used troublesome and messy workarounds for language defects that were actually fixed months before this project began. He copied code that I wrote for one such workaround, including the comment which states the workaround won't be necessary after May 2019. He did this in August, three months later.

Two weeks of work just to get the code to a point where it doesn't make my eyes bleed. Probably another week to make it stop showing ten warnings every time it builds successfully, preventing Jenkins from throwing a fit with every build. And then I can actually implement the feature I was supposed to implement last month.

Just take a moment to appreciate that devRant is both free and doesn't have ads.

6 months ago I sold everything, quit my job, gave up my apartment and left the country with my 11kg backpack. I booked a one way ticket to South America. I wanted to travel, get lost but also finish up some personal projects and do a little tech books challenge I came up with. I learnt so much over the past half a year, it's crazy.

Not looking back. Projects paid off and it turns out that my dream company actually found me themselves without me even applying... and so still from South America I'm in final rounds of the interview! 🤗

All my worries about a gap in CV, no employment along with other problems I thought I was gonna have... It's all BS. So if anyone here is waiting for a sign. Well, this is it now. Go!

Lead developer wants to put SQL statements in to records of the database for the code to execute (in Rails). This smells really bad to me, am I over reacting?

CEO hired graphics designer without HR help after first meeting and that person first day of his work borrowed money from people and that’s not end of story.

Same guy came back at night and robbed the workplace with his friends, didn’t came back to work. Company bought couple of big iMac for new graphics department back then, all gone.

When company reported incident to Police it turned out he travel and steal from companies all over the country and they’re trying to catch him for a year.

Feel free to scroll by if you feel like it.

I am just very excited this evening because with today's commit I have reached a very important milestone in my side-project development. As of today all the [so far] 12 components are all working together and processing the main flow themselves.
No special functions, no test data in the code, nothing like that. A client is able to do its thing now as it should.

I know it doesn't sound like much, but as I'm working on this gigantic beast for 3 years now this milestone is hell of a reward for me!

Just wanted to share :)

edit: f* it! I'm getting a cake!

When you write your assignment in LATEX just because you're bored

After being hired as a PHP programmer, I have been assigned my first Java project

(•_•)
<) )╯i
/ \

\(•_•)
( (> got
/ \

(•_•)
<) )> promoted
/ \

Bad: it works but throws errors

Worse: it doesn’t work but throws errors

Worst: it doesn’t work and doesn’t throw errors

Today I found somebodies phone... Together with his bank cards in the flip protection wallet ... I was able to turn it on and charge it so I awaited a call and now through the caller I was able to return it to its owner within 2 hours of finding it 🥰 got a nice bottle of booze as a reward

I joined a "multi-national" company in middle-east where 90% of the developers are Indian. And since it's a "multi-national" company with 50+ developers I thought they already figured it out. Most of them have 5-10 years of experience. They should know at least how to use git properly, deployment should be done via CI/CD. database changes should be run via migration script. Agile methodology, Code Review - Pull Request. Unit testing. Design Patterns, Clean Code Principle. etc etc

I thought I'm gonna learn new things here. I have never been so wrong in all my life...

Technical Manager doesn't even know what Pull Request is. They started developing the software 4 years ago but used Yii v1 instead which was released almost a decade ago. They combined it with a VueJS where in some files contains around 4000 lines of code. Some PHP functions contain 500+ of code. No proper indentions as well. The web console is bloody red with javascript errors. In short, it's the worst code I've seen so far.

No wonder why they keep receiving complaints from their 30+ clients.

I wrote this code last month...

def func(is_admin, user):
is_admin = is_admin or False
user = user # so pro much wow
return is_admin ^ user

I have a bunch of contesters fort the worst interview.

#1 The Dishonest Ignorant

Me: *asks question*
#1: *stumbles*
Me: It's okay to say that you don't know.
#1: *continues to ramble on without making sense*
Me: Well, okay. That is all. I don't think that this will be a fit.

#2 The fraud

Me: How would you rate your knowledge in object orientated programming?
#2: Very advanced! I am an expert!
Me: Can you state the difference of an interface and an abstract class?
#2: *surprised pikachu-face* Well not that advanced!

#3 The trickster

During a skype call (without video):

Me: *asks question*
#3: *keyboard sounds aclacking*
Me: Are you googling?
#3: No *click clack click a clack* ... and to answer your question: *starts reading from the first search results*

The real bummer is, that in all of these cases, just saying "I don't know" would have been fine. (The "expert" OOP-guy would still have some explaining to do.)

It's not like that our interview process resolves around trick questions or that you'd get kicked out for getting one answer wrong. Though how can I trust somebody not to lie to me on a daily basis if they fake their interview?

We keep the interview relatively basic and rely on real-word coding exercise anyway and it helps us to get an idea on where we would gain support from them and where we need to support them.

As a developer you spend a lot of time learning new stuff anyways.

It blows my mind.

Today I discovered by myself that...

...in a shell...

...when entering a password (e.g. ssh)...

...and you make a typo... 🤦‍♂️

...you don't need to smack that backspace key like a maniac! You can just use the clear line shortcut: control+U (^U). This clears all input to the left of your cursor and this also works for passwords.

note: Not the worst dev I've interviewed but worst I've worked with.
A guy who worked in my company before me "HARDCODED" the entire calendar for next 10 years starting 2016 in dictionaries and arrays in Python for a project.