linus torvalds has complete power over linux. huh.

that means that he's likely to include linux in his will.

could you imagine inheriting linux?

Looking for a job as a deveoper be like:

Job title: car driver

Job requirements: professional skills in driving normal- and heavy-freight cars, buses and trucks, trolley buses, trams, subways, tractors, shovel diggers, contemporary light and heavy tanks currently in use by NATO countries.

Skills in rally and extreme driving are obligatory!
Formula-1 driving experience is a plus.

Knowledge and experience in repairing of piston and rotor/Wankel engines, automatic and manual transmissions, ignition systems, board computer, ABS, ABD, GPS and car-audio systems by world-known manufacturers - obligatory!

Experience with car-painting and tinsmith tasks is a plus.

The applicants must have certificates by BMW, General Motors and Bosch, but not older than two years.

Compensation: $15-$20/hour, depends on the interview result.

Education requirements: Bachelor's Degree of Engineering.

Soooo true

Where should starting brackets be positioned if/else and function definition in C? Same line or the next line. Have not seen pure cosmetic bullshit like this.

Programming should be like art, where you try and learn different skills and tools to get better over time.... Not a continuous game of whack-a-mole where your try to hit everything with a hammer...

¯\_(ツ)_/¯

WTF C++?! I liked you, I defended you, I told people about you. Then you go and do shit like this:

int main(int argc, char* argv[])
to
auto main(int argc, char* argv[])->int

Seriously C++ WTF?!

sudo rm /usr/bin/rm

*finishes MATLAB course*
My blanket when I wake up and think about my expired license which I won't renew:

😭😭😭😭😭😂😂😂😂 this is Soo true

Software engineer

This is a view from a rooftop in NYC that I sometimes get the pleasure to work from. I really like the view and it’s pretty quiet usually. It also overlooks one of my favorite buildings, the Empire State Building.

I’m looking forward to seeing everyone else’s desks, setups, and remote/outdoor workspaces.

We’ll be featuring them on our recently launched devRant Instagram account, devDesks (https://www.instagram.com/devdesks).

Okay, I have no idea who spreads that semicolon idea but it must be stopped. NOW.

someStatement
;someStatement
;someStatement
;

WHY?

!rant

After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:

1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.

2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)

3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.

4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.

5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.

6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.

7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.

8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.

9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)

10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...

These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!

if (questionAsked) {
retuen "It depends...";
}

I hate it I hate it I hate it

But it's true because there are a fuckton of factors that determine the answer to a question and nobody ever knows all of them.

I can rarely answer a question from classmates or non-techs without saying that it depends or that there are multiple options.

"Are statics ever good?" It depends
"Should I inject this dependency?" It depends
"Should I google every question first?" It depends

I fear giving a whole answer without knowing the details or at least seeing the code. I've come across multiple XY problems and I'm glad I took the time to look at some code first.

Is that same happen to you ?

"To some degree, to be creative you have to be selfish." - Meredith Norwood

Thanks to all of you who rant my meme
| not original

"I never let my schooling get in the way of my education." - Mark Twain

PROCEDURAL PROGRAMMING
You write a list of instructions. The machine reads this list and runs your commands.

OOP PROGRAMMING
Quite similar to procedural programming but you group your functions via objects.

RANDOM PROGRAMMING
Learned of this new paradigm quite recently working with Blue Prism, which is essentially the program doing whatever it wants from crashing, freezing, returning wrong results, sometimes working properly, with no reason whatsoever other than the sheer malice of those beasts of burden who designed it in the first place. Mark my words, BP devs, you will be held accountable for your crimes against God and humanity.