Got call from extremely angry customer, our product is shit and doesn't work. At all. Important customer so I went to visit.

He had the perfect setup, our product to the left, our competitor's to the right.

He connected the Ethernet cable to their product, it worked. He plugged it out and connected to ours... Nothing. Shit.

I started to debug on the premises, took logs, everything. It seemed like our product didn't receive any data at all. What the fuck? Tried everything, debugged low level, still nothing. Sweating as hell.

After two hours I got a strange feeling. So I swapped place, our product to the right, competitor's to the left. Now OUR product worked, competitor's zilch.

THE FUCKING ETHERNET CABLE HAD A GLITCH. IF YOU BENT IT TO THE RIGHT IT WORKED, IF YOU BENT IT TO THE LEFT IT WAS BROKEN.

I had never seen a customer be this embarrassed in my life. He apologized to me, my boss, his boss, the Queen, everyone.

We got the contract.

Dear people who complain about spending a whole night to find a tiny syntax error; Every time I read one of your rants, I feel like a part of me dies.

As a developer, your job is to create elegant optimized rivers of data, to puzzle with interesting algorithmic problems, to craft beautiful mappings from user input to computer storage and back.

You should strive to write code like a Michelangelo, not like a house painter.

You're arguing about indentation or getting annoyed by a project with braces on the same line as the method name. You're struggling with semicolons, misplaced braces or wrongly spelled keywords.

You're bitching about the medium of your paint, about the hardness of the marble -- when you should be lamenting the absence of your muse or the struggle to capture the essence of elegance in your work.

In other words:

Fix your fucking mindset, and fix your fucking tools. Don't fucking rant about your tabs and spaces. Stop fucking screaming how your bloated swiss-army-knife text editor is soooo much better than a purpose-built IDE, if it fails to draw something red and obnoxious around your fuck ups.

Thanks.

My dumb CEO just hired an even dumber CTO. The new CTO asked me the following questions...

1. What is GitHub?

2. What is JSON?

3. What’s an array?

4. What is Get and what is Post?

5. When an iPhone is offline, can it call an API on our server to tell us it’s offline?

6. I know you’ve spent 11 month the writing this backend in PHP but can you change it to Java now?
Me: Why?
Dumb CTO: Because it’s better.
Me: How?
Dumb CTO: because it is.

7. I know you’ve started to rewrite this codebase I Java but can you convert it to Node.JS now?
Me: Why?
Dumb CTO: Because Facebook uses it.

8. What is MySQL? Why aren’t you using a database instead?

9. What does NULL mean?

Somehow, I doubt that asshole is remotely qualified for the job.

Fakin shyt for brains.

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.

I've been on devRant long enough that I'm getting familiar with some of the more frequent ranters here. I imagine it's been done before, but I'd like to put some faces to the names.

So post them mugs in here, fellas!

Here's me with my daughter (turns 1 next week!), taken last Saturday.

*Changes code*
*alt + tab to website*
*ctrl + s to save changes*

FUUUUUU...

Waiting for this day....

When I Googled a problem I faced, and found a YouTube video solving it, then tried to thumb 👍 it up, but YouTube said: "You can not like your own videos!"
.
.
I recorded it for a friend two years ago!

"Any product that needs a manual to work is broken." - Elon Musk

buzzword translations:

"cloud" -> someones computer

"big data" -> lots of somewhat irrelevant data

"ai" -> if if if if if if if if if if if if if else

"algorithm" -> something that works but you don't know why

"secure" -> https://

"cyber security" -> kali linux + black hoodie

"innovation" -> adding something completely irrelevant such as making a poop emoji talk

"blockchain" -> we make lots of backups

"privacy" -> we store your data, we just don't tell you about it

Who want join in a study group?
To develop a web app

Hey guys! So I'm new new here and it would be great to get a few upvotes so that I can create my avatar as soon as possible. I love the community and I'm planning to stay active for time to come.

Thanks :)

Tried browsing reddit on my new feature phone today, was not disappointed.

It has a surprisingly feature rich browser
http://html5test.com/s/...

Me and myself have worked on so many projects together but somehow we never really finished any of them...

I rewrote something in clean 20 lines of code, while my coworker had worked hard and ended up with like 80-100 lines. I did not talk to him before I did it, but asked him to review what I did. I still had to learn how to properly work together..

Interviewer: Tell me your previous achievements.
Me: I had a level 213 fire mage.
Interviewer:
Me:

Tumblr has the best changelog, ever!

For all the people that have nothing to hide:

https://vimeo.com/189016018

I managed to fuck up grub... 😔

And I managed to unfuck it. Feels so good! 😁

I wonder, do you also sometimes take a tech book and read it like a novel?

Maybe I'm strange. It's just thrilling to read about a new problem and wonder 'oh my God, how will they solve it' - can't wait to read on 😅

This is happening in Firefox. The definitions are not being rendered.

Interviewers : interviewees
Employers : employees​
Testers : balls 😛

Today I discovered MIT OpenCourseWare.

I hate university, and I usually doze off during lectures, but my god, I've been listening to "Introduction to Algorithms" for about 6 hours now, and I'm hanging on to every word.

To become an engineer (CS/IT) in India, you have to study:
1. 3 papers in Physics (2 mechanics, 1 optics)
2. 1 paper in Chemistry
3. 2 papers in English (1 grammar, 1 professional communication). Sometimes 3 papers will be there.
4. 6 papers in Mathematics (sequences, series, linear algebra, complex numbers and related stuff, vectors and 3D geometry, differential calculus, integral calculus, maxima/minima, differential equations, descrete mathematics)
5. 1 paper in Economics
6. 1 paper in Business Management
7. 1 paper in Engineering Drawing (drawing random nuts and bolts, locus of point etc)
8. 1 paper in Electronics
9. 1 paper in Mechanical Workshop (sheet metal, wooden work, moulding, metal casting, fitting, lathe machine, milling machine, various drills)
And when you jump in real life scenario, you encounter source/revision/version control, profilers, build server, automated build toolchains, scripts, refactoring, debugging, optimizations etc. As a matter of fact none of these are touched in the course.
Sure, they teach you a large set of algorithms, but they don't tell you when to prefer insertion sort over quick sort, quick sort over merge sort etc. They teach you Las Vegas and Monte Carlo algorithms, but they don't tell you that the randomizer in question should pass Die Hard test (and then you wonder why algorithm is not working as expected). They teach compiler theory, but you cannot write a simple parser after passing the course. They taught you multicore architecture and multicore programming, but you don't know how to detect and fix a race condition. You passed entire engineering course with flying colors, and yet you don't know ABC of debugging (I wish you encounter some notorious heisenbug really soon). They taught 2-3 programming languages, and yet you cannot explain simple variable declaration.
And then, they say that you should have knowledge of multiple fields. Oh well! you don't have any damn idea about your major, and now you are talking about knowledge in multiple fields?
What is the point of such education?
PS: I am tired of interviewing shitty candidates with flying colours in their marksheets. Go kids, learn some real stuff first, and then talk some random bullshit.

TFW trying to delete something, but some random background program has a unclosed handle on it

How I solve my problems..😆😆

The only useful indicator of code-quality is the wtf-per-minute scale.

A super creepy webcrawler I built with a friend in Haskell. It uses social media, various reverse image searches from images and strategically picked video/gif frames, image EXIF data, user names, location data, etc to cross reference everything there is to know about someone. It builds weighted graphs in a database over time, trying to verify information through multiple pathways — although most searches are completed in seconds.

I originally built it for two reasons: Manager walks into the office for a meeting, and during the meeting I could ask him how his ski holiday with his wife and kids was, or casually mention how much I would like to learn his favorite hobby.

The other reason was porn of course.

I put further development in the freezer because it's already too creepy. I'd run it on some porn gif, and after a long search it had built a graph pointing to a residence in rural Russia with pictures of a local volleyball club.

To imagine that intelligence agencies probably have much better gathering tools is so insane to think about.

Simple and Clear 👍

I love writing and using my own apps!

Was just using 2 of them but found a new annoyance...

No problem! Open the source code, add the functionality, publish and install 😆

10 minutes after... All good and better 😁