Impacted by phones removal of the pain of being in a queue sure. Due to phones seems to ignore all the comments that this "came out of nowhere" and wasn't seen before "2020".
It seems most likely that with pubs not so active over the pandemic, then operating with more socially distanced rules, new pub users just never learnt the "only used in pubs queueing system".
Which is a weird blindspot for the article, where they reference a normal queue as something from "border control", rather than then thing you do everywhere but the pub. Without the introduction to the system they just use the system they use everywhere else. And don't worry it takes longer because it's a convenient time to check your phone.
>if the goal is to build up your own strength
I think you missed this line. If the goal is just to move weights or lift the most - forklift away. If you want to learn to use a forklift, drive on and best of luck. But if you're trying to get stronger the forklift will not help that goal.
Like many educational tests the outcome is not the point - doing the work to get there is. If you're asked to code fizz buzz it's not because the teacher needs you to solve fizz buzz for them, it's because you will learn things while you make it. Ai, copying stack overflow, using someone's code from last year, it all solves the problem while missing the purpose of the exercise. You're not learning - and presumably that is your goal.
I feel like the take it back approach, just ends with the retailer/manufacturer throwing it away anyway.
Looking at this device it feels like it shouldn't be hard to have a reusable base with battery and electronics, and a disposable capsule that attaches on top but is replaceable.
Who bears the cost of that improvement? Either the manufacturer, the retailer, or the customer. The problem is that the waste created by vapes is a negative externality so there's no incentive to improve their design. Until the government starts requiring safe disposal of these things, we won't see a change. Think about what people used to do with old car oil before new environment protection regulations.
Tailwind (like most things) is way more complex than it first appears.
Sure the main thing was originally 'just' mapping `.p-4` to `padding: 1rem`. But it's also about grepping the code to see if `p-4` is used so it only builds needed classes. It also needs to work with things like their responsive and state classes so `md:p-4` or `hover:p-4` add the padding only on medium or larger screens, or when hovered etc.
All of which increased to support more and more css features and arbitrary values so `not-supports-[display:grid]:p-[5px]` generates the required code to check if grid is supported and add 5px padding or whatever other values you put in the [].
You can question if that's really a sensible idea, but it is undeniably a pretty complex challenge. Not sure it compares to blender, I imagine that has a lot more maths involved - put probably less edge cases and weird displays odd in X browser bugs.
It's the difference between one-off revenue and recurring revenue. If you're making new components, making new changes for the new version, adding new css and browser support it's hard to keep going with only income from new customers.
I found it pretty surprising. It would not have surprised me at all if we made fake plastic feathers and burned or buried even more real ones because it works out fractionally 'cheaper' to make new then collect and wash/treat the old.
Honestly, I’d still be surprised to learn feathers in America are produced from American poultry. Far more likely the local ones get burned and everything for sale is shipped across the ocean because cheaper.
This is what I don't get with a lot of the AI based saas projects - what is your value add? If you can build it with AI then (in theory) your customer can also build it with ai, so why do they need you? In the SaaS world you don't because the cost of development and maintenance just doesn't scale well, but if you're 99% a wrapper around an AI, your 'business' feels easily replicable to me.
But that does leave a weird gap where SaaSes that took a lot of time to make but can now be handled by an Ai won't survive either. If the business stays hand-coded it costs too much to be viable, if it moves to Ai it looses any advantage over doing it youself.
As a largely solo dev I found I can't estimate well unless it's a common task, and it's easy to find tasks grow exponentially if it touches too many layers.
Asking "how long do you want me to spend on this?" got better results, because I got more idea how important tasks were to the business and can usually tell if something is going to take longer than they want. (Or know when we need to discuss scoping it back, or just abandoning the feature)
It also helps because software is one of the rare engineering fields where code is non-destrictive and can be changed after the fact.
The carpenters trick of measure many times, cut once, can instead just be cut and re-size if wrong size, which can often be quicker.
Asking how long they want me to spend on it also let's me know how solid it needs to be engineered. Is it something that needs doing right then first time, or do we just want something rough that we can refine later with feedback.
I think that that's how you solve the estimate problem - by having an understanding of how many layers it's going to touch, and how big of a change it's going to be for each layer.
Less effectively too (depending how you travel). Most hotel rooms I'm there for a couple of days min, most normally a vacation week. I settle in, move the chair somewhere sensible, unpack clothes and charge, set up for the short term. Poster seems to be talking about very short lived instances where you can kill them at any time. I'm never able to leave a hotel room at a moments notice - that's where my stuff is...
Pets vs Cattle seems much more clear, cattle is there to be culled, you feed it, look after it, but you don't get attached. If the herd has a week member you kill it.
I'd be a heartless farmer, but that analogy radically improved my infrastructure.
It seems most likely that with pubs not so active over the pandemic, then operating with more socially distanced rules, new pub users just never learnt the "only used in pubs queueing system".
Which is a weird blindspot for the article, where they reference a normal queue as something from "border control", rather than then thing you do everywhere but the pub. Without the introduction to the system they just use the system they use everywhere else. And don't worry it takes longer because it's a convenient time to check your phone.
reply