1. If your contract allows it (and it should), get more involved in public dev community. Your employer benefits greatly from making a small closed source core product, with a giant open source ecosystem around it. Write public articles. Working in a community larger than one single business is fun.

2. Start a company coding club, a "labs" division, work in a slightly more exotic language. Great if your employer gives you time, but using some of your own is worth it too. Work on non critical tools, creative experiments. Sometimes you stumble onto incredibly valuable ideas which would never have popped up if you had strictly followed stakeholder requirements.

3. Listen to your body. If you feel restless, go for a run. If you feel tired, take a nap. If you're stuck, wander around the company. If you feel down, go find a place with more than a dozen trees. And always have a notepad nearby for doodling!

Linux Directories cheat sheet ✌️

😀😊😊😉😉😂😂

I decided to make some new icons for Atom editor (the launcher/executable ones), because I liked the vscode-icons project.

Made the repo on GitHub and decided to automate making the icons for different OS using Travis CI.

Started writing the Python Script for Travis.
My google queries:

How to generate icons for Linux?
I can use SVG or generate a PNG, many libraries available. 👍👍

How to generate icons for Windows?
Generate PNGs of various sizes and pack in an .ico file. Easy enough

So far so good.

How to generate icons for Mac?
Mac needs a .icns file, a package of PNGs of various sizes. Libraries available but can be done on OSX only. 😫😫

Then I think, what OS does Travis use?
Oh, I can specify macOS in it 😁😁😁

Starts the build 😎😎

Travis doesn't support Python on macOS

😑😑😑😑

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"

Boss: "I don't want to comply with the GDPR"

Me, DPO: "I've told you the house rules. You must comply, stop arguing"

Boss: "But I don't want it. Bobby doesn't have to, and Eve doesn't have to, their moms are cool"

Me: "I don't give a crap about the other kids, you're going to be GDPR compliant. Bob and Eve will end up being raped in prison. It's that what you want?"

Boss: "What if I just pretend to do it."

Me: "I'll take away all your marketing toys. No more mailchimp for you young man."

Boss, crying: "You wouldn't touch my Facebook pixel!"

Me: "Especially your Facebook pixel. I'm so sick of that thing...."

Me: "...Look, you can still play with your toys, all I'm saying is you need to be honest and ask your buddies for consent before you put your pixels up their various holes"

Boss: "But they will never agree!"

Me: "Maybe that is good thing"

Boss: "But how will we get people to like us if I can't feed them pills and insert probes into their holes to measure their responses?"

Me: "Maybe you should focus on being a nice kid, someone people like to play with. Your buddies will tell other kids that you're a nice guy. Now, I'm not going to lie to you, it will be hard work. Much more effort than what you're doing now. But you know, those friends will stick with you for decades, instead of just until the marketing-drugs wear off"

Boss: "I think I want a new mom"

Me: "You signed a contract. You're stuck with me for the next 2 years. And as long as you're living under my roof, you will follow my rules."

Not really Dev advice, but I appreciated it.
"Do your best to take responsibility for everything that happens to you. Even if it's not your fault."
"On the flip side, never apologize for something that isn't your fault. That includes other people's feelings. You're not in control of their emotions."

Nice job, Zuckerberg

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.

Just....

You'll have more pain convincing people that you CAN write a decent app in PHP, than writing one.

#noHatePlz