I fried my laptop's lithium-ion battery by overheating it too much when gaming for 1.5 years now. Was only getting 20 minutes on a charge. Bought a replacement battery to install.

My laptop is full-body aluminum, and when removing the difficult-to-remove backplate, I sliced my thumb deeply on the razor-sharp internal edge of the backplate.

Hurt like hell. Took a while to get the bleeding to stop. I had to finish what I started, so I swore I'll be careful the rest of the time.

Yet somehow, my hand eventually slipped and I ended up slicing my OTHER thumb, on the exact same component! And the gash was even deeper and hurt even more! And took 3x as long to stop bleeding! I lost so much blood... 😫

Moral of the story: Be careful when dealing with full-body aluminum laptops. They're fucking evil and dangerous. Also, don't let your laptop reach temps above 82-85 degrees Celsius.

Thankfully, no tetanus from any of this. 😓

Really? No matter how hard you try, I will not switch to Edge. I want proof!

Microsoft Internet Explorer is my least favorite enterprise software. We are forced to use it. I hate being forced. This is like being asked to climb a mountain with a broken leg...not fun, painful, hopeless, threatening, discouraging, slow, and ugly, and infected...it is downright evil corporate bullshit.

<!--[if IE]>
<link rel="styleshit" type=trash/css" href="die-die-die-you-evil-bastard.css"/>
<![endif]-->

Just push it over the edge with a chrome sword stuck in its back. I will just sit here by the fire with my pet fox and watch the opera as I listen to vivaldi.

Google: hey website owner, use link rel preload for images loaded by CSS to reduce roundtrip delays. Chrome supports that, Safari also, and even Edge does.

Mozilla: we had some bug with preload back in FF 57 and our solution since has just been to disable preload per default. Done. Who would care about loading speed?

Also Mozilla: we have no idea why our market share has been plunging. Google is evil.

Crime can be prevented. War can be explained. Evil can be analyzed.

Pure chaos, however, is different. Somewhere out there, an inch away from the edge of the universe, lies what will destroy your mind should you try to grasp it.

For web devs here, do we really still need to support browsers of the evil (yeah I'm talking about MS browsers, Edge included) ?

I mean, building a css ui library here in 2017, without the benefits of custom properties, grid and so many other cool things, is so fucking frustrating.
A practical example : color theming with custom properties = Fuck Yeah / color theming without custom properties = so verbose and painfull, sucks.

The library is mostly for private usage at the moment so... I'm about to drop IE and Edge in the deepest shithole of the darkest cavern of my memory, and move on coding my lib with modern CSS, with almost no regret for the ghosts of the past who are still using these shitware today.

Should I ? Or should I... maintain compatibility as we traditionnally do ?
What's you guys opinion about this ? Can we finally kickban these browsers from our lives ?

I really really really hate Edge! What kind of web browser doesn't have a proper address box where a url is a url and not a search phrase directing you to fucking Google, the most evil search engine of them all.

Persisterising derived values. Often a necessary evil for optimisation or privacy while conflicting with concerns such as auditing.

Password hashing is the common example of a case considered necessary to cover security concerns.

Also often a mistake to store derived values. Some times it can be annoying. Sometimes it can be data loss. Derived values often require careful maintenance otherwise the actual comments in your database for a page is 10 but the stored value for the page record is 9. This becomes very important when dealing with money where eventual consistency might not be enough.

Annoying is when given a and b then c = a + b only b and c are stored so you often have to run things backwards.

Given any processing pipeline such as A -> B -> C with A being original and C final then you technically only need C. This applies to anything.

However, not all steps stay or deflate. Sum of values is an example of deflate. Mapping values is an example of stay. Combining all possible value pairs is inflate, IE, N * N and tends to represent the true termination point for a pipeline as to what can be persisted.

I've quite often seen people exclude original. Some amount of lossy can be alright if it's genuine noise and one way if serving some purpose.

If A is O(N) and C reduces to O(1) then it can seem to make sense to store only C until someone also wants B -> D as well. Technically speaking A is all you ever need to persist to cater to all dependencies.

I've seen every kind of mess with processing chains. People persisting the inflations while still being lossy. Giant chains linear chains where instead items should rely on a common ancestor. Things being applied to only be unapplied. Yes ABCBDBEBCF etc then truncating A happens.

Extreme care needs to be taken with data and future proofing. Excess data you can remove. Missing code can be added. Data however once its gone its gone and your bug is forever.

This doesn't seem to enter the minds of many developers who don't reconcile their execution or processing graphs with entry points, exist points, edge direction, size, persistence, etc.