What do you get distracted from?

Deadly = new name of deadline

I wonder how programmers make money. And found this answer

One creates Bugs and other fixes it.

Love this programming world 🤩🤩🤩🤩🤩🤩🤩🤩🤩

Before an interview prepare a list of questions for them, they expect it!
My list to give inspiration:

Describe your company culture? - if the response is buzzword heavy, avoid.

What’s the oldest technology still in use? - all companies have legacy systems but some are worse than others

Describe your agile process? - a few companies I’ve interviewed with said they are agile but it’s actually kanban

Are developers involved with customers?- if they trust you to talk to customers you can infer trust to do your job ( I’m sure others will disagree)

Describe your development environment?- do they have such a thing as dev, test and prod?

These are the only ones I can remember but should give others a bit of inspiration I hope 😄

Before you're hired:
1. A binary tree?
2. Currying?
3. Higher-order function?
4. How does event loop work?
5. What is prototype?
6. What is encapsulation?
7. Can you draw an algorithm?

After you're hired:
1. Hey, can you add auth token and login to our app?

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.

One of my biggest tech related peeves, someone shows a video as part of their presentation but doesn't use full screen or even worse leaves the cursor over the video.

So who else is on Mac and not updating Slack to retain the old good logo? LOL 😂

Just one more dependency...

From my experience you can't really avoid bad companies with 100% success ratio. You can pay attention to the surroundings during an interview, you can research the company online, but in the end whether the company is good or bad is a purely subjective feeling. I think the most important thing is to make sure you don't get too attached to the company either emotionally or legally, so you can just gtfo when you decide it's not right for you.

Are you using socat?

Any interesting use case you would like to share?

I am using it to create fake / proxy docker containers for network testing.

Backend vs Frontend

Well, you wanted to chat...

Age++;
I'm gonna flex and tell that I've got a new Switch. My family and friends are really the best.

Thanks to them I also got to know that thief that stole my original Switch is named Stephan.

So I also want to thank you, Stephan, you thieving fuck. I hope you'll have fun with my console. I know that the police won't do shit since you are living in different country, so you can feel safe.

I've lost most of my games along with the console, cause I'm an idiot, but if anyone want to add me to their friend list here's my code:

SW-4095-0455-2232

1) Glassdoor

2) Only work on open source projects so you can see what you're getting yourself into.

3) Avoid job postings that use the words "polygot" and "passion" in the same sentence.

4) Work for yourself. Build a product or service to make you money, and if it doesn't pay for itself sell it.

I'm actually starting to search for a new job and no clue about this so I'll just sit by and watch 😇

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.