Osmose

I make websites and chiptunes!

  • he/him

AKAs:
Lapsed Neurotypical
JavaScript's Strongest Warrior
Fake Podcast Host
Thotleader
Vertically Integrated Boyfriend
Your Fave's Mutual
Certified 5x Severals by the RIAA
Inconsistently Medicated
The Source That Views Back
Carnally Known
The Alternative


Homepage
osmose.ceo/

And most of the replies were enthusiastic agreements about how it wasn't a real word and was really annoying

I don't really care about the word. I care about the quantification of knowledge. Pulling facts from some experience someone else had does not mean you had that experience. The lesson learned is more than just some facts.

You cannot replace someone who knows a lot about a topic or community with a sufficient amount of user studies or experiments. You do not pay me because of the facts I know—you pay me for how I interpret and act upon them.

Experience isn't fungible, but the word "learnings" tends to imply that it is and that you can get the full benefit of experience from reading the conclusions of someone else's experience.

This truth is a fundamental part of why treating people as resources is not only unethical, it is a cause of failure.


You must log in to comment.

in reply to @Osmose's post:

I’ve never heard this term before, but I do like this kind of perspective on what the work of software development means. I also like to think about how this active knowledge is communicated or instructed on others.

Many of my thoughts are affected by having some legacy CMS and CI/CD systems land on my shoulders in the last. The most crucial help came from people who knew the history behind a fact and could point me in the right the direction to act on it.

And tbh it sucks that my ability to cope and learn under pressure feeds capital after it created the pressure! But learning is so reified in software development that it feels normal and good!