Probably the most rage inducing data loss story...
When it comes to my cellphone I'm a data hoarder, I store each relevant meme, conversation, video, contact, nudes, etc. Had to replace my phone? Easy, change the SD.

I did this for about 4 years, had over 11GB of almost everything and anything in a 36GB SD, one afternoon my buddies and I went to a small tech convention and on our way to my car we got mugged by 5 armed men.

They took my brand new phone along with my wallet and all my cash, luckily I had GPS tracking enabled and we were able to pinpoint the exact location of my phone within 30min.

So far so good...

We called the cops and went with them, we found the car with illegal plates and weapons inside (knives, a bat, gun) so I tell the robbers were in there inside a closed cyber cafe and showed him the point on the map confirming this.

Cop: oh we can't do that we don't have an order...
Me: are you kidding me, here's the GPS, there's the car, there's the weapons, doesnt that count as at least probable cause or some shit?
Cop: we don't have that in this country, you can file a report and after 3 business days we can come here to inquire.
Me: (fucking lost it) do you fucking think they'll be here in 3 days?! I'll give you 500 bucks if you go bust their ass now.
Cop: (thinks about it) but what if they are armed? [4 patrols, 8 cops, 4 rifles and at least 6 guns plus vests] Maybe if you had contacts within the bureau we could have an order now...

(┛✧Д✧))┛彡┻━┻

I lost a lot that day, including respect to this fucked up system.

t(ಠ益ಠt) FUCK THE POLICE go eat a dick.

So recently I completed side gig from random freelancing site where I had to shadow troubleshoot performance problems over teams call with random Indian guy on his client's AWS account. Long story short you can autoscale new instances all you want but it's not gonna help if your FIFO sqs has only one message group ID. This architecture is running an online game, which is basically limited to processing ONE event at the same time for ALL players xD
What's even better, basing on naming convention I realized it's a company that I interviewed for like 4 months ago and they told me "we need someone with more experience". Well good luck, thanks for quick cash

Who books meetings on Friday afternoons?
Isn't that against the Geneva convention?

(Note: this is ***NOT*** advertising if you are questioning the validity of this post)

I know that Microsoft gets a bad word for many things (and rightfully so), but one good thing that they do is host a yearly general developer convention in Israel called BlueHat IL.

I've been trying to get invited in for 2 years now (they have to manually accept your application because so many people want to be there and they would run out of physical space if they accepted everyone), and yesterday I FINALLY GOT MY INVITATION!!

So, if you are also going - meet me there!

A LPT I read on Reddit which I really found effective, sharing with the community here:

Using following naming convention really helps to keep file system sorted

YYYY - MM - DD - Name

Example:
2022-12-31-Christmas trip to Amsterdam
2022-02-28-Honeymoon to Maldives
2021-09-15-Banged Christina

Your folders, will always be sorted in order making it easier for you to locate them.

Texas jokes time!

M16: Jams when dirty
AK-47: Works when dirty
Mosin-Nagant: Wasn’t clean since issuing in 1932

M16: You’d rather die than break your expensive rifle in melee
AK-47: Your rifle works good in melee
Mosin-Nagant: Your rifle is a spear that can shoot

M16: 40mm grenade launcher is heavy, but is accurate up to 200 meters
AK-47: If something goes wrong, you can throw a 40mm grenade into the window yourself
Mosin-Nagant: Throwing grenades into windows? Shoot through the wall, your cartridge penetrates one meter of brick

M16: You can use a suppressor, a small bullet doesn’t make much noise
AK-47: You can use a suppressor, but it’s better to spray and pray
Mosin-Nagant: You don’t need a suppressor — everyone will go deaf after the first shot anyway

M16: More complex than some aeroplanes
AK-47: Used by countries that have no money for aeroplanes
Mosin-Nagant: Was used to shoot down aeroplanes

A favourite drink of the user:
M16: Whiskey
AK-47: Vodka
Mosin-Nagant: brake fluid

M16: Makes a small hole, obeys the Geneva convention
AK-47: Makes a large hole, doesn’t obey the Geneva convention
Mosin-Nagant: One of the reasons for the creation of the Geneva convention

M16: Perfect for shooting squirrels
AK-47: Perfect for shooting enemies of the State
Mosin-Nagant: Perfect for shooting armoured personnel carriers

If not understanding code, read the documentation or debug the code. When trying to modify...
1. Follow proper indentation.
2. Don't make spelling mistakes and follow naming convention.
3. Don't try to write all the code in one line (based on line length set)
4. Simplify if else statements if possible.
5. If value of method call need to be used once, don't store it in a variable. Directly use where ever it is needed.
6. If there is duplicated code, put it in separate method and re-use it if possible.

I hate these Mondays. You start really motivated after a nice weekend of seeing lots of old friends, but instead of your own work, you have to pick up the mess a coworker left for you while fleeing into holiday and because that's not frustrating enough, you try to review code from that new senior developer and get confronted with the probably most awful commit history someone ever managed to create.

Of course he also needed handholding and multiple trys to stop breaking like every coding convention we have for branch management...

I am still a junior and I feel pretty disappointed when being confronted with people being so..confused with stuff like git even though they have like 10 years of experience.

While I was still studying, I somehow imagined this industry to be much more...sophisticated?

What to do as junior, if multiple seniors (4) aren't in sync with each other. Following different convention on same client's project. Even after 3 years they didn't able come up with seemless infrastrure. The code is getting ugly day by day. No review happens. Is that normal? As they are not in sync, we, juniors are frequently getting confused what to do. What could be done? I'm planning to leave the project somehow. Don't know what to do. 😑

After upgrading to kubelet 1.24 kubernetes won't even start. Complains about an unrecognized flag "--network-plugin=cni". And stackoverflow has nothing to offer to work around it.

God I hate backwards-incompatible software updates. Esp w/o vendor's scripts automatically porting old version configs to match the new configuration convention.

Now I have to learn all about something big, called dockershim.

Fuck! I so don't want to spend my whole day on this...

It's not very linuxish to push breaking updates w/o any bpo mechanism, esp for a software that's a part of the linux foundation :|

There was a murder at a mime convention.
People that were there know who did it, but nobody is talking.

A year ago I built my first todo, not from a tutorial, but using basic libraries and nw.js, and doing basic dom manipulations.

It had drag n drop, icons, and basic saving and loading. And I was satisfied.

Since then I've been working odd jobs.

And today I've decided to stretch out a bit, and build a basic airtable clone, because I think I can.
And also because I hate anything without an offline option.

First thing I realized was I wasn't about to duplicate all the features of a spreadsheet from scratch. I'd need a base to work from.

I spent about an hour looking.
Core features needed would be trivial serialization or saving/loading.

Proper event support for when a cell, row, or column changed, or was selected. Necessary for triggering validation and serialization/saving.

Custom column types.

Embedding html in cells.

Reorderable columns

Optional but nice to have:

Changeable column width and row height.

Drag and drop on rows and columns.

Right click menu support out of the box.

After that hour I had a few I wanted to test.

And started looking at frameworks to support the SPA aspects.

Both mithril and riot have minimal router support. But theres also a ton of other leightweight frameworks and libraries worthy of prototyping in, solid, marko, svelte, etc.
I didn't want to futz with lots of overhead, babeling/gulping/grunting/webpacking or any complex configuration-over-convention.

Didn't care for dom vs shadow dom. Its a prototype not a startup.

And I didn't care to do it the "right way". Learning curve here was antithesis to experimenting. I was trying to get away from plugin, configuration-over-convention, astronaut architecture, monolithic frameworks, the works.

Could I import the library without five dozen dependancies and learning four different tools before getting to hello world?
"But if you know IJK then its quick to get started!", except I don't, so it won't. I didn't want that.

Could I get cheap component-oriented designs?

Was I managing complex state embedded in a monolith that took over the entire layout and conventions of my code, like the world balanced on the back of a turtle?

Did it obscure the dom and state, and the standard way of doing things or *compliment* those?

As for validation, theres a number of vanilla libraries, one of which treats validation similar to unit testing, which seems kinda novel.

For presentation and backend I could do NW.JS, which would remove some of the complications, by putting everything in one script. Or if I wanted to make it a web backend, and avoid writing it in something that ran like a potato strapped to a nuclear rocket (visual studio), I could skip TS and go with python and quart, an async variation of flask.
This has the advantage that using something thats *not* JS, namely python, for interacting with a proper database, and would allow self-hosting or putting it online so people can share data and access in real time with others.

And because I'm horrible, and do things the wrong way for convenience, I could use tailwind.
Because it pisses people off.

How easy (or hard) would it be to recreate a basic functional clone of the core of airtable?

I don't know, but I have feeling I'm going to find out!

What's the correct way to do an iterator in a for loop?
Some teachers tells me that every iterator be named like line and row and other says i and j are the convention and you should name your iterator like that.

Damn, I hate Spring and most CoC frameworks. We’re using it from 2 years, I read most of the docs and it still gives issue for basic taks which takes hours to fix because I have to guess the exact convention which allows the program to process corner cases which aren’t explained in the docs. Yes, in the end the code is more elegant but it’s worth it when issues which could be solved in minutes by a trivial if/else statement takes hours (rigorously on pair programming™️ since being one of the few which actually read the docs I end up with lots of calls for help for Spring related issues by other teammates) and huge headaches to fix following the framework’s way?