Manager (via phone): You need to setup the CEO with access to the app IMMEDIATELY

Dev: Ok…What’s the occasion?

Manager: There is a big important meeting right now where we go over our achievements for the year and my plan was to have him log in and play around.

Dev: Likely would have been worth mentioning at this mornings standup.

Manager: Don’t be a smart ass. In fact, if you were actually smart you would have given him an account in the first place! So you’re just an ass then, what kind of idiot doesn’t give the CEO an account to an app like this?

Dev: Actually you specifically asked for him to be removed when I added him. “Unnecessary Optics” you said.

Manager: THAT’S BULLSHIT, I NEVER SAID THAT!!

Dev: It’s in our meeting minutes from 2 years ago.

Manager: STOP WRITING THE THINGS I SAY DOWN IT’S COMPLETELY UNNECESSARY.

Dev: I’ll make a note of that request

Manager: YOU ABSOL—ok looks like he’s waving me back in the room now the account must be working now bye. *click*.

Dev: Moron.

a small local social network i made around 2008 as a replacement for the original which the owner closed down.

i missed the people from there, so it motivated me to make a replacement in a week, while learning html+php+mysql+js.

it worked for about 3 years and i redid it from scratch 3 times as i gradually learned more.

it was cool to be basically a host of a community i've come to like in the years before, and it was basically the only project i felt, really felt, had meaning, a point. people were grateful that i made a replacement for the original closed-down site, and i was grateful that they were using it and that i could keep talking to all of them on it.

at the height of its popularity it had about 1500 registered accounts, 150 daily logged in ones, and about 30-40 very active ones.

it was also the place where i went to implement all the cool stuff i learned and came up with.

it had a pretty cool questionnaire creator (originally just a test of how deppressed users are, but then i thought "why not let people make their own tests/questionnaires?"), which tracked people's results over time and showed them on a cool interactive flash-based chart.

also a whole forum system made from scratch, wysiwyg article editor, later seamlessly integrated admin controls for those who had privileges, like, not a separate admin ui, but the admin buttons right on the site, later even a realtime chat persistent across page reloads where you could put special links which, on click, would highlight site elements/buttons, or even complete step-by-step path to them if it was more clicks. would highlight the first step, after clicking would then highlight the second one, and so on...

it was pretty cool stuff for 2008, and afaik it basically landed me my first two full-time jobs with almost no actual job interview, basically just "we looked at the site, interesting stuff, tell us how you did x and y and z on it, okay, hired"

back then i kinda felt i have a bright future ahead of me =D

old but funny ...

Part of an honest interview :

- What is your biggest weakness?
+ Triceps femoris muscles

- Why do you want this job?
+ Earning money to buy food so that I don't die of hunger.

- How do you handle pressure?
+ By shouting the word fuck

- What are your goals?
+ Have a cheek in bed every night.

- We will be in touch.
+ you never call, do you?

Fact :)

The 1st rule of Javascript is: You don't admit you program Javascript.

The 1st rule of Rust is: You tell everyone you program Rust and how it is better than basically any programming language that existed or will exist.

The 1st rule of C++ is: There are no rules because everyone was too busy debugging templates to think of any rules.

The 1st rule of Java is: You must have excessive numbers of classes and boilerplate. The more boilerplate the better.

The 1st rule of Haskell is: It is great to learn, but you will never see it again once you leave college.

sob

after scam

Started new job at startup and finished all the development environment setup started development it was going smooth for one week.all the created API were working fine on the next day morning without any changes API's were giving cors error.asked my senior what must be the problem he said bypass cors and figure out the problem after trying for 1hrs i couldn't figure out what was the problem but API's were back to normal without any changes. then after sometime same day in zoom call i asked what was the problem he said show me the error but I couldn't reproduced the same cors error he then lectured me for 1 hrs and after that he said that learn to solve by your own dont come with silly mistake like this to me.
I don't know what was the problem he even refused me show to what the problem was.

Saw this today in the exercise code of a deep learning lecture. These people are doing their PhDs in deep learning 😳

* the snippet has no side effects

I'm starting to rethink the 'Software Developer' title as 'Sanity Maintainer'...

Software Development is just convoluted.. and it often comes with stress; I hate stress.

Just very diplomatically told the VP of Engineering to kick rocks (fuck off) for calling me at nearly 9pm to talk about project planning for a thing that isn’t even in active development.

Asked point blank if we were dealing with a life or death thing. He said no. I replied “then we can talk about this tomorrow”.

He balks and tries to tell me how important it is.

I cut him off “I wasn’t asking you, I am telling you it’s a quarter to 9 and I’m at a bar. This call is over. We’ll talk tomorrow. Good NIGHT”. With as much aggression and pissed off emphasis as I could muster on the ending.

Stay tuned to find out if I still have a job after this.

The following paper combines recurrent neural nets for vision with methods from reinforcement learning research:

https://proceedings.neurips.cc/pape...

Apparently an agent learned to catch a ball 85% of the time, without being explicitly told to track the ball. The RL algorithm rewarded the agent *only* for successfully catching the ball. The system itself used this reward signal to set its *own* policy/goal, which was used to guide it toward the goal of tracking the ball itself--all on its own.

Behold, the very infancy of the paperclip maximizer problem.

😂🤣🤣🤣🤣🤣😅

I decided to go freelance/contracting. Headhunters keep pitching me permament roles (and I love watching them run out of pitch lines :D )

Headhunter: This job can't do your asking salary, but can offer career development.

Me: Already did that. was Engineer, then Architect, then CTO. I'm actually stepping back to be an Engineer.

Headhunter: Ok well, in this job you can do things start to finish, see them through to the end.

Me: I actually get bored after a while. Prefer change.

Headhunter: Well this place has a great culture and fun atmosphere!

Me: It's an insurance company mate...