Just managed to setup a tiny/simple privacy-friendly analytics system.

You basically call an api from your backend with the api key and all the headers you received from the browser (php and Apache or nginx in my case) and the analytics api gets useful stuff out of that data without sacrificing privacy.

I get a little bit more insight into my websites usage and the client isn't sacrificing identifiable information!

I've been wanting to make this fucker for fucking months.

"Leave this fucking company, now."

>you love Google
>you're writing a CV
>you have big ego
>your CV looks like that one
>you're probably me

finally reddit changed its UI...😍😍😀

Opening Google Chrome
In the omnibox(address bar) typing www.google.com
Waits for the page to load.
Enters the search query.

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.

Dev: Microsoft is shit

VS Code: (ಥ⌣ಥ)

Dev: Oh not you dear! You're not like the other guys

VS Code: (｡◕‿◕｡)

I'm fucking tired of this so called lead developer, lead developer my ass:

- He takes two days to complete a simple task and he dares to ask me why I extended the deadline of this freaking complex feature I need to build.

- He does a half-assed job when completes a task, no validation of data, no well informative message when exceptions are th thrown ...

- He assigns me his tasks although I already have tons and we need to release soon.

- I take care of developing and maintaining 60% of the APIs and I implemented the most complex of features and he dares to always say that my code can be optimized in a vague way, never mentioning what exactly is he talking about, and never telling me beforehand, he always does it during team meetings where another thing is being discussed.

- He presents the app to the whole company and at the end doesn't give credit where it's due, no " thank you for being part of this or helping build this" even if I built most of that shit, instead he says he's disappointed in me ... WTF! What did you fucking do to build this to be disappointed in me? I'm the fucking disappointed one here !!

- He fucking keeps preaching practices that he doesn't follow or he finds workarounds to skip them while the rest of the team follows them.

- He's like "I'm only taking care of this task to help you out?!" .... wtf! I have nothing to do with that fucking task, how are you helping me! You just keep fucking lazing around when we need to be finishing features asap.

Thank God I don't expect anything from you, I get enough credit from my boss who expresses how impressed he's with my job.

You ever sit down to start working on a project, get all your imports and variables set up, and then just completely lose all motivation to even press a key?

Javascript is McDonald's.

1) everyone says they hate it....but they just keep going back.

2) very few people admit they keep gong back...

3) When McDonald's started doing salads, dressing nice, and delivering to tables it seemed a little much, you're a burger place. A few years later I'm writing my app in react JS, serving up eJS templates with my NodeJS server, running off a NOSQL JSon database, and munching down a Greek salad from McD's.

4) you start your burger (project) with high hopes. As you eat though....you start to regret it, but oh well, you're halfway in. By the end, never again, last time. A little while later, npm asks you if you'd like fries with that.

Feel free to disagree or add more!

I don't understand why people like an app but give it the lowest rating because they want more

admin
admin

Every computer programmer. :)

*Builds a web component for a client website*

CLIENT: I don't like it, can I have it a tiny bit over to the right more

ME: Taps the arrow key a few times making it look like I'm doing something.(Which actually does nothing)

Client: 👌Perfect

😂😂😂 Wut 😂😂😂

Management: "We have a Team Building session next week"
Colleague A: "Paintballing"
Colleague B: "Go-Karting"
On the day: "Welcome. Today we will be playing an IT Helpdesk Role Playing Game"

Kill me.

Three years into studying software engineering and three quarters of my class have no idea what git is.

But by gosh, can we code the shit out of a tic tac toe game.

1. Doesnt want to pay for server
2. Doesnt want to pay for disk
3. Doesnt want to pay at all
3. Wants the app in 1 week

A client wanted "a video on a server".

I took a server, put it on the ground, stood on it carefully and took 'a video on a server' 😊

I was so tempted to just send it 😆

Fire all incompetent teachers and update all the reading materials