1,483 karma · joined March 2, 2016
Recognising when you are in "defensive" mode in an argument, when you're just defending your pride instead of reason, is one of the most valued skill you can learn.
So I can get behind the statement that self-soothing, and being able to put your ego in the passenger seat is indeed something that can boost your "intelligence" (as in, capacity of acting on reasoning and logic).
At scale, destroying things has larger returns than the costs.
What we need to do is retrain everyone to use the more general term "Web API" and reclaim the term "rest" for architecture and design decision discussions.
This doesn't fix the problem but it does fix the environmental impact.
If you build something properly (ie you did not deliberately made a choice of taking a shortcut), and it ages badly I called it Tech rot.
But if something is done with plain bad code, it shouldn't be called tech debt. Something that outgrew its objective shouldn't be called tech debt. If something is a bug it shouldn't be called tech debt.
I found that writing has the same effect for me, that is why I use journaling for dealing with complex situations in life. It forces you to materialise what is in your head the same why that speech does, and I find it almost meditative as well.
Also I might have misread the protocol, since I'm no medical scientist, but wasn't the efficacy of the vaccine measured only in a 1 month timespan? Are we even sure the effects are long lasting?
I just don't want to get the hopes too high too soon. The crash after a positivity high can be quite bad. Reuters is even live streaming Wall Street because of this announcement!
The title is quite sensationalistic for such preliminary results. Especially when they have only been reviewed by an "outside panel of experts" [1] who sometimes have undisclosed conflict of interests.
[1] https://www.nytimes.com/2020/11/09/health/covid-vaccine-pfiz...
For example: I especially love the metaphor of technical debt. But we should consider the other aspects of debt - You only take on debt deliberately and so that you can invest the time / money on something that will yield a return on investment. Calling bad code "technical debt" breaks the metaphor for me. We probably should stop calling bad code "technical debt"
That's the case I had in mind when writing that quote.
On the other hand, changing the docker user to non root might introduce some failure scenarios (eg file ownership) which might lead to other problems like availability incidents.
Security should start with threat modelling, and taking a risk-based approach. You can spend hours fearing that someone might break out of the Docker virtual machine through a zero day, instead of using that time to fix much more likely and plausible threat scenarios. Pick your battles.
I now have a Onyx Boox Note that has inferior hardware. But at least I can use Google Drive and easily export documents.
I'm happy they have made a Chrome plugin because when I got my device, before returning it, I had a go at making exactly that: A Firefox extension that renders a simplified version and pushes it to ReMarkable as PDF https://github.com/sergioisidoro/push-to-remarkable
There is a cost function associated with time. For most people, there is a threshold after which further gains become insignificant per hour saved, so a Jumbo jet is not much better than a super sonic plane.
But the world has also changed since the Concorde, and maybe now there's a bigger market for people for whom getting something or someone across the Atlantic in a few hours is important: Let's say, for example, that a loved one is severely ill, and you need to get there fast to say your goodbyes.
Very much this. I tend to lean towards Flask for building simple APIs. I think it's easier and faster to start a project and get something done.
But I always end up missing the admin features and the far superior ORM, and always regret midway that I did not use Django instead.
Isn't this the most obvious reason? If you have an idea and the capabilities to develop it for your own gain, why would you do it so the shareholders of your old company can buy a new yacht, while you struggle to buy an apartment?
If this kind of attitude picks up, of labelling domestic protest groups as terrorists, together with things like these, there won't be much separating the USA from an oppressive state
Feels like we, as an industry, already had this conversation in infosec - abot security by obfuscation - which has some parallels here. The conclusion was that hiding things is generally a bad solution to the underlying problems.
We basically built these metrics with Prometheus and grafana because our review queue kept growing. Now we keep everyone accountable, and make these metrics part of our stand-up meetings.
Our PR queue is now smaller, and review time is shorter. We use these metrics not to point fingers, but to ensure people are not overcommitting, overworked, and that people know how many things they have on their table.
I'm quite glad something like this is now available off the shelf
HL7 and FHIR are a major step in interoperability for health, and they should not be taken for granted.
I've worked with integration projects with EHR (Electronic health record) Systems, and a lot of hospitals still have proprietary formats for exchanging data with limited documentation.
If you ever work on any health related system, consider starting from those standards!
But tech debt, at least for me, feels very different from the tasks that should be triaged. It's very uncommon that we allocate time to repay certain debt, so does it make sense to triage and/or backlog? That was mainly my point with previous comment.
My experience is more like doing some other task, coming across some tech debt, and repaying it on the spot if I'm not that constrained by time. For paying debt on the spot having a clearly flagged issue and proposed resolution would likely help me navigating and avoiding known caveats, and get a fix faster.
Even if I don't have time to fix the issue in the spot, knowing the reason why things are like they are might help with my morale and be less frustrated with coworkers.
But you mentioned a systematic way of tracking tech debt and the cost of each item per year. How is that different from a backlog after a while?
But yes, for finding existing and uncharted tech debt items, and deciding on their future, the discussion should happen somewhere else.
I wrote a bit about what was going on in my head here, if you're interested: https://isidoro.io/writing/tech-debt-broken-windows/
Feels like the open source is aimed only for the development phase, and no one else other than the authors will be able to execute large scale production