OMG I LOVE IT!

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

What's your favourite fact?

Don't really have many favorite things.

But I will tell you the best one I can think of right now:

"Human eyeballs are all the exact same size. "

Now. In fact, they grow a little bit ra little while after birth. And "Exactly the same size" means "Within 1-2mm" but I think it counts.

Why do I know that fact? Because I make robots. And robots can get the distance to something on the camera IF they know the true size of an object next to the target.

And eyes are quite easy to spot with peogramming. So robots use all the human eyeballs to constantly calibrate their distance measurements.

Now THAT is a neat fact!

Fun fact. Markdown... is a markup language

If you do not know what markup is... you should look it up. It is basically HTML that works both encoded and as clear text. Meaning it is the perfect note taking "language". In reality it is "just" a convention for how to write super nice-looking notes that have been tested by millions of people to be the very best it can be.

No big deal.

Oh also it is free, you do not even need a special program to look at it. Your browser can do it perfectly.

Sharing knowledge is awesome! This inspired me to write... a small novel... which did not really fit as a reblog so I will post as its own thing :)

What’s your take? Should senior developers spend more time coding or coaching more junior peers?

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

When to add delta in GoDot?

So I am slowly eating my way though the tutorial for GoDot. I already have some experience with moving things in space and calculating inputs for individual objects.... That is essentially half of robotics software. So in every frame, a function called _process is called. this function takes a number called "delta", which is the amount of time passed since last frame ins seconds (Usually close to 1/30 or 1/60). You add delta to the calculation of certain variables. The first example usually found is position, which is done like so:

position += velocity * delta

To me that was all good and obvious. But I found a lot of posts of people being confused when to multiply delta and when not to. And apparently doing it in wrong places is a quite common bug in GoDot games. Here is to figure it out! Think in term of units

Velocity is distance/time Position is distance

So you cannot add velocity to position. They are 2 different units. How to fix this? Remove the time component.

Since time is distance is divided by time, we simply multiply time onto it. You know what have the unit of time?

delta is time

Meaning it is obvious why you need delta in the line! :D position += velocity * delta

Because distance += distance / time * time