TOP 10 PROGRAMMING BEST PRACTICES

#1 Start numbering from 0.
#10 Sort elements in lexicographic order for readability.
    #2 Use consistent indentation.
#3 use Consistent Casing.
#4.000000000000001 Use floating-point arithmetic only where necessary.
#5 Not avoiding double negations is not smart.
#6 Not recommended is Yoda style.
#7 See rule #7.
#8 Avoid deadlocks.
#9 ISO-8859 is passé - Use UTF-8 if you ▯ Unicode.
#A Prefer base 10 for human-readable messages.
#10 See rule #7.
#10 Don't repeat yourself.

The project where I realized I wanted to go from chemist to pro dev.

I built a flow-chemistry spectrometer with monitoring backend in Haskell.

Spectroscopy is where you add a reagent to a glass tube, it changes color, and by measuring the exact color it tells you how much of something (for example, a toxin) is present in the sample.

I had to do that a lot on factory samples, writing down measurements using pen & paper.

I'm lazy so I decided to do the logical thing: Automate it. I bought a second hand spectrometer, stripped the casing, did a shitload of glassblowing and hooked up tubes to the production pipelines, so I could get samples, mixing them in the correct ratio with reagents in continuous flows using valves.

I ended up using 2 home-crafted arduino-like boards (etching PCBs is fun!).

One to calibrate the mixture against known samples and control solenoid valves to continuously cycle through various reagents and deionized flushing water, the other to record the measurements and send them to a server running a Haskell/Yesod API.

The server collected the information into InfluxDB (A time series database), displaying all data on a graphite dashboard.

Eventually I wrote Haskell plugins for most of the chemistry processes, from pH & temperature measurements to polymer property and pigment tests (they made a lot of printer ink).

Then I was fired because they didn't need chemists anymore, and the code "could be maintained by the intern" (poor guy)...

But I did find out that I loved functional programming, chemistry automation projects, and crafting my own electronics during that time.

You know what´s really retarded?

How HP decided to put the delete key next to the power button on their Elitebooks (and make the power button part of the top keyboard row)

All my code is hacked together and barely works and is nowhere near shameless. But I'm pretty proud of my hardware hacks. Like the sticker that holds the casing on my laptop together.

Refactoring code of somebody who left and:

- Plagued the code with TYPOS (milions of them but ok I can live with those... to a certain point)
- Used global variables by default.... of course even where they're not needed
- Used comments only in parts of code where... well they're not needed, important ones are of course left out
- Did not indent code. 3..2..1... Did not FUCKING indent code properly and when he did... did WRONG!
- Instead of indentation he used commented line with multiple ==== signes.... so far top is 60 consecutive lines with olny ==== again no apparent pattern here
- Did not follow a fucking standard in variable naming... no camle casing... there are varaibles assigned multiple times to "temp" variables without no reason just for the sake of wasting resources on the system I guess

This is just the beginning of the review but I already want to change job, die, scream, cry... not in any specific order.

I was blowing dusts from my PC opening it's casing. My parents came near to me and said "Will this gonna wipe all the viruses from this PC ?"

Wrote a cpp semester project where i had to develop school management system.
The code was spaghetti and horrible with frightening OOP implementation but it was beautifully written with comments and 🐫 Casing.
Submitted the program and examiner rejected it while saying that i had copied it from else where and i could never write a beauty code like that .

You dumb 💩! Don't you know other basis to reject a person's hard-work

Some years back (Window XP time)..
There used to be desktops mostly.

I was opening the CPU casing to clean the boards and my mother came near to me and saw lots of dusts inside. She realized something and told this : " You don't often clean these dusts and that's why your computer is getting more viruses."

I’m pretty terrible at soldiering and small electronics in general, but I’m kind of okay with how this turned out.

Back story:
That helmet is my sister-in-law’s, she drives a polaris slingshot. (It’s technically a motorcycle here in the US because it has three wheels.) and she hooked up some EL wire to her helmet and the larger black rectangle in the picture is what the battery pack looked like before. (It takes two AA batteries.) and doesn’t have anyway to recharge them natively.

I did some research and found a neat little charging board (TP4056) and got her a small single cell li-ion battery for it. Now it’s not only less than half the length of the original, but it has a rechargeable battery and a charging circuit built in. The battery is 500mAh and lasts about 65-70mins on a charge. Personally, I feel like that’s not a good enough battery life on a charge, but my sis-in-law says that her and her slingshot friends usually only run with the EL lights on for 30 minute stretches at time so they should be able to get two to three uses before needing a recharge. Which btw, only takes about 35-40 minutes from completely dead.

The box looks like shit cause I literally hacked away at the original casing with a pocket knife and then crammed all the pieces back in and hot-glued the casing together. But I took measurements of the final-ish design and will try to find a small electronics box that will be able to house everything internally. (L: 1-3/4” W: 1-1/4” H: 1-1/4”)

In the before time (late 90s) I worked for a company that worked for a company that worked for a company that provided software engineering services for NRC regulatory compliance. Fallout radius simulation, security access and checks, operational reporting, that sort of thing. Given that, I spent a lot of time around/at/in nuclear reactors.

One day, we're working on this system that uses RFID (before it was cool) and various physical sensors to do a few things, one of which is to determine if people exist at the intersection of hazardous particles, gasses, etc.

This also happens to be a system which, at that moment, is reporting hazardous conditions and people at the top of the outer containment shell. We know this is probably a red herring or faulty sensor because no one is present in the system vs the access logs and cameras, but we have to check anyways. A few building engineers climb the ladders up there and find that nothing is really visibly wrong and we have an all clear. They did not however know how to check the sensor.

Enter me, the only person from our firm on site that day. So in the next few minutes I am also in a monkey suit (bc protocol), climbing a 150 foot ladder that leads to another 150 foot ladder, all 110lbs of me + a 30lb diag "laptop" slung over my shoulder by a strap. At the top, I walk about a quarter of the way out, open the casing on the sensor module and find that someone had hooked up the line feed, but not the activity connection wire so it was sending a false signal. I open the diag laptop, plug it into the unit, write a simple firmware extension to intermediate the condition, flash, reload. I verify the error has cleared and an appropriate message was sent to the diagnostic system over the radio, run through an error test cycle, radio again, close it up. Once I returned to the ground, sweating my ass off, I also send a not at all passive aggressive email letting the boss know that the next shift will need to push the update to the other 600 air-gapped, unidirectional sensors around the facility.

Phones are getting bigger screens but also heavier. Why can't they just make a mobile phone that fits nicely on one hand and doesn't weigh like 1/4th of a kilo (phone+casing+screen protector).

!Dev / story

My phone starts dying gently but surely. Since last week I cannot use my jack input anymore, and thus can't listen to music in the car. I also compose music, and was eager to listen to my latest production (for reviewing purposes) in the car. In my frustrated search for a spare device with a jack, I found a pile of blank CDs instead. "Aw yiss, I can haz music in my car" I thought with a huge relieved grin.

I grabbed a CD, looked at my pc, and my grin faded instantly to an "oh" of disappointment: I deliberately did not install a CD drive in my computer.

Not losing hope, I grabbed my Mac and tried inserting my blank disk in the drive. "Clunk, clunk", the cd won't go in. "Ah silly me, I replaced that drive with a SSD". So I went looking for that spare cd drive.

After I found it, its SATA power interface was smaller than regular SATA devices, and any connectors I tried were too big. "Hmpf, ok, I'm desperate, let's remove that SSD in my Mac". So I went grabbing some screwdrivers, removed the cover lid underneath the computer, and removed two screws from the SSD casing, allowing me to lift the unit up, disconnect the cable, plug in the cd drive, flip the Mac carefully, turn it on... And burn my CDs, and finally I resetted everything back to normal, carefully removing the cd drive and closing the computer.

What one doesn't do in frustration...

all of them. countless wasted hours.

as fate decided to turn me from $random-dev-geek into "the guy that calls the shots in tech", one of my earliest decisions was to automate formatting.

everywhere, automated at CI.

gofmt was an inspiration for the industry.
js?/ts? use prettier
C++? use ClangFormat
etc.

always default settings.
enforced by pre-commit hooks and CI.

never a single argument about bracket style, I don't care if someone likes single or double quotes better.

"fucks given" counter is fixed at 0.
everybody prefers it (ok, sometimes after a while sometimes)

of course there is still some more conventions to do for us humans.
IMHO the most critical ones.

like naming or even casing (camel, snake, kebab, - which one works where), but taking out most of the "so what" decisions takes discussions to a much more resonable level.

I had a mid semester test and there was one question on how we should create class names. I was very tired, so the test started like around 9-ish. Instead of saying Camel Case method I said Camel Toe method.

Makes me wonder how did they come up with the name "camel casing" anyways?

Customer is not always right :(

I'm so used to camel casing variable names that when I wasn't concentrating properly just now I called a variable "outPut"

Hey guys i wanna build a Pi-like Cluster to try out kunernetes locally and I would like some parts advice for the boards, casing, cooling, and the rack itself.

so far I have a Cisco E1200 Router I would use for the cluster for SSHing and connecting to

The AMD song, to the tune of Sam Riegel's DnD Beyond jingle:

You got the perfect casing
Its drive bays and supplies
But you need something to run your stuff
Cause you're late for that deadline

You click open a web page
You've heard about Phoronix test suite
And now you see a red company rise
In a field of blue and green

It's AMD! (AMD)
Yeah! AMD Radeon!
Yeah! AMD! (AMD)
Yeah! AMD Radeon!

You've got your motherboard
You've got your processors
And you've got Socket AM4!

It's AMD (AMD)
AMD (AMD)
AMD Radeon

Do 9V Alkaline batterys explode when in 90 degrees?

Update- Battery casing is melting in room temp. When pulled out of the heater.

Spent 2 days installing different versions of nvidia-driver, nvidia-cuda-toolkit, cudnn.
Disassembled pc due to some ram memory problems and pc not starting after freeze.
Looks like sometimes plug out and plug in various components on your motherboard fix pc lol. Destroyed PC casing that collapsed due to me sitting on it.

All of this to just find out tensorflow error and all crashes are from graphics card overheating after keeping it for some time at 82 celsius.

Added time.sleep to python code and looks like it's working, keeping temperature below 65 celsius.

Still ~100 times faster than cpu training so I can live with that.

Here is a gem I found when looking at the previous offshore team's database.

So apparently they didn't know that SQL has an ALTER TABLE command to add new columns. So they created a brand new table, version 2, THEN migrated all the data over, every single time a new field was needed.

Then of course they had to update all their code that previously looked at the original table and the clients had to resync data onto the tablets as well.

Maybe they thought it was a good solution since they don't know what database versioning is (something they also manually implemented) or that ORMs exist.

**Sanitized the table names but kept the general structure, casing, etc

CREATE TABLE [dbo].[TVP_NameHere] AS TABLE(
[NameTime] [datetime] NULL,
[NameId] [int] NULL,
[somethingId] [int] NULL,
[fooId] [int] NULL,
[Time] [int] NULL
)

CREATE TABLE [dbo].[TVP_NameHereV002] AS TABLE(
[NewColumnHere] [int] NULL,
[NameTime] [datetime] NULL,
[NameId] [int] NULL,
[somethingId] [int] NULL,
[fooId] [int] NULL,
[Time] [int] NULL
)

So I bought this HP laptop about a year ago thinking HP was actually reliable. But oh boy was I wrong. The fucking screen cracked within the first 2 months, because of a small drop from a table, even while it was in my backpack. And the plastic casing is flimsy. It's only been a year, and it's already slowing down because of, what I'm almost positive is age. I've been careful not to do or download anything that might give it a virus. And this thing is supposed to last me another 2 years till college. And, it's fan is the most annoying thing ever. It'll run even if I'm not doing anything super demanding like browsing the internet with only a couple tabs. I'm not one of those people who usually have a ton of tabs open. What's worse is that it's the only machine I have to code with. The school chromebooks are complete shit, and I avoid them at all costs, my cs class has PC's to use but I can only use them during school hours.

Constantly getting static shocks from the metal casing of your laptop 😠

I hate when programming books have shit code examples.

Just came across these, in a single example app in a Go book:

- inconsistent casing of names

- ignoring go doc conventions about how comments should look like

- failing to provide comments beyond captain obvious level ones

- some essential functionality delegated to a "utils" file, and they should not be there (the whole file should not exist in such a small project. If you already dump your code into a "utils" here, what will you do in a large project?)

- arbitrary project structure. Why are some things dumped in package main, while others are separated out?

- why is db connection string hardcoded, yet the IP and port for the app to listen on is configurable from a json file?

- why does the data access code contain random functions that format dates for templates? If anything, these should really be in "utils".

- failing to use gofmt

These are just at a first glance. Seriously man, wft!

I wanted to check what topics could be useful from the book, but I guess this one is a stinker. It's just a shame that beginners will work through stuff like this and think this is the way it should be done.

Fuck you HP.
I needed to replace my laptops body but the top panel (ONLY THE FREAKIN CASING HOLDING THE KEYBOARD AND SOME OTHER STUFF) costs a whoopig 114 USD. Like C'mon =(
My laptop works perfectly fine but the body is brtlutally damaged.

Would love it if anyone from the subcontinent or rather anyone really would tell me where to find cheap Chinese laptop replacement parts.

Well this is in fact just me reminiscing, instead of telling anecdote.

My first PC was a pentium two, the cpu casing being those horizontal ones, and a big bulky monitor resting on top of it; all white. A white mouse, two white speakers (you know the ones). I was perhaps just about 6 years old, and I used it the first bunch of times to play Mortal Kombat, and Sega's Moto Racer 3, and watch animated disney movies but mostly mickey mouse on VCD. I guess my habits of gaming and binge watching started way too early.

So, got my first ssd. It's so freaking light 😳. I hope it's not just the outer casing without the internal PCB 🤪.

No, i wasn't living without an ssd. It's just to revive my 5 year old laptop 😅