Thor!!

Welp, wish me luck diving into C for the first time

Anyone here worked a whole lot with low level programming?

I have always worked with high level languages like Python and C++, but I’ve also had an interest in working with embedded systems, real close to the metal.

Any directions on where I should go to start learning low level programming? Sites, languages, etc?

Appreciated devRant fam!😊

I love working as one-man army in multiple projects. Just love.

I got sick, stayed in bed for a week and now, after getting back to work, everything went to shit. And there's no one but me to fix the whole mess.

Yay.

It's 4 A.M and I just remembered what I did wrong, this happens every freaking time 😐

What the hell brain !
I need some sleep !

Average devranter walking into the office:

It's disheartening to see a senior member of my team shitting on the code of less mature developers. Don't just say "this is unacceptable", elaborate, teach them. How are they going to action anything from that feedback?

Take the time to respond to their questions when they ask for clarification on what you're saying. Don't berate them.

Honestly some developers need to learn a thing or two about code etiquette.

There's no room for good cop / bad cop behaviour.

wk87 is a dangerous topic for me, i've been through a lot. I apologise for what I am about to inflict on this network over the coming week.

Most incompetent co-worker, candidate 1, "T".

T was an embedded C developer who talked openly about how he's been writing code since he was 14, knew all the C system libraries and functions like the back of his hand. For the most part, he did ... but not how to actually use them, as (based on his shocking ... well everything) he was inflicted by some sort of brain disorder not yet fully understood by medical science. Some highlights:

- Myself and the CTO spent 4 days teaching him what a circle buffer was and how to build one.
- His final circle buffer implementation had about 3 times as much code as he actually needed.
- When the code was running too slowly on the device, we didn't try find any performance improvements, or debug anything to see if there was anything taking too long. No not with T, T immediately blamed TCP for being inefficient.
- After he left we found a file called "TCP-Light" in his projects folder.
- He accused the CTO of having "violent tendencies" because he was playing with a marker tossing it up in the air and catching it.
- He once managed to leave his bank statements, jumper and TROUSERS in the bathroom and didn't realise until a building wide email went out.
- He once .... no hang on, seriously his fucking trousers, how?
- He accused us all of being fascists because we gave out to him for not driving with his glasses, despite the fact his license says he needs to (blind as a bat).

... why were his trousers off in the first place? and how do you forget ... or miss the pile of clothes and letters in a small bathroom.

Moving on, eventually he was fired, but the most depressing thing of all about T, is that he might not even be top of my list.

Tune in later for more practiceSafeHex's most incompetent co-worker!!!

today is my first day ever as junior dev.
congratulate me (?)

Websites these days be like.....

Do you ever spend an hour editing an email reply to a client before you send it? Trying something akin to alchemy when you attempt to convert snark, veiled contempt, and shock at how stupid the client is into something professional and polite? It’s like trying to bottle farts as fancy perfume.

Like the first draft is:

“Dear idiot,

Please disconnect your computer from the wall and return it to where you bought it from and then never use a computer again you dopey fuck.”

To

“Dear Client,

Yes sir. I’ll have it done for you by tomorrow.”

God it hurts.

Hey Mm...Morty. What are you doing?

Oh gee Rick, I’m just...you know...using Linux and telling the internet how that makes me better than them.

Morty, you rr...realize that it...it...doesn’t matter what OS you use Morty. Y...y...you’re still a piece of shit Morty. I can prove it...burp...mathematically Morty. In the grand scheme of the universe...y...y...you are a bubble sort algorithm surrounded by quick sorts Morty.

Oh gee Rick.

If you're going to ask for my help

... and then do the opposite of everything i say

... and then complain when things don't work

... and continue to ignore everything i say

HOW ABOUT YOU JUST FUCK OFF

If this rant gets 4,294,967,296 likes, it might cause an integer overflow.

How many can relate?

You know you're a dev when your browser tabs look like this

Photo of the day...

Haha, always a gem ❤

Jesus, Apple are fucking amazing at design! A keyboard I need to prop up with a book and a mouse I can't use when charging.... Genius!!!!

Thanks windows for the best error message ever

"You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!"

So, as the author of the code in question, I join the bridge... And what happens next, I will simply never forget.

First, a little backstory... Another team within our company needed some vendor client software installed and maintained across the enterprise. Multiple OSes (Linux, AIX, Solaris, HPUX, etc.), so packaging and consistent update methods were a a challenge. I wrote an entire set of utilities to install, update and generally maintain the software; intending all the time that this other team would eventually own the process and code. With this in mind, I wrote extensive documentation, and conducted a formal turnover / training season with the other team.

So, fast forward to when the other team now owns my code, has been trained on how to use it, including (perhaps most importantly) how to send out updates when the vendor released upgrades to the agent software.

Now, this other team had the responsibility of releasing their first update since I gave them the process. Very simple upgrade process, already fully automated. What could have gone so horribly wrong? Did something the vendor supplied break their client?

I asked for the log files from the upgrade process. They sent them, and they looked... wrong. Very, very wrong.

Did you run the code I gave you to do this update?

"Yes, your code is broken - fix it! Production is down! Rabble, rabble, rabble!"

So, I go into our code management tool and review the _actual_ script they ran. Sure enough, it is my code... But something is very wrong.

More than 2/3rds of my code... has been commented out. The code is "there"... but has been commented out so it is not being executed. WT-actual-F?!

I question this on the bridge line. Silence. I insist someone explain what is going on. Is this a joke? Is this some kind of work version of candid camera?
Finally someone breaks the silence and explains.

And this, my friends, is the part I will never forget.

"We wanted to look through your code before we ran the update. When we looked at it, there was some stuff we didn't understand, so we commented that stuff out."

You... you didn't... understand... my some of the code... so you... you didn't ask me about it... you didn't try to actually figure out what it did... you... commented it OUT?!

"Right, we figured it was better to only run the parts we understood... But now we ran it and everything is broken and you need to fix your code."

I cannot repeat the things I said next, even here on devRant. Let's just say that call did not go well.

So, lesson learned? If you don't know what some code does? Just comment that shit out. Then blame the original author when it doesn't work.

You just cannot make this kind of stuff up.

At my last place of employment, there was a really smart developer who was charged with building a shared library to setup new applications. He called it Jack Stack. He had it pretty much finished, but got pulled into other projects so he couldn't do much "internal marketing". Of bunch of us (friends of this dev) knew it was cool, but always teased him about how no one was using it.

Several months later, he is able to revisit it, and starts refactoring it. He gets on a chat with us saying, "I've got an amazing name for Jack Stack 2! Do you want to know what I called it?" Without skipping a beat, another friend typed, "Deprecated?" Oh the laughing that ensued... Every time it was brought up, I couldn't stop laughing...

But for reals, it was an amazing library.

https://www.gitignore.io/ is very simple and useful to make .gitignore files . try it :))

When you check the comments under GitHub and most of them are +1

When Linux doesn't boot