204 karma · joined January 27, 2015
It also means that the article spends virtually zero time talking about things that may actually be risks of the practice, or potential solutions. We aren't getting rid of natural gas powerplants any time soon. We could do a better job of monitoring and cleaning up leaks of fracking chemicals and wastewater injection though, if we focused on that.
In naive sql land, people solve this with string concatenations. Its... fine, but there is a lot of complexity to getting it right.
In sqlalchemy you can do `q = session.query(Users)` followed by `if username: q = q.filter(Users.username == mystring)`. The library handles all the concatenation and type conversions and whatnot for you.
So far as I can tell- with this you literally just write both queries and call a different one? I don't see ANY way of doing code reuse. And in my toy example that may not seem like a big deal, but I remember lots of functions where I had tens of endpoints that each were making similar queries, with a number of optional arguments to each. With sqlalchemy, we can build a "active user filter" function, and reuse it everywhere. This seems to take away that option.
I would be surprised if the true value (if that were possible to calculate) weren't closer to 1/10th the valuation that investors bought in at.
Yes, turns out that there are a LOT of ways to measure this, and the people whose jobs it is to do so have chosen some, and even laid out the pros and cons of each of them. Yes, the definition of unemployment that you usually hear (U3) has things it doesn't count. But those choices were made intentionally because they thought it was more useful this way... not because they are too stupid to understand this, or because of a vast conspiracy.
They CAN all be top performers at their responsibility list...
Narrativ is moving search forward. Our AI-powered platform is transforming content with our award-winning SmartLink technology. We’re democratizing access to a $60bn pipeline while improving shopper utility.
https://hire.withgoogle.com/public/jobs/narrativcom/view/P_A...
When the day comes that the revenue from the fuel tax has dipped low enough that the money needs to be replaced, I am quite sure we can come up with 300 other ways to allocate the tax burden appropriately.
Even without those though, this is a good read, thanks for it!
Why? Each of those pushes you have one thing to check, and if it is messed up only one thing to revert. With a batched release you have multiple things to check, and are reverting other people's working stuff when you have to revert. Even worse, you have to choose between reverting slowly (but checking every feature) and possibly having to revert a second time because there was another bug you missed!
> Personally, I favor stability vs. easier troubleshooting. This works for some products and not others.
I don't understand. If you make the same number of changes with the same number of breakages, is packing them into a smaller window really more stable? Even worse the more time it takes you to fix those breakages, the less uptime you have... The opposite of stability.
> All of the environments I govern match production 1:1 (sans data sanitation) in every way possible. I feel pretty strongly about this, if you can't test your code without pushing it into production, you should not be automating anything
I agree with this! But... Then why are you advocating for staging to digress further from production waiting for a big release?
I usually put integration tests in the client repo but it doesn't matter. The key is that you put in a trigger so they get run by changes to any of the projects.
The actual solution to that problem, of course, is to use smaller generators?