As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.

I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.

These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.

Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.

All I want to say is:

No time was lost.

This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.

Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.

One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.

You don't notice the things you take back from your failures, they slip back sticking to you, undetected.

You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.

You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.

You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.

Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.

Please, for the love of code...

Start and fail as many projects as you can.

Let's quickly talk about idiots.

> A simpleton coworker of mine installed Ubuntu on his brand new ThinkPad with a touch screen.
> Asks me to show him the Linux games site I mentioned earlier.
> I see that he has no browser installed.
No Firefox, Chromium, Epiphany, etc.
> Now I know that he has a room temperature IQ and something moronic is going to happen.
Truth be said, I subliminally desired a terminal based browser.
> Then he fucking opens Wine and I shit you NOT! That thundercunt opens...
> Internet Explorer!
> I punched his screen.
> No longer a touch-screen laptop.

Probably the biggest one in my life.
TL:DR at the bottom

A client wanted to create an online retirement calculator, sounds easy enough , i said sure.

Few days later i get an email with an excel file saying the online version has to work exactly like this and they're on a tight deadline

Having a little experience with excel, i thought eh, what could possibly go wrong, if anything i can take off the calculations from the excel file

I WAS WRONG !!!
17 Sheets, Linking each other, Passing data to each sheet to make the calculation
( Sure they had lot of stuff to calculate, like age, gender, financial group etc etc )

First thing i said to my self was, WHAT THE FREAKING FUCK IS THIS ?, WHAT YEAR IS THIS ?

After messing with it for couple of hours just to get one calculation out of it, i gave up

Thought about making a mysql database with the cell data and making the calculations, but NOOOO.
Whoever made it decided to put each cell a excel calculation ( so even if i manage to get it into a database and recode all the calculations it would be wayyy pass the deadline )

Then i had an epiphany

"What if i could just parse the excel file and get the data ?"
Did a bit of research sure enough there's a php project
( But i think it was outdated and takes about 15-25 seconds to parse, and makes a copy of the original file )

But this seemed like the best option at the time.
So downloaded the library, finished the whole thing, wrote a cron job to delete temporary files, and added a loading spinner for that delay, so people know something is happening
( and had few days to spare )

Sent the demo link to client, they were very happy with it, cause it worked same as their cute little excel file and gave the same result,

It's been live on their website for almost a year now, lot of submissions, no complains
I was feeling bit guilty just after finishing it, cause i could've done better, but not anymore

Sorry for making it so long, to understand the whole thing, you need to know the full story

TL:DR - Replicated the functionality of a 17 sheet excel calculator in php hack-ishly.

I don’t even know the word epiphany

Goes to sleep.

Wakes up.

"OMFG WHY WAS I SO STUPID!?"

*has code epiphany*

Late night rant

You've been coding until 2 am. The moment you're about to get into bed (one leg already under the duvet) you have an epiphany about the code. Huge interior dilemma revolving around the "what to do now?" question.

I had a huge epiphany on Friday... not all developers enjoy coding.

Discovered when they brought down 2 of our environments, well told them what was wrong with the changes in their code that caused the environments to break, gave them links directly to the file in the gitlab repo that needed to be updated, and...

They fucking went home. The change would’ve taken all of about 30-45 seconds to update and they fucking left.

This person’s team lead come storming in pissed off because her manager is furious about 2 environments going down and preventing everyone else from being able to deploy their changes.

We provide the exact same details to the team lead about what needs to be changed, and advise that her team member took off....

30 mins later, her manager is storming up to us (devops/sre) livid as hell.

Explain the situation for a third time... manager is like, why can’t you guys fix it?

Look here you dense motherfuckers, we can fix the code. We can be the plumbers that clean up your shit. But what value do you gain as a developer if you don’t understand how the systems work and you keep pushing shit in?

Made the changes, fixed the environments, done right? Wrong.

The original developer made more changes not knowing what would happen and thoroughly fucked the environments again.

This dumb-fucking dumpster fire of a dude then sends us a slack message. “It’s down again, can you fix it?”

Our manager steps in and tells us to send him a link to the logs and have him fix it himself!

Thank goodness we have a badass manager.

Send logs, send repo file links (again), and send line numbers in the logs to try and help just a bit more. Dude goes almost the whole day without fixing it, environments are down, other devs are pissed, we throw this dude to the wolves. His manager starts to head over and was about to talk with my team lead when our manager steps out of his office and tells him the in’s and out’s of the situation and that our job isn’t to play log parser/error fixer for the developers. This dude that’s breaking the environments needs to be the one to fix the issue and his team lead should be aware of the problems and should have been able to correct his errors before it ever came to us.

The amount of hand-holding we do is ridiculous.

(Disclaimer, this one guy making some mistakes doesn’t sound too bad, but this is actually a common occurrence for like 40% of all of our developers)

We literally have interns still in college running circles around some of our full time devs. I know I’m not a developer, but for anyone that’s new-ish to developing, when you see shit like that please don’t lose hope. Those ass-hats got into programming purely for a paycheck, not because of passion.

Stick with it and your greatness will know no bounds 👍

As for you craptastic dipstick lickers, FUCK YOU!!! Go back to school and learn how to give a damn.

The moment you realize, you are not getting your own website's Google Analytics information because of your Ghostry and Ad block plus installed :|

It hurts 10 folds when you spend 8 hours in debugging and on SO before epiphany ://

Karma is a Bitch :|

So I had a thought this morning while brushing my teeth.....maybe I should change my devRant avatars clothes every day? That way it looks like a real person and stuffs......then it HIT me suddenly.....I'm a fucking loser.

- Back in October 2019 -

- Me: Hey, these two servers are having weird problems. Several services we use stop functioning every 7-10 days. I can temporarily fix them by taking them off the domain and putting them back on, but I don’t know why they’re happening or what further damage this workaround causes.
- Boss: Thats not good. Well. Keep doing the fix when it’s needed.
- Me: We should really reach out to someone at Microsoft through our support plan. I have no idea how to fix any of this and it’s making our Hyper-V environment very unstable.
- Boss: K. Let’s not worry about that now, let’s just keep working around it.

- In January 2020 -

- Me: Hey boss. More and more errors are generating from these servers. I’ve created a log of everything Ive found to hand off to a support agent. We really need to.
- Boss: Okay. Let’s talk to our internal team that uses Hyper-V and see what they did since they don’t have any problems.
- Me: Its not Hyper-V specific. It’s stemming from AD and authentication. It causes problems even without Hyper-V installed, so I don’t think it will help.
- Boss: K. Let’s just do what we can with what we got.

- Today, May 2020 -

- Me: Hey. The servers no longer work at all, and the workaround has no effect anymore. I’m completely stalled on my project now and have nothing to do.
- Boss: What?? What happened to them?
- Me: *Sends 17 page PDF file documenting all found issues, errors, warnings, and weird anomalies in both servers, as well as troubleshooting steps I’ve already performed*
- Boss: None of this makes any sense. I need you to start troubleshooting right away.
- Me: But... I can’t... *Sends screenshots of errors having no search results on the web, screenshots of Microsoft Support Techs on forums telling me we need to open tickets with Microsoft directly, other reasons why I’m completely blocked*
- Boss: Keep trying to figure it out. We need this resolved as soon as possible and we can’t let it happen again in the future.

Now I’m completely alone in our office, bitterly staring at the servers, trying to force an epiphany on how to fix these dumb boxes.

I was to optimise a SQL query (7 min to execute,yes) with around 20 joins (I did not write this). Checked for missing indexes,etc.. but nothing worked. Stared outside the window, and back to desk reordered the joins ,executed in 10 secs.

I've got a rant-type question:

Why would you EVER use Google Chrome?

There are a million browsers in the world, you could've used Firefox, Opera, Vivaldi, Brave, Bad Wolf, Qute, st, Epiphany etc, but you chose to uss Google Chrome.

What would be the reason you would ever choose Google Chrome over any of the million browsers, out of which many of them get the job done much better than Chrome? Okay, I get it why you might use IE or Edge, cause you might be too lazy to install any other browser or you just want the performance benefits you get with Edge which totally, most definatelly, a very big plus point for Edge.

*"Chrome has a balanced-bloat out of all browsers"*
But how tf does that matter? That doesn't even help performance wise anyways.

I can't get over the fact that I have to see/hear about 'Chrome hogging RAM' EVERYWHERE. Like, why do you even care about the god damn browser? Why is it a standard over the million other browsers that exist? Why can't the general public be educated that browsers have choices (just like phones) and you don't have to spit crap over people who don't use Chrome.

It just drives me crazy of how many people hate Chrome, and still it's a 'default' browser.

I would quote Vivaldi (the company/browser):
'A browser should adapt to you, not the other way around.'

(Disclaimer: Rant of a former Firefox, qute, st, Opera, OperaGX, Edge, and ofcourse, Chrome user. Currently in deep love with Vivaldi.)

I'm done ranting. Have a nice day!

(My first post here, if I did something wrong, let me know! I'll make sure I don't do it again!)

I have been working for my current employer about 3 years now. When I first got to work I was asked by another employee to work on an editor for certain types of files. We will call this employee Ed. Because his name is Ed.

Ed is a verifiable genius, and a genuinely great guy to work with. He is amazing with hardware and math. Ed has a need, or shall I say fetish. He wants an editor for some our proprietary files called "Settings files". They are just xml. Nothing special.

However, I have always had other priorities. We actually had a tense moment when I had to tell Ed my boss doesn't want me to work on the editor. I had started looking into working on the editor when my boss said stop working on this file. So since then it had become a running joke between Ed and myself. Well, I think it is funny, Ed smiles, but I know he wants this editor bad. Our boss even suggested at one time that Ed write this editor. He looked into it, but "other priorities" trumped this effort.

Okay, so now it has been 3 years and we still don't have this editor. Then I had an epiphany. Since Ed wants this editor I found an idea for the name of this program. "Settings Editor" is just too mundane. I now think it should be called: "Mr. Edit". I also found that the library we use for most of our development has text to speech built in. So when the program starts I can have it say: "Hello, I am Mr. Edit, the talking Settings Editor". I have never wanted to write this program so badly before. Muahahahahaha!

Why can we all relate to almost every rant for wk24?

Devs could rule the world! Why do we have to endure all of the same crap from India to the UK?

(The recurring meetings and the 'Dynamic Requisits', as I call it, are what bugs me the most!)

!rant

Coworker: I've been working on this computer for an entire day now and it's still having issues

Boss: Well, we can give the client an option to get another SSD and clone to it before reinstalling the OS.

Coworker: But he doens't have an SSD...

Boss: Yes he does

Coworker: *opens computer* let's see, two 1TB hard drives... but no SSD... Oh, there it is. It's hidden. But it's booting too slow to be....

*epiphany*

Coworker: Oh my god. I've been telling the computer to boot to the wrong hard drive. That explains everything!

The more I play, the more I realise the similarities between coding and Dark Souls.

Working on an Android app for a client who has a dev team that is developing a web app in with ember js / rails. These folks are "in charge" of the endpoints our app needs to function. Now as a native developer, I'm not a hater of a web apps way of doing things but with this particular app their dev teams seems to think that all programming languages can parse json as dynamically as javascript...

Exhibit A:

- Sample Endpoint Documentation
* GetImportantInfo
* Params: $id // id of info to get details of
* Endpoint: get-info/$id
* Method: GET
* Entity Return {SampleInfoModel}

- Example API calls in desktop REST client
* get-info/1
- response
{
"a" : 0,
"b" : false,
"c" : null
}
* get-info/2
- response
{
"a" : [null, "random date stamp"],
"b" : 3.14,
"c" : {
"z" : false,
"y" : 0.5
}
}
* get-info/3
- response
{
"a" : "false" // yes as a string
"b" : "yellow"
"c" : 1.75
}

Look, I get that js and ruby have dynamic types and a string can become a float can become a Boolean can become a cat can become an anvil. But that mess is very difficult to parse and make sense of in a stack that relies on static types.

After writing a million switch statements with cases like "is Float" or "is String" from kotlin's Any type // alias for java.Object, I throw my hands in the air and tell my boss we need to get on the phone with these folks. He agrees and we schedules a day that their main developer can come to our shop to "show us the ropes".

So the day comes and this guy shows up with his mac book pro and skinny jeans. We begin showing him the different data types coming back and explain how its bad for performance and can lead to bugs in the future if the model structure changes between different call params. He matter of factually has an epiphany and exclaims "OHHHHHH! I got you covered dawg!" and begins click clacking on his laptop to make sense of it all. We decide not to disturb him any more so he can keep working.

3 hours goes by...

He burst out of our conference room shouting "I am the greatest coder in the world! There's no problem I can't solve! Test it now!"

Weary, we begin testing the endpoints in our REST clients....

His magic fix, every single response is a quoted string of json:

example:
- old response
{
"foo" : "bar"
}
- new "improved" response
"{ \"foo\" : \"bar\" }"

smh....

Typical development cycle:

Spend hours trying to think of a solution to a problem.

Get epiphany and implement possible solution.

Be afraid to compile it in case of bugs or errors

My biggest dev epiphany was also my dumbest one. We were working on a payment system for a roadside rescue company where an employee would register payments "in the field".

The challenge was automating input with typeahead and autocompletes in order to lessen the workload as manual input had to be an absolute minimum; this will be used by truck drivers/mechanics as they are trying to hurry to the next customer who has been waiting for 3 hours longer than we said we'd take.

We managed to make the invoice path first (customer has not paid, employee logs personalia needed for billing), but when it came to "paid on site" we almost upended the entire system trying to find a way to fetch user personalia outside of the invoice path.

Neither of us realized it during the days we were banging our heads against it. Realizing we don't need to make an invoice for a job that has been paid for was equal parts relief and utter embarrassment.

Probably my greatest lesson in how important it is to pull my head out of the code once in a while, and to ask myself what I'm trying to do and why.

The day I read The Simulation Argument, by Nick Bostrom, a thought popped into my mind: "if we are made of code, maybe there are ways to hack life as you would hack some random program", I started thinking privilege escalation over the simulation, buffer overflow, picking signals as if I was eavesdropping... it was an epiphany and also fun

Epiphany.....

After crash and burns all through FB, Twitter and Instagram, I've got to admit, the only place a dev can actually get any likes is devRant!

If you need workarounds and tricks to make your computer obey you, your operating system is trash. MacOS, Windows, I’m looking at you. This is indisputable.

Instead of defending that crap, just admit it. You did nothing wrong. You was forced to use it, because I understand that not every piece of software can run on Linux. Perhaps you earn money using Photoshop or any other Adobe software. There’s nothing wrong with it. You don’t become a baby-eating trash supporter billyboy if you’re just using an OS.

Perhaps you like macOS UI better than KDE or Epiphany. There’s nothing wrong with it either.

But please don’t defend trash just because you use it for one reason or another. Admit it to yourself and say “yes, the OS I use is a piece of crap that doesn’t respect users, but right now I’m forced to use it because of the software I make a living with”. This is the only non-traumatic way to start defending your rights.

Peace

i had an epiphany today, in a discussion with the software architect of our new project.

i'm having the epic job to design & implement a prototype for a C++ library in a new software project and collected some inspiration in our "old" software, where i'm maintaining the module that fulfills the same functionality (i thought). i've been maintaining this module for around a year now. i analyzed the different features and stuff to consider and created a partial model of the new library.

when i showed it to the architect today, he was like "oh my god, no no no, you don't need all this functionality, this shall not be part of the new library!"

this was the moment when i realized how deeply fucked up the code base of the old module is.

imagine it like this:
you want to automate the process of making yourself a good ol' cup of coffee.
the reasonable thing would be to have

- a smart water boiler where you set parameters water temperature and amount of water to be fetched from the water supply
- a smart coffee bean grinder where you can set type of beans, amount of beans and grinding fineness
- a component where water and ground coffee are joined to brew the coffee, where parameters like duration, pressure etc. are set
- a milk tank where amount of milk, desired temperature and duration / speed of foaming can be set
- a sugar dispenser where amount of applied sugar can be set
- optionally, additional modules with spices, syrup, ice cubes, whatever for your very personal coffee experience

on requesting a coffee, you would then configure and orchestrate all components to your wishes to make you a fine cup of coffee. you can also add routines like "makeCappucchino()", "makeEspresso()", or whatever.

our software is not like this.
it is like this:
- a smart water boiler consisting of submodules that know how to cook water for e.g. "cappucchino with sugar" or for "espresso without sugar, but with milk and ice cubes"
- 5 smart bean grinders that know how to grind beans for e.g. cappucchino, espresso, latte macchiato and for 73ml of water preheated to 82°C
- a very smart sugar dispenser that knows how to add sugar to 95, 98 and 100°C coffee and to coffee made of BOTH coffee arabica AND coffee robusta beans.

etc. etc., i think you're getting the gist.

when i realized this, it was like, right in front of my eyes, this terrible pattern emerged like a foul, corrupted caleidoscope of chaos, through the whole code base of this module.
i've already known how rotten from the core this code base is, but today i've actually identified a really bad pattern that i hadn't realized before. the whole architecture is so bloated that it is hard to have an overview of the whole thing. and it would require a LOT of refactoring to repair this pattern.
but i guess it would also be infinitely satisfying because i could probably reduce the code base for 30% or something...

but unfortunately, this is never going to happen, because screw refactoring.

it's a great feeling to start this new library from scratch, tho...

I was trying to make a circular buffer in C++. I was also trying to expose iterators for using the buffer with STL algorithms. I kept trying to think about how to add the functions needed to manipulate the existing internal iterators to not exceed the bounds of the buffer. Then I realized I was "too close" to the problem. There was no way I could properly control the internal iterators of the storage vector I was using. Not without giving too much power to the user of my library. So I abstracted the iterators up one level. Hid all the details of the internal iterator and made a new iterator.

The solution of abstracting the iterator was not the epiphany. The epiphany was if you are struggling with how to solve a particular problem. You keep running into problems with how to represent something, there is too much power available at a particular representation, or the object you are trying to make work just don't fit. This is when you should consider abstracting a level up. Take a higher look at the problem and simplify the interface.

Abstraction could be a number of things. Divide and conquer, hiding details, specializing an object, etc. Whatever tool is needed to make the problem more consumable to your brain.

I am now going to attempt the problem solving ritual.
Requirements:
-have a problem or piece of unoptimized code and you don't know how tk fix/improve it
-be able to sleep/take a nap

Now before I fall asleep the ritual should provide me with an epiphany to solve my problem

Plan b:
I have a class ninja (model), with an observablecollection<property> properties and an observablecollection<gearslot> gearslots;
,a class gear with an observablecollection<property> properties and an Category category:
And a class gearslot with a Gear gear and a Category category;
Via entity framework this results in several property entries per ninja
And several property entries per gear item

All good so far.

I now actually want the ninja property values, to be the sum of the gear property values

So a ninja has int, agi and str of 0.
Gear has 0 or more stats.
If the ninja has two pieces of gear on with agi +1, then the ninja agi should be 2

If possible i would like the logic in the model.
Else i have to put it in the viewmodel.
That i can figure out, its just so inelegant....

very interesting how uni stressed me tf out but is still better than school has been.
I'm taking a class which has a theoretical and practical part, and there is a guy leading the practical lesson. and after struggling to find motivation for studying, this class somehow probably gives me my hopes back... even though I'm way less capable than the rest in what we're doing, I still can follow everything, which is very suprising to me because I'm always behind and the class has some recommended classes I should've taken before (but I failed some or didn't take them at all)... I still can follow the class somehow?

so... school taught me to not ask question because even if they say there are no dumb questions... the possibility still existed that I could ask a dumb question (shoutout to my math teacher in 3rd class). so... I stopped and when I didn't understand something I gave up.

now... this class makes me feel differently, I can ask questions and the guy I've talked about talks to me normally, talks to me as human beings should talk with each other and doesn't judge me for making a mistake, because... mistakes are human and when I allow myself to ask questions I can learn from it.

this is really a weird epiphany I had this week

and I also don't know if anything of this makes sense

I feel like there's an over saturation of dev sites talking about "tutorial this" and "best practice that". Would be refreshing to have developers just talk about their grind and not so much their showing off of what they just learned from Stack.....oh wait a minute!! Must be how this devRant came to be! Hmmm....fuck me, epiphany. Who knew?

Epiphany!!
01. You realized you are in matrix
00. You get only Pokemon to follow not the white rabbit (just kidding)
10. You realized you are not Morpehus
11. You realized you are also not Agent
100. You realized you are no where near Trinity or Oracle
101. You realized you are not even the Architect
110. You think you are Neo!!
111. You ask the right question : Who Am I ? (Not which pills to choose)
1000. Who you are ??? :
You are some one who is walking pass the Blonde Woman in Red without even giving a look at her. (May be too busy in our own world to realize the world around can be as beautiful as the code we write)

Do some of you somehow internalize the rants of people here and wonder if your workmates feel the same?

Or have you encountered someone rant about a coworker but that’s also something you do/did and now you wonder if your workmates think the same about you?

A few weeks ago a friend was teaching me about 16bit numbers because we were making one in C# with a function, but he said we need two numbers for the function to work.(so as an example were gonna use 0, 2)

Now I didn’t understand how two numbers were supposed to make one. And my friend could not explain it to me. So I researched the topic all day and the epiphany happened I realized I was looking at it all wrong. I shouldn’t be looking at it as 2 decimal numbers but 2 binary values or two binary arrays forming one byte array with a length of 16.

Epiphany..?
My first was in the toilet, I had to clean up fast and go to my laptop to catch up the idea, when it worked I realized I will love this field.

After few years, with this stress and anxiety. I am slowly having my next big epiphany that this is not my job.

So I had an epiphany. I have always thought of linux as a big ugly slow monstrosity. It occurred to me the only time I had used Linux was on rPis and similar devices. Then I threw vanilla Ubuntu onto a flash drive and booted my workstation to it.

My next point what is the most seamless dual boot solution. 😁

Edit - typos

I would have wanted to bring up SICP again, with the great big warning about the evil assignment operator and state and all the troubles that ensue (just think: concurrency).
But in a way, nothing has really come up from this or my attempts to dig deeper into "everything is a file/object" (Unix, smalltalk), neither from formal languages or the Curry-Howard correspondence. - Maybe there's just nothing, no firm bottom ground to discover. Like the physicists going for their world formula, but instead of a grand, beautiful symmetry that explains everything, we face a shattered world of (incompatible) theories, that is ever so more complex and chaotic through our theories applied to it. There may not be a Platonic ideal world of ideas, but rather partial constructs explaining some particular perceptions.

Similarly the one perfect programming language to rule them all, the perfect abstraction, pattern is probably just another prepubertal fantasy to be sunk.

So maybe instead of seeking the perfect epiphany, we should go for something quite different: the nagging, brooding uneasiness that something is wrong there, that there's something to be fixed... that even negative feeling would propel us to search further, not to stay in whatever is touted as the real thing.

Such irritations I found with Pieter Hintjens' writings. For example when he actively engaged in conspiracy theories. And I'm still not sure, if he just went off the cliff or he's even right alluding that these theories are an act of sanity, a self-defence against the hidden evil mights. I just don't know. Anything.

I think I may have just had a bit of an epiphany...

Algorithms and Data Structures are sort of like libraries and frameworks.

JS is probably the easiest example since npm has a lot of libraries.

For most cases, underscore.each and lodash.each $.each achieve pretty much the same thing except one maybe better in certain cases.

And data structures are sort of like Angular, React, Electron, ReactNative. Each has its own purpose or style and are good for solving certain types of problems?

So day-to-day you don't really care what Sort() algo you use.. unless you really need to perfoarmance tune it for a specific case.

And data structures, depending on the type of problem you have, one is easier to work/think about the problem in although not examply... Usually have to use a few of them at once.

How is this going to help me in interviews... I'm not sure... other than reconfirming that knowing specific implementations of Sort and Trees is usually BS... most of the time just need to know you should Sort or use a Tree...

Product, not project!

for some reason twitter showed as the first trend the word epiphany and the first thing i thought about was the web browser.

Was pretty good and light but missed a lot of things.

Is there a web browser for Linux that supports hw accelerated video decode?
(Intel graphics)

There are so many bug reports for this, but all seem to be "won't fix"/ api is unstable or some other problem

I want to watch youtube without it destroying my battery.

(I know I can load the stream into a video player like VLC and watch it there, but that is not very practical...)

since my favourite phone automation app llama is no more i discovered automate. you build your 'scripts' with functional blocks. it's quite fun but debugging is messy.

mildly interesting: implementing a guided setup instead of defining the values directly leaves me with 77% setup and ui vs 23% actual task.