tres
Joined 16 years ago
Joined 16 years ago
Not a great song, but one that expresses the zeitgeist in a pretty succinct way.
We thought that we were at the cusp of a new era... one where we could overcome the injustices of the past and author a future based on the best version of ourselves.
In the end, Gen X never even got a chance to start; we watched from the sidelines as geriatric Boomers clung (and still cling) to power -- leaving less and less of that (ever more naive) dream behind.
"Right here, right now,
there's no other place I'd rather be.
Right here, right now,
watching the world wake up from history."
The song hasn't aged well & has become a cloy reminder of that time and what we didn't become.
My graveyard of projects and dreams stretches out behind me and I feel saddened to know that these articles representing portions of my life never achieved what I had hoped for them.
However, I've come to view my work like a mandala or some representation of our mortality itself; our works and our lives are temporary.
We can make the most of the brief moment that we have – whether that be through work or through parenting or through base jumping – whatever that may be for each of us, or we can choose to do nothing with that moment, knowing that it's ephemeral and will be gone soon anyway.
I choose to try making each day's the best code I have ever written; I want it to be "beautiful" and maintainable in spite of knowing that it will be refactored, deleted or decommissioned at some point.
If you're a Jetbrains addict, there's this IDE extension which has worked well for me: https://github.com/KronicDeth/intellij-elixir
There's no need to design security in the system when you literally know everyone who is using it. And everyone who was using it had the same goals in mind.
So, I don't disagree with the sentiment -- people today would probably do it a little bit differently; however, I do disagree with the expression -- people designing these protocols weren't naive. They were trustful because they had to be.
In the early days of building something new, nothing works without trust; not the Internet... not Bitcoin... not a nascent venture... nothing.
Judgements of competence and honesty are subjective; we can all fail to distribute them fairly (especially when it comes to ourselves).
Rarely, when it comes to a history of an entire culture that spans hundreds of years and thousands of miles, can we find one perspective that describes a universal "truth."
All we have are shades of approximation.
That doesn't mean that there's no value in that approximation, it just means that we have to be a little patient with each other while each of our generalizations don't necessarily conform to the ineffable complexity of such a large group of people over such a large area over such a large timespan.
"Perfect is the enemy of good."
I'm sorry that it seems to be so problematic.
This piece seems interesting and illuminating regarding a specific aspect of a culture that we are thousands of years removed from. It's a pop-piece, meant to be approachable and to stir the curiosity of the reader.
I can't imagine how many different ways it probably gets things wrong... and I guess that in itself is interesting to think about... but because it's impure does it mean that it has no value?
Is anything with a hint of inaccuracy (according to our own perspective and understanding) deigned unworthy of inclusion and distribution?
Does one need to be perfect in order to be published?
The toga thing has been addressed by others as our cultural mores being projected on people with different values...
Otherwise, I found the article interesting and entertaining.
¯\_(ツ)_/¯
I believe it's the amps you need to worry about; "amps kill."
I believe it takes about 1 amp to kill a person.
This thing is outputting somewhere around 55 amps (if I remember right).
Not sure why good coverage wouldn't mitigate risk in a refactor...
My mantra whenever I'm working with AI is that I want it to know what "point b" looks like and be able to tell by itself whether it's gotten there...
If you have a working implementation, it sounds like you have a basis for automated tests to be written... once you have that (assuming that the tests are written to test the interface rather than the implementation), then it should be fairly direct to have an agent extract and decompose...