Well I did exactly what it said I would.

Today I learned:

`/usr` stands for “universal system resources” not “user”

`/dev` stands for “device” not “development”

Had no idea.

Why Apple developer are up at night?

Oh poor Libre😂

Such a relief

This rant has been written from the Signal messaging app and uses a custom Signal 'gateway' (a registered user which is a server in this case) with a PHP api behind it. If this rant appears on devRant, it fucking works!

Some empty-headed helpdesk girl skipped into our office yesterday afternoon, despite the big scary warning signs glued to the door.

"Hey, when I log in on my phone, the menu is looking weird"

"Uh... look at my beard"

"What"

"Just look at this beard!"

"Uh.... OK"

"Does this look like a perfectly groomed beard"

"Uh... it's pretty nice I guess"

"You don't have to lie"

She looks puzzled: "OK... maybe it could use a little trimming. Uh... a lot of trimming". "I still like it though" she adds, trying hard to be polite.

"I understand you just started working here. But the beard... the beard should make it clear. See the office opposite to this one?"

"Yeah"

"Perfectly groomed ginger beards. It's all stylish shawls and smiles and spinach smoothies. Those people are known as frontend developers, they care about pixels and menus. Now look at my beard. It is dark and wild, it has some gray stress hairs, and if you take a deep breath it smells like dust and cognac mixed with the tears caused by failed deploys. Nothing personal, but I don't give a fuck what a menu looks like on your phone."

She looked around, and noticed the other 2 tired looking guys with unshaven hobo chins. To her credit, she pointed at the woman in the corner: "What about her, she doesn't seem to have a beard"

Yulia, 1.9m long muscled database admin from Ukraine, lets out a heavy sigh. "I do not know you well enough yet to show you where I grow my unkempt graying hairs... . Now get lost divchyna."

Helpdesk girl leaves the scene.

Joanna, machine learning dev, walks in: "I saw a confused blonde lost in the hallway, did you give her the beard speech?"

"Yeah" -- couldn't hold back a giggle -- "haha now she'll come to you"

Joanna: "No I already took care of it"

"How?"

"She started about some stupid menu, so I just told her to smell my cup". Joanna, functional alcoholic, is holding her 4pm Irish coffee. "I think this living up to our stereotype tactic is working, because the girl laughed and nodded like she understood, and ran off to the design department"

Me: "I do miss shaving though"

devRant needs some form of syntax highlighting, so 𝐂𝐨𝐝𝐞 snippets can be posted as oppose to screenshots.

1. Buy boxes of orange juice, almost past their expiry date.
2. Put boxes on the hot office windowsill for a few weeks.
3. Cool down juice in fridge.
4. "Hey dear coworker, would you like a refreshing juice box on this hot spring day?"
5. Watch coworker retch and vomit, spitting blue-grayish juice over his desk, crying: "Why would you give me old moldy juice without checking the date?"
6. "Do you remember when you told me you didn't have time for unit tests? THIS IS WHAT HAPPENS, DAVE, THIS IS WHAT FUCKING HAPPENS WHEN YOU DEPLOY UNTESTED CODE.... NOW FINISH YOUR JUICE!"

Happy April Fool's!

- Windows 8 == Best OS
- Apple is fairly priced
- PHP > C++
- Java === JavaScript
- facebook > devrant
- Github useless, use .zip
- Comic Sans best terminal font
- Nobody needs a web developer because Wordpress much better
- Linux is for virgins

As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.

I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.

These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.

Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.

All I want to say is:

No time was lost.

This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.

Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.

One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.

You don't notice the things you take back from your failures, they slip back sticking to you, undetected.

You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.

You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.

You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.

Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.

Please, for the love of code...

Start and fail as many projects as you can.

Secretary of the IT department stated in a meeting that she was "overqualified to babysit a group of 40 grown-ass men who are unable to communicate with each other"

... all devs had a huge grin on their faces because we knew that she was absolutely right, management was furious 😂

She submitted her resignation on the same day, best secretary we've ever had!

A boy asked his bitcoin-investing dad for 1 bitcoin for his birthday.

Dad: What? $15,554??? $14,354 is a lot of money! What do you need $16,782 for anyway?

Source: Twitter @cryptomanran

My mom said that if I don't get off my computer and do my homework she'll slam my head on the keyboard, but I think she's jokinfjreoiwjrtwe4to8rkljreun8f4ny84c8y4t58lym4wthylmhawt4mylt4amlathnatyn

REAL gif from Hawaii warning system!

The beginning of my freelancing time. I was so naive. Didn't even used contracts...

This one client wanted a website with 2 specific features until a certain time. It should look nice, but only the features functionality was defined. All seemed reasonable at first.

I delivered 2 weeks before the deadline. The client was furious, as it didn't look like they imagined. They wrote me 8 lengthy emails with very fractioned feedback. It was becoming unreasonable.

But hey, I'm a newbie in this business. I have to make myself a name, I thought.
Oh was I naive....

This whole project went on for 2 more months. The client was unhappy with every change and 2-5 emails a day with new demands were coming in. I was changing things they wanted done 2 days ago, because they changed their mind.

Then they started to get personal. They were insulting me and even my family. My self-confidence dropped to an all-time low.

In the end I just sent them all the code for free and went to therapy.

BTW: this was also my most important experience, as things went up hill from then on. As Yoda once said: The greatest teacher, failure is.

Aardwolf is very fun and i suggest y'all play it a bit if you're looking for better ways to slack off at work

$ telnet aardwolf.org 4000
*port 23 also works

#mindhacks 😎

So I "grade" homework for programming 1 students...
Task was to produce an output like:
1
1 2
1 2 3
1 2 3 4
1 2 3 4 5

...and this was committed!
I really had to hold back laughter...
This looks purposefully obfuscated...

Give that man some HUGE FUCKING COOKIES!

When you watch LotR as a geek xD

I want to pay respects to my favourite teacher by far.

I turned up at university as a pretty arrogant person. This was because I had about 6 years of self-taught programming experience, and the classes started from the ansolute basics. I turned up to my first classes and everything was extremely easy. I felt like I wouldn't learn anything for at least a year.

Then, I met one of my lecturers for the first time. He was about 50~60 years old and had been programming for all of his career. He was known by everyone to be really strict and we were told by other lecturers that it could be difficult for some people to be his student.

His classes were awesome. He was friendly, but took absolutely no shit, and told everything as it was. He had great stories from his life, which he used to throw out during the more boring computer science topics. He had extremely strict rules for our programming style, and bloody good reasons for all of them. If we didn't follow a clear rule on an assignment, he'd give us 0%. To prove how well this worked, nobody got 0%.

We eventually learned that he was that way because he used to work on real-time systems for the military, where if something didn't work then people could die.

This was exactly what I needed. In around one semester I went from a capable self-taught kid, to writing code that was clear, maintainable and fast, without being hacky.

I learned so much in just that small time, and I owe it all to him. So often when I write code now I think back to his rules. Even if I disagree with some, I learned to be strict and consistent.

Sadly, during the break between our first and second year, he passed away due to illness. There was so many lessons still to be learned from him, and there's now no teachers with enough knowledge to continue his best modules like compiler writing.

He is greatly missed, I've never had greater respect for a teacher than for him.

When your boss learns how to use StackOverflow

90s - We will use AI to cure cancer in the future..
2017 -

So everyone is showing their setup, I thought why not share mine.

Someone on the IP 127.0.0.1 has been creating a lot of bugs in my code, please beware of you notice any connections from that address.

I don't understand why so many people fight this war of tabs vs spaces. My colleagues elegantly solved the problem just not using indentation at all

Always

I don't seem to understand why so many developers nowadays are focused on learning newer frameworks rather than focusing on best practices and learning how to code better.

"Hey I learnt React today, we should totally switch to it because it's so amazing"

> mfw the same guy doesn't even know how to follow coding styles, write good code that scales or document his code.

I think some people need to take a step back and focus on the more vital tasks of writing good code to begin with rather than getting so excited about every new thing that surfaces. It's annoying as fuck to deal with some of these people who you have to work alongside and be able to read their loopy shit code and all they are doing in their time is refreshing hackernews.

Hot fix of a production bug!