Running an Alpaca farm in rural Finland, next to some mountain creek with an oldschool water mill so I can grind flour and coffee beans.

I hated people so I tried to find solace as a nerd in technology, but tech is also fucking awful so I feel like retiring in a tranquil forest with some equally grumpy wooly animals.

If I get eaten by a bear because I'm a skimpy city boy that's OK, more epic than being found decomposing slumped over on a keyboard in the boring grey suburbs.

All of this is probably pandemic-me talking though. So sick of this concrete city with the farting cars and fat obnoxious shoppers.

I need some trees around me, and some mammals with a higher IQ than my current neighbors.

This is more just a note for younger and less experienced devs out there...

I've been doing this for around 25 years professionally, and about 15 years more generally beyond that. I've seen a lot and done a lot, many things most developers never will: built my own OS (nothing especially amazing, but still), created my own language and compiler for it, created multiple web frameworks and UI toolkits from scratch before those things were common like they are today. I've had eleven technical books published, along with some articles. I've done interviews and speaking engagements at various user groups, meetups and conferences. I've taught classes on programming. On the job, I'm the guy that others often come to when they have a difficult problem they are having trouble solving because I seem to them to usually have the answer, or at least a gut feel that gets them on the right track. To be blunt, I've probably forgotten more about CS than a lot of devs will ever know and it's all just a natural consequence of doing this for so long.

I don't say any of this to try and impress anyone, I really don't... I say it only so that there's some weight behind what I say next:

Almost every day I feel like I'm not good enough. Sometimes, I face a challenge that feels like it might be the one that finally breaks me. I often feel like I don't have a clue what to do next. My head bangs against the wall as much as anyone and I do my fair share of yelling and screaming out of frustration. I beat myself up for every little mistake, and I make plenty.

Imposter syndrome is very real and it never truly goes away no matter what successes you've had and you have to fight the urge to feel shame when things aren't going well because you're not alone in those feelings and they can destroy even the best of us. I suppose the Torvald's and Carmack's of the world possibly don't experience it, but us mere mortals do and we probably always will - at least, I'm still waiting for it to go away!

Remember that what we do is intrinsically hard. What we do is something not everyone can do, contrary to all the "anyone can code" things people do. In some ways, it's unnatural even! Therefore, we shouldn't expect to not face tough days, and being human, the stress of those days gets to us all and causes us to doubt ourselves in a very insidious way.

But, it's okay. You're not alone. Hang in there and go easy on yourself! You'll only ever truly fail if you give up.

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

For Windows driver update, found a great (open source) tool to update or install missing drivers.

https://sdi-tool.org/

My dell laptop (Windows 10) screen used to go blank or some bubble used to appear may times a day. Used Dell driver update tool, no update, says all driver up to date.

Then used Snappy Driver Installer tool, which detected my laptop details correctly.

Then it showed that my display driver was almost a year old and there were couple of updates, latest being just last month. In addition to that, there were 30+ updates on disk drivers, networking, sensors, bluetooth, audio etc.

First updated my display driver, upon success, slowly updated the rest of it. Now, the system worked entire day without any issue. Also, my laptop fan used to run full speed seems to have slowed down.

Also, my external monitor clarity has improved.

ps: worked for me, but be careful. Check it thoroughly before updating, update only those drivers which are giving trouble and there are no updated drivers available from windows or manufacturers.

1. The quality of the coffee and toilet paper you encounter during an interview tells you more than promises about table tennis or fruit baskets.

2. Try to determine who their primary client is: subscribers, app buyers, advertisers, etc. It's a major influence on the company dynamic.

3. Before an interview, you can just say: "I would like to sit down with a PO and run through one backlog feature and one bug, to get a feel for the type of tasks at the company". Such an activity immediately reveals team structure, whether they have product owners & scrum masters, what a sprint looks like, how they prioritize tasks, and how organized/chaotic your work experience will be.

Share your most useful terminal aliases and functions.

alias gs='git status'
alias gcm='git commit -m'
alias push='git push'
alias pull='git pull'
alias hosts='sudo nano /etc/hosts'
alias glog='git log --graph --oneline --decorate -n 10 --color'
alias mykey='cat ~/.ssh/id_rsa.pub | xclip -sel clip'

function mkcd () {
mkdir -p -- "$1" && cd -P -- "$1"
}

As well as one for each major project (lets say 1+ weeks of dev time) to immediately cd to it from anywhere. How about you guys?

Always looking to improve my terminal commands, so am curious what everyone else uses for shortcuts.

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"

Time to move my mailserver!
I am having an inner struggle about what distro/OS to use:

Debian
CentOS
Ubuntu
FreeBSD
OpenBSD

What should I use? Why?

Just found this website for Regular Expressions:
https://regex101.com/

In-case anyone struggles like I do

A small story on digitalization

I had spent an hour in the bank with my dad, as he had to transfer some money. I couldn't resist myself & asked:

Dad, why don't we activate your internet banking?

''Why would I do that?'' He asked, ''Well, then you wont have to spend an hour here for things like transfer.

You can even do your shopping online. Everything will be so easy!

I was so excited about initiating him into the world of Net banking.

He asked, If I do that, I wont have to step out of the house?

''Yes, yes''! I said. I told him how even grocery can be delivered at door now and how amazon delivers everything!

His answer left me tongue-tied.

He said ''Since I entered this bank today, I have met four of my friends, I have chatted a while with the staff who know me very well by now.

Two years back I got sick, The store owner from whom I buy fruits, came to see me and sat by my bedside and cried.

When u r Mom fell down few days back while on her morning walk. Our local grocer saw her and immediately got his car to rush her home as he knows where I live.

Would I have that 'human' touch if everything became online?

I like to know the person that I'm dealing with and not just the 'seller'. It creates bonds. Relationships.

Does "online" deliver all this as well?

Technology isn't life #BeHuman

For those who are not getting the context, this things happen in India. It is truth not a fact.

So many developer that does not know how to generate a simple .csr file. Here you go:

$DOMAIN=www.yourdomain.com
$STATE=State
$CITY=The city
$COMPANY=Company Name Gmbh
openssl req -utf8 -nameopt multiline,utf8 -new -newkey rsa:2048 -nodes -sha256 -out $DOMAIN.csr -keyout $DOMAIN.key -subj "/C=Your CountryCode/ST=$STATE/L=$CITY/O=${ORG:-$COMPANY}/OU=${ORG:-IT}/CN=$DOMAIN"

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.

25 phrases you wish you could say at work more often

(Warning: Contains naughty words...:-)))

1. Ahhh...I see the fuck-up fairy has visited us again...

2. I don't know what your problem is, but I'll bet it's hard to pronounce.

3. How about never? Is never good for you?

4. I see you've set aside this special time to humiliate yourself in public.

5. I'm really easy to get along with once you people learn to worship me.

6. I'll try being nicer if you'll try being smarter.

7. I'm out of my mind, but feel free to leave a message...

8. I don't work here. I'm a consultant.

9. It sounds like English, but I can't understand a word you're saying.

10. I can see your point, but I still think you're full of shit.

11. I like you. You remind me of me when I was young and stupid.

12. You are validating my inherent mistrust of strangers.

13. I have plenty of talent and vision. I just don't give a damn.

14. I'm already visualizing the duct tape over your mouth.

15. I will always cherish the initial misconceptions I had about you.

16. Thank you. We're all refreshed and challenged by your unique point of view.

17. The fact that no one understands you doesn't mean you're an artist.

18. Any connection between your reality and mine is purely coincidental.

19. What am I? Flypaper for freaks!?

20. I'm not being rude. You're just insignificant.

21. It's a thankless job, but I've got a lot of Karma to burn off.

22. Yes, I am an agent of Satan, but my duties are largely ceremonial.

23. No, my powers can only be used for good.

24. You sound reasonable... Time to up the medication.

25. Who me? I just wander from room to room

FUCK PHP!!!
We were trying to go live with a big online shop, it is connected through a crappy API to SAP.
PHP keeps outputting fucking errors because our intern doesn't fucking know how to properly write PHP.

YEAH, JUST FUCKING RETURN A WHOLE DIFFERENT TYPE OF DATA IF THE FUNCTION HAS AN ERROR.

Oh and using fucking strtr( ... ) to insert stuff in a string is REALLY FUCKING 1337...

And when you think the whole fuckery has reached the summit, just look at how HE FUCKING CREATED THE UGLY EMAIL TEMPLATE:
$content .= "UGLY HTML ABOMINATION";
$content .= "MORE UGLY HTML";
$content .= "HTML WITH SPELLING ERRORS";
$content .= "<table>";
$content .= "TEARS OF TIM BERNERS LEE";
$content .= "<table>HE FOGOT THE FUCKING '/'";

and dozens more of these lines...

and the whole piece for ALL 3 FUCKING LANGUAGES...

Thanks for writing the fucking backend stuff, it is better to rewrite the whole piece.

If Programming Languages Were Girls:

Java: Your current girlfriend, you've been going steady for a while now. Things are okay.

Kotlin: The girl Java finds you cheating on, she's just amazing, and you wish you'd met her sooner.

Visual Basic: The girl you accidentally started a relationship with because you didn't know how to say no. But quickly realised your mistake and regretted it.

JavaScript: A childhood friend you occasionally hook up with. But you could never settle for a relationship with them.

Python: A bossy, manipulative girl who quickly turned things sour. But everyone else loves her because of her huge libraries.
-----------------------------------------------------
My and a co worker were joking the other day about what programming languages would be like if they were girls. This is what we came up with (Original inspiration: the Distracted Boyfriend meme (Feel free to add your own!)).

Reading my old rants, I am happy that I evolve

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.

Ohhh helll nooooo

It happens all the time...

Dream big

Hahaha

please contact god for detail information

CSS - keep guessing the values until it looks fine.

That moment when your password is constantly rejected and you realize that the fucking NUM LOCK IS OFF.
(ノಠ益ಠ)ノ彡┻━┻
(⌐■_■)–︻╦╤─ 💻

When you take User Experience to the next level. Just what I was thinking

Credits : Riot App