Obviously, energy cost creates a barrier to entry, so reduction of cost reduces the barrier to entry... which adds more players... which increases demand.
355 karma · joined September 30, 2014
Obviously, energy cost creates a barrier to entry, so reduction of cost reduces the barrier to entry... which adds more players... which increases demand.
> In Scrum, Product Owners have sole authority over the Product Backlog; they control what to build and when to build it. Engineers are merely ticket-takers, implementing one instruction after another.
I think this immediately starts the article off in the wrong place. An Engineer that is a "ticket-taker" is relegating themselves to that role; they have more agency than that.
If you're able to cogently explain why something needs to done, and are additionally weighing product value while doing that, you will be heard. Stakeholders are not the problem here.
Before seeing this here, I went down a rabbit hole on why-anyone-cares about the OSI model, especially as a descriptor for their golang project. It seems to be just a classification that one person found useful, and people treat like an interesting thing.
Separately, we need more deprogrammers in the world.
It's difficult to believe that the decision should be made quickly. When making decisions about the trajectory of someone's life, they should be made with care. Having a system that removes snap judgements and bias is important, and I would say that even a quick-scan and re-ordering of documents is a form of bias.
Having worked in AdTech and Pulisher Analytics for about a decade, I know that orgs are measuring fake news viewability and content type + quality, so it'd just be nice to see a company making that digestible for people.
https://research.swtch.com/xz-timeline#jia_tan_becomes_maint...
would be useful info for Lasse Collins before taking the pressure campaign seriously.
https://www.researchgate.net/profile/Gilfranco-Alves/publica...
It's interesting using computational tools to finish something in spirit, that started long before their mainstreaming.
you're hired
Nvidia's CEO openly stated AI will replace coding: https://techwireasia.com/03/2024/nvidias-ceo-jensen-huang-ai...
The article starts with building a straw person, Stanley (who is weirdly homophobic for some reason?), and doesn't really articulate "here's how you code with intent" and "why coding with intent is important". Instead, it tries to tear apart people who don't use intent.
This is so that you can specify ranges of api versions that your program could be built with. For reference, here's where I took my understanding: https://semver.org/
It's something like "Net revenue" and "net user happiness" trump "code prettiness". Additionally, in the "maintainer > user" scenario, is it all maintainers? Is it one particular maintainer that has strong opinions (maybe which don't reflect what the business cares about)?
I'd suggest to replace the inequality mentality with an optimization problem, like: Find a version of the code that maximizes user happiness and minimizes maintenance cost.
If there are two solutions that give roughly the same values for the above, then accept either.
I think the problem is fundamentally that if you take a record, and split it across 2 tables, then there's no easy operation to merge them and guarantee distinctness.
Separately, even though there are some %-breakdowns in the article, I don't think the `DISTINCT` sort is so much of a problem in most cases. Usually the actually joining is the problem for any truly large dataset, so while I trust the diagrams shown, I think those %'s change dramatically based on the underlying data.
Google was playing 3D chess when they started developing Chrome, and when they started making moves to strip away things like user agent strings, they were really just making the final moves of a campaign set years before to create a walled garden of ads data.
In particular, the parts where you are adding buffers + prefaces ahead of the important content.
That said, non-violent communication is super important, so learning to retract from more direct, factual styles in exchange for a style that make people feel understood and respected as a colleague is important.
Tense situations usually evolve because both parties are adding slight amounts of intensity/unhappiness to the situation iteratively, and the only way to get them back to peaceful is by making commitment to making _the next interaction_ some amount less tense/hostile. Do that repeatedly and you'll get somewhere.
PS: Also Stoicism helps especially with these things... great, practical text on it: "The Practicing Stoic: A Philosophical User's Manual" by Farnsworth
In the abstract, I feel like editing a file on your phone vs. editing a file somewhere "in the cloud" isn't so different if the interface makes it indistinguishable, so I don't know if you get any real benefit to toting around your webserver...
but I like the notion of a homegrown, self-managed webserver that you keep in your pocket.
- Operation of the gun can be used as training data for AI
- Eventually we won't know when the gun becomes completely guided by AI
Best takeaways here:
- SQLite kills it. It appears untuned PostgreSQL is only 2 seconds (???) faster than untuned SQLite; always try to kickoff a project with SQLite
- PostgreSQL has a performance cliff when query responses leave memory. This is extra true when an index no longer fits in memory. worker_mem is critical for pushing back this performance cliff
Side note: Tuning postgres can be really painful, but it's also a really dope tried-and-true db.