Best programming language since Chef:

https://github.com/dylanbeattie/...

Today I needed the scroll lock key.

I was running a super long test suite, one which puts a green dot on the screen every 500ms, so you can't scroll up. I needed to view some output of an earlier command... in other words, I needed to lock the automatic scrolling of the terminal.

That is what the scroll lock key was made for.

A momentous occasion.

Then I found out that a while ago, I used the macro function of my keyboard to rebind the that key... to close the current terminal window. 😡

*Admin leaves his computer unlocked*

1. Takes a desktop screenshot and flips it and sets it as background.
2. Disables right click.
3. Hides taskbar.
4. Flips the screen.
5. Connects keyboard to another computer close by with screen off.
6. Has the time of the week.

*Hopefully, there is no revenge 😁*

Being paid to rewrite someone else's bad code is no joke.

I'll give the dev this, the use of gen 1,2,3 Pokemon for variable names and class names in beyond fantastic in terms of memory and childhood nostalgia. It would be even more fantastic if he spelt the names correctly, or used it to make a Pokemon game and NOT A FUCKING ACCOUNTANCY PROGRAM.

There's no correspondence in name according to type, or even number. Dev has just gone batshit, left zero comments, and now somehow Ryhorn is shitting out error codes because of errors existing in Charmeleon's asshole.

The things I do for money...

I'll be moving to a new job soon. Myself and a colleague are working on a new feature before I leave. He's building an IoT device, i'm doing the backend work. Were testing a "ping" style system, where his IoT device replies to a message from the backend.

The JSON payload he's sending is {traitor: true}

(!dev)

Fuck Twitter.

I get sucked in for 10 minutes through some news article, and my blood is boiling.

I think the platform does not even deserve to exist.

And I didn't think I would ever say that.

I used to be a staunch defender of the free & open internet, even with it's ugly and extreme sides, because I was convinced the good would outshine the evil.

I displayed the Pirate flag with pride on the mast outside of my house, I was intimately involved in the founding of their political party in my country. I was convinced of the power of the internet, I believed it would empower democracy and debate.

So why do simple tweets, even just the ones about technology, incite an endless stream of vile ultranationalist & misogynist hate?

How is it that those who are reasonable get drowned out?

That fucking character limit is a cancer.

The orator's wings are clipped. The richness of language is wilting before our eyes. All that remains are a bunch of caged chickens pecking every argument to death.

I will defend the right to free speech, even when it comes to the most disagreeable and controversial opinions.

But Twitter does not promote free speech. It's poison to free speech.

It's an endless torrent of non sequiturs, which constricts all reason and intellect. It replaces free speech by pretending to have equal value.

I really don't care if you are left or right, socialist or libertarian, globalist or nationalist.

You can argue to me that we should close all borders for immigrants, that Apple makes great products, that genocide has its pros, you could try to convince me that Heineken tastes acceptable (sorry AlexDeLarge), that Linux should be outlawed or that we should really try to bring this Eugenics thing back again.

Just be fucking rational -- and "Rationality implies the conformity of one's beliefs with one's reasons to believe"

You can NOT fit both your beliefs and their supporting reasons in 140 or even 280 characters.

So what's left is just your beliefs.

Stripped of all reason.

Repeat it often enough, keep spewing, keep throwing out incomplete arguments, and you'll train yourself to forego ratio in your convictions completely.

All social platforms should get a forced captcha for every spelling/grammar error, and a 1000 character minimum.

The world would be a slightly better place.

The GET /users endpoint will return a page of the first 13 users by default.

To request other pages, add |-separated querystring with the limit and offset, as roman numerals enclosed in double quotation marks. Response status is always equal to 200, plus the total count of the resource, or zero when there's an error.

You can include an array of friends of the user in the result by setting the request header "friends" to the base64-encoded value of the single white pixel png.

Other metadata is not included by default in responses, but can be requested by appending ?meta.json to any endpoint, which will return an xml response.

If you want to update the user's profile picture, you can request an OAuth token per fax machine, followed by a pigeon POST capsule containing a filename and a rolled up Polaroid picture. The status code attached to the return postal dove will be the decimal ASCII code for a happy smiley on success, and a sad smiley if any field fails form validation.

-- Every single external REST API I've ever worked with.

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!"

If Gordon Ramsay made code reviews, I would watch that show. Especially the insults he would use for handling clients.

"This code has so much spaghetti, it decided to open it's own restaurant"

Windows 10 is like a vagina with testicles:- it makes no sense

$Me: *whispers* Do you like it rough baby?

$Her: *moans* uhuh

$Me: *continues whispering* I'm gonna implement a dynamic programming algorithm for you.

$Her: ahhhhhhh yaass *looses control of her body*

Fictional scenario of course I'd never implement shit for nobody who isn't paying.

Quote of the day:
“Don‘t ever miss a good occasion to shut up!”

Don't mind me, just writing maintainable, legible, commented and documented code. What's that, an email validation? Let me just
/^(([^<>()\[\]\.,;:\s@\"]+(\.[^<>()\[\]\.,;:\s@\"]+)*)|(\".+\"))@(([^<>()[\]\.,;:\s@\"]+\.)+[^<>()[\]\.,;:\s@\"]{2,})$/i

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.

Storytime!

This customer comes in and practically throws a computer on the counter.

Customer: This computer isn't working. I've ran the diagnostics and it says it's software. *places a dvd case with a 32 bit Windows 7 disk in it on the counter* It had Windows 10 on it, but I want Windows 7 on it.

Me: Well, you may have issues with the drivers if you put Windows 7 on it--

Customer: I don't care, I just want Windows 7.

Me: You SHOULD care. That means no wifi, no display, no mouse... Windows 7 doesn't like Windows 10 hardware.

Customer: Then... check to see Windows 7 compatibility!

Me: Alright.... *makes notes to check for Windows 7 compatibility*

Me: So has this Windows 7 been used before?

Customer: Yes, it has.

Me: On how many computers?

Customer: I've installed it on two computers and it works just fine.

Me: That's weird because Windows license keys are for one computer only. Are both of them connected to the internet?

Customer: Yes.

Me: Well, okay then... *finishes up ticket*

Customer: I work in this field and I just don't understand why they don't come with the disks anymore. How much is a Windows 10 disk?

Me: *gives price*

Customer: And do you have any?

Me: Let me check *I go to where they are, find some and come back out*

Me: Unfortunately we're out at the moment and would have to special order some back in.

Customer: OK. So then how much to fix this computer?

Me: *price of installing Windows and backing up data*

Customer: That's halfway to the price of a new one of these!

Me: Well yes, an HP at Walmart... But you do have that option if you want to take it.

Customer: Well, why does it cost that much?

Me: Well, it's $labor1 to install Windows, $labor2 to do some basic setup and drivers, and $labor3 to backup and restore data.

Customer: Oh, well I don't want data.

Me: Okay, well then it would be $total - $labor3

Customer: ...Okay, fine

Me: *updates the ticket*

When she finally left I put it on the bench and the first message said "SMART ERROR." I then did 4 different tests that said "lol, the hard drive is failing."

If you "worked in this field," you would know that a SMART error is hard drive related.

If you worked in this field, you would know that Windows is only a 1PC license, so why are you lying about installing it with no issues on other computers?

If you worked in this field, you would know you would want a 64bit Windows on your computer.

If you worked in this field, you would know how to find a Windows 10 installation media online.

If you worked in this field, you would know that HPs are not good computers to get.

IF YOU FUCKING WORKED IN THIS FIELD YOU WOULDN'T BE SUCH A FUCKING CUNT.

"The difference between SSDs and HDDs is that HDDs store data on spinning CDs inside the drive"
-- a 3rd year CS student

Spinning CDs?? CDs?!?!?

Buzzword dictionary to deal with annoying clients:

AI—regression
Big data—data
Blockchain—database
Algorithm—automated decision-making
Cloud—Internet
Crypto—cryptocurrency
Dark web—Onion service
Data science—statistics done by nonstatisticians
Disruption—competition
Viral—popular
IoT—malware-ready device

Rough analysis of LinkedIn inmail’s I get:

Hi <5% of time, not my name>,

I was looking at your profile <97% a lie>. I was very impressed with your <10% something I’ve never done> experience working for <5% a company I’ve never heard of>. Would you be interested in hearing more about <60% a job I’m not suited for>, they offer amazing benefits and have a great culture!

... no

A while ago I encountered this atrocity

Well, it happened. The stupidest request, no demand, I have ever, and most likely will ever receive...

Me: So what is it you're looking to do with your website.

Client: We're not showing up Facebook's home page. We need you to fix that. We have a budget of $10,000 to make this happen right now.

Me: As much as I'd love to take your money, that isn't something I can control. Every "home page" is profile-based, which technically isn't a homepage, but a "feed" that changes constantly. So say you create a profile on Facebook, only those you follow, and paid posts show up on your feed. What I can do however is use your budget to create and promote posts from your company page to show on users' feeds. If you're serious about marketing, we can start slow at $250/week, then work our way up or down based on results until your budget is exhausted, then re-evaluate the budget at that time. I can tailor a retainer for you based on the number of ads per week that you'd like to make.

Client: No, this is not what we're asking for at all.

Me: Okay...what is it you're looking for exactly? Run through this in as much detail as possible so I can get on the same page.

Client: We want to be on the main home page of facebook.com. We want our logo on that page when people sign up to make an account, linking to our website.

Me: That's simply not possible. That's Facebook's own home page. Nobody has a right to edit that other than Facebook itself.

Client: Bullshit. There's a Facebook developers section with APIs to edit and view Facebook's entire website. We would do it ourselves, but we signed up and don't understand how to change it in Chrome. That's why we need you and [referring client] said you were the best guy for our needs.

Me: That API has no control over Facebook's corporate data, including their own home page. That API designed ONLY for sections in which you are authorized to access or modify, such as your personal profile or created page for your business.

Client: We know that it can be done. If you don't do it, we'll find someone else who can.

Me: Well good luck with that, because the only way it would be remotely possible to do that WILL involve prison time, since that would be illegal. The only legal way to do it would be to buy Facebook, and they'll laugh you out of the building with that offer. But I'm done with this conversation because I have work to complete from clients that aren't delusional. Have a nice day! [hang up]

----

What. The. Fuck.

Client: Where are we with the project, it's been a week and I see nothing.

Me: You asked me to do something that was not in the agreed scope of work, which has kept me from starting on the project.

Client: Do I need to plan out everything in advance on paper for you to get it done in a timely manner?

Me: Is that a serious question? Yes, you should. That's the whole point of creating a scope of work. It's to allow me to schedule out the time necessary to build out a product in a "timely manner".

Client: I don't appreciate your attitude. This is not how you should be doing business if you like making money.

Me: I don't appreciate your condescending, unreasonable, dickhead mentality that makes you think it's remotely okay to act like you're better than me. Money doesn't grant you the right to be a dickwad, and just because I'm being paid doesn't mean I have to put up with any level of arrogance or disrespect.

I am in this business to make money, but not at the cost of my dignity and self-respect. You will be receiving a full refund later today, not because I have to provide a refund, but because I never want to communicate with you ever again moving forward. Take your unacceptable bullshit somewhere else.

You know who sucks at developing APIs?

Facebook.

I mean, how are so high paid guys with so great ideas manage to come up with apis THAT shitty?

Let's have a look. They took MVC and invented flux. It was so complicated that there were so many overhyped articles that stated "Flux is just X", "Flux is just Y", and exactly when Redux comes to the stage, flux is forgotten. Nobody uses it anymore.

They took declarative cursors and created Relay, but again, Apollo GraphQL comes and relay just goes away. When i tried just to get started with relay, it seemed so complicated that i just closed the tab. I mean, i get the idea, it's simple yet brilliant, but the api...

Immutable.js. Shitload of fuck. Explain WHY should i mess with shit like getIn(path: Iterable<string | number>): any and class List<T> { push(value: T): this }? Clojurescript offers Om, the React wrapper that works about three times faster! How is it even possible? Clojure's immutable data structures! They're even opensourced as standalone library, Mori js, and api is great! Just use it! Why reinvent the wheel?

It seems like when i just need to develop a simple react app, i should configure webpack (huge fuckload of work by itself) to get hot reload, modern es and jsx to work, then add redux, redux-saga, redux-thunk, react-redux and immutable.js, and if i just want my simple component to communicate with state, i need to define a component, a container, fucking mapStateToProps and mapDispatchToProps, and that's all just for "hello world" to pop out. And make sure you didn't forget to type that this.handler = this.handler.bind(this) for every handler function. Or use ev closure fucked up hack that requires just a bit more webpack tweaks. We haven't even started to communicate to the server! Fuck!

I bet there is savage ass overengineer sitting there at facebook, and he of course knows everything about how good api should look, and he also has huge ass ego and he just allowed to ban everything that he doesn't like. And he just bans everything with good simple api because it "isn't flexible enough".

"React is heavier than preact because we offer isomorphic multiple rendering targets", oh, how hard want i to slap your face, you fuckface. You know what i offered your mom and she agreed?

They even created create-react-app, but state management is still up to you. And react-boierplate is just too complicated.

When i need web app, i type "lein new re-frame", then "lein dev", and boom, live reload server started. No config. Every action is just (dispatch) away, works from any component. State subscription? (subscribe). Isolated side-effects? (reg-fx). Organize files as you want. File size? Around 30k, maybe 60 if you use some clojure libs.

If you don't care about massive market support, just use hyperapp. It's way simpler.

Dear developers, PLEASE, don't forget about api. Take it serious, it's very important. You may even design api first, and only then implement the actual logic. That's even better.

And facebook, sincerelly,

Fuck you.

My "Coding Standards" for my dev team

1.) Every developer thinks or have thought their shit don't stink. If you think you have the best code, submit it to your peers for review. The results may surprise you.

2.) It doesn't matter if you've been working here for a day or ten years. Everyone's input is valuable. I don't care if you're the best damn programmer. If you ever pull rank or seniority on someone who is trying to help, even if it isn't necessarily valid or helpful, please have your resume ready to work elsewhere.

3.) Every language is great and every language sucks in their own ways. We don't have time for a measuring contest. The only time a language debate should arise is for the goal of finding the right one for the project at hand.

4.) Comment your code. We don't have time to investigate what the structure and purpose of your code is when we need to extend upon it.

5.) If you use someone else's work, give them the credit in your comments. Plagiarism will not be tolerated.

6.) If you use flash, you will be taken out back and shot. If you survive, you will be shot again.

7.) If you load jQuery for the sole purpose of writing a simple function, #6 applies.

8.) Unless it is an actual picture, there is little to no reason for not utilizing CSS. That's what it's there for.

9.) We don't support any version of Internet Explorer and Edge other than the latest versions, and only layout/alignment fixes will be bothered with.

10.) If you are struggling with a task, reach out. While you should be able to work independently, it doesn't make sense to waste your time and everyone else's to not seek assistance when needed.

11.) I'm serious about #6 and #7. Don't do it.

Confessions of a Programmer

#1
If a client is an unbearable asshole during the initial communication, I look for every excuse to pad on the hours for the estimate to get paid more. If a client goes above and beyond in their douchbaggery, I tack on an additional $40/hour.

#2
Sometimes I will present an elaborate solution to a client, but really I'm just reading off the features of a plugin or library I'm going to download or buy after the call. Not because I can't build it myself, but because I'd rather spend more time on other/my own projects.

#3
Clients assume because I know one language, I know them all. Rather than turning down the work, I take a crash course to work in that language, or outsource the work and clean it up afterwards, whichever is more practical at the time.

#4
I use cPanel on a dedicated to manage our client websites. I'm not paid enough to bother with setting up everything manually.

#5
Certain projects I build have a 3-day backdoor built into it. If the client doesn't pay upon completion, a unique hash triggered as a GET variable deletes a core file in my work, rendering the work useless. If it wasn't triggered by the 4th day, the file allowing me to trigger this backdoor is removed. This is only used for clients where the project must be launched on their servers, or if there has been a previous issue collecting payment.

#6
I slip in the initial contract that all preceeding phone calls will be monitored and recorded, and that they acknowledge the recordings are admissable in court. This has saved me from losing money twice now.

#7
I have never used an IDE. (I know, I know, it's really inefficient and dumb, but I'm just more comfortable with Sublime. Plus I often find myself mobile and without my computer, so I have to program from my phone.)

#8
Each day resembles a betting spectacle of which work will be late, which will be rushed out and which will never see the light of day.

#9
I have used "sick" and "family emergency" as an excuse to just sleep in far more than I can count.

#10
When a client from hell crosses over the line in their conduct (such as getting very nasty and personal, or sending threats), I anonymously report them to the BBB and on RipOffReport.

That feeling when you run out of YouTube videos to watch and end up in some weird ass corner of the internet watching some dude scream "lemons!" at his fish for 12 minutes.

Seen as most devs listen to music while programming, I'm curious what music you listen to? Playlist are welcome too!

Working really hard, finishing tasks, upgrading servers. Cancel some useless meetings to finish up features, working till 2am to get a database migration working. Half of the platform is transformed, both customers and team are very happy about their accomplishments.

Boss: "OK, I think we're on the right path with these changes, but productivity and morale is honestly disappointing. Are you guys sleeping enough? You all look very tired and unmotivated!"

Attend all meetings, call boss at 7am to discuss random purchases like a whiteboard, run around the office holding a (broken, lol) MacBook, looking very busy & slightly worried. I shout random things at people across the office like "Nice work Gary!" and "Damn, you are on a roll Angela!". I initiate smalltalk with department heads, only to immediately disrupt the conversation by checking my phone saying "Oh I really have to take this one" (empty battery, lol). No one writes a single line of code for four weeks, and nothing new has been deployed by the whole team.

Boss: "I think it's commendable how productive the team has become this month. You guys are all so active and involved. A real improvement!"

I got my wife pregnant despite birth control being used... You could say she *puts on sunglasses* failed the penetration test.

I'll see myself out.

Today the inconceivable happened at the office. A rather attractive female colleague of ours asked if anybody could help her with a Java related issue.
Of course the majority of guys were more than willing to help.
A victor finally emerged. He went on to claim his prize by helping the fair maiden.
After a few seconds..."This is not Java. It's javascript'
I shit you not we just exploded in laughter 😂

I call my git repos the field hospital.

I didn't finish my studies, but I seem to be the most qualified person to pick up the scalpel. Big corner of body bags. New brilliant ideas arrive, I do what I can with the time I have. Sometimes something survives, but it's usually too heavily mutilated to fully function. Unfinished refactorings develop into hardened scar tissue, the feature creep starts festering and leaking.

I should get better at triaging, just deleting old crap, pick one project and nurse it back to health.

But it's not easy to start with fresh focus, when your keyboard is still soaked in booze and the blood and tears of all the victims you've butchered.