You Made Me Wake My Dog Up From Laughter! :D

You made me wake my dog up from laughter! :D

programmers will complain about how C++ is too complicated or arcane or whatever and then will literally go and write in JavaScript

This is freaking amazing. And I think you are making good choices in simply cutting away what is not working so you can make your deadline.

I am still curious though.

Power banks are freaking temperamental little bitches ( There is NO standard for when they should give charge, other than the vague " When a phone is connected" ). How did the environmental sensor not like it?

And did the programmable RGB have a datasheet to explain the logic of how to address LEDs?

And would it be possible to adjust the addressable LEDs by powering them with a PWM signal? ( IE, is it powered by 5V? )

Servo skull integration is underway!

I have run a few tests and the core functionality seems to be working fine - so I can press the button and it'll take a picture with the camera embedded in the left eye socket, briefly illuminating an led that's in the right eye socket and playing a buzzer briefly.

The green led turns on when the program I wrote is running, and if it's connected to a network the orange led will also turn on(so I can tell whether it's accessible to get the pictures off of it)

So it should be all good for MCM London on Saturday at this rate, just need to check that the cranial casing for the left hand side won't affect the picture too much

Had to remove the environment sensor as it didn't like that it was being powered from a power bank - so no temperature alert when it gets too hot for me(It was going to light up the remed if the temperature got above 30°)

Also had to take off the programmable RGB array, as whoever wired that integrated circuit was clearly on a great many things when they designed it - Trying to just access specified lights was madness. The first led was accessed through (0,1) whilst the 2nd was (1,1) and the third (6,0). And having all of them on made it looks like the skull was about to self-destruct with how bright they are

That is a very good point. I absolutely agree!

(Nearly) Never use auto in C++!!!

So I used to be amongst the people who thought "Yeah ok, auto hides the type. But if the type is not really important to understand the code, and was really long and confusing then it is worth it"

Like this: std::vector<std::pair<std::string, Employee>> MyFunction(); To turn it into: auto MyFunction();

And I was wrong. Do NOT use auto to hide that monstrosity. You FIX it. auto hides that awful thing and dumps the problem on the next poor fucker who will use it. ( People writing and using metaprogramming libraries are especially prone to doing this, since their typenames can fill entire screens ).

YOU just looked at YOUR code. Found it confusing... And decided... to HIDE it??? What it is the next person who did NOT write this code going to do when they read this going to do???

No. I beg of you. Use typedef.

You can create aliases of anything and make your code easy to read. And this only "hides" the code as much as auto and you can get the types the alias points to by musing over it. So it is auto... but way better. Because it is a UNIQUE name. Which can DESCRIBE things.

Like, with the horror in the previous example. Let us have a typedef in the .hpp file where "MyFunction" is declared. Now it reads MUCH better:

std::vector<std::pair< Employee_ID, Employee>> MyFunction();

I actually understand what the pair is now! Key value pairs! And screw it. Let us typedef the pair too now that we understand it!

std::vector<Employee_KeyValuePair> MyFunction();

And fuck it. Once more! Typedef the vector too!

Employee_Roster MyFunction();

I will bet most of you reading this only realized what the hell that moster was when you got near the end. BECAUSE THE FIRST THING IS FREAKING UNREADABLE! Fix it. Make your code readable. If you feel the urge to use an auto to hide a typename, it is time to typedef that motherfucker!

I am average american man I work fifteen hours in hamburger mine to buy one rock and roll disk

OMG I LOVE IT!

What is the dumbest thing you have coded and gotten to work?

a discord bot in my friend group server where it would scold people if they swore XD

An example hehe

I am so happy for you! Congratulations! I hope it will be an awesome place to work!!!

Here is a good tip for whenever you join a new company, no matter which number of job it is for you

Write down things you wished to had when you started. List of Libraries to download, instructions, tutorials in how to do things, set up ID. Virtual machines...Whatever.

And then offer to your supervisor after some months that you spend a few work-hours making those ressources.

From then on, make it a task of every new hire to update this packet.

That way it comes easier and easier to be a newly hired person at this company.

This trick takes advantage of the fact that YOU are right now the best and most experienced in the company at "Being the newly hired person", and so are by far the most competent to do this.

First day at new job!

Monday 8th January 2024

OMG today was the best! The new job’s office (not in the picture background, I'm at the doctor's there...) has so many cool chill people in it, so far I wanna stay here forever!

Had induction meetings, and a tour around the office, everything was so cool! Another 2 people joined so I wasn’t entirely nervous thinking I’m the only one who would be confused on the whole onboarding process. Work’s in an old-like building with a Grunge aesthetic vibe going on, absolutely love it! And music plays in the background which is so much better than the old job which was in complete silence 🤐

I'm just super excited to start working on the project + the team seem, and are, super friendly and helpful! Thank God for a smooth process getting here, yay!

New Years Resolutions #3: Work hard and do well in new job!