I don't know who needs to hear this, but EVERY FUCKING RETAILER needs to show the tariffs next to the price -- not just Amazon.
Walmart, Target (where I do not shop), ALL OF THEM. It's a fucking tax, why shouldn't we see it?
I want to know exactly how much trump's tariffs are jacking my prices up. DON'T YOU?
You made it, you own it
You always own your intellectual property, mailing list, and subscriber payments. With full editorial control and no gatekeepers, you can do the work you most believe in.
I refuse to be the kind of person who loses their mind over a delayed train or lets a spilled coffee set the tone for the whole day.
I want to be the one who stays composed, who sees the good even when things don’t go as planned. The kind of person who breathes through the little chaos and still finds beauty in how the day unfolds.
I want to be soft. I want to be steady.
Grow your publication on Substack
With recommendations, referrals, and a powerful growth network, Substack creators spend less time on marketing and more time on their craft.
You always own your intellectual property, mailing list, and subscriber payments. With full editorial control and no gatekeepers, you can do the work you most believe in.
When might city council wards be redrawn to reflect growth? How much did local drug take-back efforts collect this past weekend? And Jerome residents are invited to Station 210 to see it up close.
I’m going to say something that shouldn’t be controversial but will be. If you are a Christian, you can support border control and immigration being legal vs illegal. You CANNOT celebrate deportations and get off on the cruelty, and be a real Christ follower. Period
You always own your intellectual property, mailing list, and subscriber payments. With full editorial control and no gatekeepers, you can do the work you most believe in.
The idea of writing code *clean to refactor* really caught my attention. It is only a small shift of perspective compare to writing *clean* code, but it means looking ahead and anticipating instead of being obsessed with the current state of your problem.
I can relate to that in data science especially, where your understanding of a problem changes as you write code and thus have new results to analyze.
But I would be curious to ask what you recommend in practice to write code *clean to refacto…
I believe avoiding premature abstractions is the most important thing. Abstractions are hard to remove when you discover they are wrong — you will be tempted to build on top of them, thus creating more debt.
In my experience, even duplicating code is better than a bad abstraction.
To go back to the two points of your interpretation, I think they are correct, and most problems come from (1). More so, problems arise from the combination of A) not having a proper understanding, and B) not realizing this. So you have these "unknown unknowns" and you end up creating abstractions that do not fit. While instead if you *know* that you don't know, you will write more conservative code, expecting to refactor it later
"even duplicating code is better than a bad abstraction"
-> nice post on this idea https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction: "the sad truth is that the more complicated and incomprehensible the code, i.e. the deeper the investment in creating it, the more we feel pressure to retain it"
For the last point, we end up with the fact that communication between teams (here business and IT) is the key (once again)