Looping around!

Please patch him through 🤣🤣🤣

At my previous job a coworker left positive comments alongside any negative ones on my code. “Nice job here. Very clean”, or “nice use of X design pattern here!” Kinda made me look forward to his code reviews.

this is it!

Lose some ...

Saw this on Reddit

When we finally get to Mars, all programmers on Earth will scream in pain over having to program another timezone

Difference between C# and Javascript
Me: Hold my cup of tea.
C#: That's not a cup of tea.
Me: Hold my cup of tea, with two teaspoons of sugar in it.
C#: That's not a cup of tea with two tea spoons of sugar in it.
Me: Hold my cup of tea, with two teaspoons of sugar and milk in it.
C#: That is not a cup of tea, with two teaspoons of sugar and milk it.
...
Me: Hold my cup of tea.
Javascript: I'll hold your cup of coffee.

Professor : Explain deadlock and I will give you full marks.

Me:- You give me full marks and I'll explain deadlock.

Found this on fb

Why Does Python lives on Land?

Because it is above C level

Exactly

Pro tip: If you are a junior, or senior but new at the company, don't start your conversations with:

"We're doing X wrong. At my previous company we did / at school I learned /in this book I read / according to this talk I watched, the right way to do X is ..."

Instead try:

"I'm curious why were doing X this way. I'm used to doing it differently."

I love flat-hierarchy teams, and people who think about flaws in procedures and proactively try to improve the tools we use are awesome, but the next kid walking up to me yelling we use git flow "wrong" will be smacked in the face with a keyboard.

If you come to me with curiosity and an open mind, I'll explain, and even return the favor by behaving the same way when I'm baffled by your seemingly retarded implementations.

Maybe we can learn from each other, maybe discover that "how I learned it" is sometimes good, sometimes bad.

But let's start with some social skills, not kicking off into every debate with a stretched leg and a red face.

Jetbrains products 👌👌👌👌

WTF!!!

Am I the last one here late to the party? Just try out and impressed by VSCode and this is my thoughts about the editors:

- I have been loyal to Sublime Text for like 5+ years, cannot complain much.
- Notepad++ was my first love, but absent on Linux so got to say goodbye.
- VSCode is the latest I try out and very rare one I could spend a couple of hours to dive into its settings to make it easier to use. The extensions are impressive!
- Atom, Bracket, and those blabla of their kind are bullshit.
- Jetbrains products are heavy ass, I can't even take a note!
- Vim is great too, but it's not the thing that I can just "open up and start typing".
- Have no idea about Emacs, but supposedly it's nowhere near its UI-friendly brothers, so I give no patience.

Redid my portfolio site again. Feel like I could make a portfolio site of portfolio sites at this point. On the plus side, I guess I’m learning new things each time?

Nice learning experience from Spotify. If a survey response might contain negative feedback, just don't allow it to submit.

Clever Spotify ;)

Current mood

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.

You know this is you everytime...

Last year I built the platform 'Tindex'. It was an index of Tinder profiles so people could search by name, gender and age.

We scraped the Tinder profiles through a Tinder API which was discontinued not long ago, but weird enough it was still intact and one of my friends who was also working on it found out how to get api keys (somewhere in network tab at Tinder Online).

Except name, gender and age we also got 3 distances so we could calculate each users' location, then save the location each 15 minutes and put the coordinates on a map so users of Tindex could easily see the current location of a specific Tinder user.

Fun note: we also got the Spotify data of each Tinder user, so we could actually know on which time and which location a user listened to a specific Spotify track.

Later on we started building it out: A chatbot which connected to Tinder so Tindex users could automatically send a pick up line to their new matches (Was kinda buggy, sometimes it sent 3 pick up lines at ones).

Right when we started building a revenue model we stopped the entire project because a friend of ours had found out that we basically violated almost all terms.

Was a great project, learned a lot from it and actually had me thinking twice or more about online dating platforms.

Below an image of the user overview design I prototyped. The data is mock-data.

( ͡° ͜ʖ ͡°)

"Knock, knock."
"Race condition."
"Who's there?"

Best clickbait ever.

I'm at my seat during the regular morning routine of checking emails, planning the things I need to complete/study when my phone rings.

HR: Good Morning, can you come over to the conference room please ?

Me: Sure

I enter the conference room and on the other side of the table, I see a group of 3 HR Managers (not a very nice feeling), especially when it was 10 months into my first job as a Trainee Software Developer.

HR: The company hasn't been performing as expected. For this reason, we've been told to cut down our staff. We're sorry but we have to let you go. You've been doing a great job all along. Thank you.

Me: ---- (seriously ?!)

The security-in-chief 'escorts' me out of the premises and I hand over the badge. I'm not allowed to return to my desk.

This happened about 16 years ago. But it stuck with me throughout my programming career.

A couple of Lessons Learnt which may help some of the developers today :

- You're not as important as you think, no matter what you do and how well you do it.
- Working hard is one thing, working smart is another. You'll understand the difference when your appraisals comes around each year.
- Focus on your work but always keep an eye on your company's health.
- Be patient with your Manager; if you're having a rough time, its likely he/she is suffering more.
- Programming solo is great fun. However it takes other skills that are not so interesting, to earn a living.
- You may think the Clients sounds stupid, talks silly and demands the stars; ever wonder what they think about you.
- When faced with a tough problem, try to 'fix' the Client first, then look for a solution.
- If you hate making code changes, don't curse the Client or your Manager - we coders collectively created a world of infinite possibilities. No point blaming them.
- Sharing your ideas matter.
- Software Development is a really long chain of ever-growing links that you may grok rather late in your career. But its still worth all the effort if you enjoy it.

I like to think of programming as a pursuit that combines mathematical precision and artistic randomness to create some pretty amazing stuff.

Thanks for reading.

Sooo my friend asked my to become more active on steam and i did something about it! I'm going to be become the most activities steam user!

Optimisation found it's doom!

😂😂😂😂😂😂

Successful release day