It's not that expensive. There are other reasons why people can't install one in Europe than money. Mostly for people living in apartments. In an apartment building you need the approval of other apartment owners to "modify the building facade". And some people have terrible neighbors. Another thing that happens in Europe is that if the building is 100+ years old, it's facade may be protected as a "historic building" and then you need another approval from some bureaucrats which are responsible for protecting historic buildings. And of course if you're renting, you need to convince your landlord if you want a proper AC not a portable one.
If the bottom of the window is 80cm or less from the floor you need safety glass. Therefore most windows are much further from the floor than that tube can reach. We also have very few sliding windows that allow such neat finish. A lot open at the top. Many turn left or right and are half the size of a door (because there is no AC) Running a crappy tiny portable single hose AC with the window open doesn't do much. Extra fun if you have roller shutters (for shade) with windows that open outwards.
The tube for my portable AC unit would quite easily reach the ~250cm to the tops of my windows and it is not unusually long. I'm not sure what makes you think that would be a problem.
I have one like that and so do my parents. But they're much less effective than classic split AC with an outside unit. A regular split can cool a bigger room to 24 even when it's 38 outside and is basically completely quiet. A portable AC cools down smaller rooms to ~27 when it's 38 outside and is noisy (50-60 dB).
That's cause you got the cheapest one and think all of them are like that. They come in different power levels and you can in fact find ones that are quiet.
People don't know which to buy. I got a really big one that doesn't make a lot of noise. I think on dehumidify it can suck 1.5 liters per hour out of the room. I think this because with 98% humidity the 0.5 liter tank is full in <20 minutes. The tank isn't removable, it has a lid 3 cm above the floor. Just low enough that one cant leave a large enough container under it.
Some of them use the waste heat to evaporate any accumulated water and have it come out of the heat exhaust as slightly humid air. The one I got when I lived in Hawaii had a hole where water would drip out of and you could attach a hose to it.
you don't need that on balcony, most of the apartments have balcony, stupid excuse, same applies for historical buildings with balcony
If a tree falls in a forest and no one is around to hear it, does it make a sound?
If there is a balcony and you install it there, so nobody can see it from the street, is there an AC installed? Can you even use your balcony the way you want and place there big cardboard box if you need? Same thing. Facade is a one thing, balcony is something completely different, if you can't even use it, what's the point in having it.
my guess is that the outdoor AC unit reached its maximum working temperature...
since we're not that used to extreme heat in EU, units with max working temperatures of 45 degrees Celsius are pretty common and the air around the AC unit is warmer than regular outdoors air, doubly so if they're placed on the ground and the glass from the building reflects some additional heat from the sun.
the risk of this was broadcasted in our local news for home AC owners when the forecast reached 40, as lots of apartments have the AC on partly glass-encased balconies, or on walls facing direct sunlight...
the sentiment "AI couldn't code last year, but now I use it for everything!" rings true for me... but I didn't flip cause AI is now better than me... I flipped cause now I am faster with AI than without it...
A year ago the AI output was so bad that getting it up to my standards took more than writing it myself from scratch. And nowadays it is faster for me to start with AI output and iterate from there to reach quality submission.
The ninety-ninety[0] rule was a thing talked about 40 years ago, long before anyone thought of AI coding. AI can nowadays make the first 90% of the task very fast and good enough. The last 10% is still the hardest part of coding by far.
I probably spend even more than 20% of my time away from the computer these days. AI is great for this. I task Claude with something and while it's working I have the time to think about next steps, I can take a walk outside, have a coffee, talk with coworkers about my ideas, ... I'm paid to think, not to sit behind a computer.
There are people who say it's better to have multiple claude code instances crunching different stuff at the same time, and using the waiting time to prompt up another one. This might result in opening up more PRs faster but in the end it's not more productive. Context switching takes time, it divides your attention so your work is more sloppy and less thought through, and driving your brain too much makes you tired which again results in more mistakes. Having to compensate for this negates the productivity gains by finishing more grunt work faster.
I love having no task assigned. Means I finally have time to do code maintenance. Upgrading dependencies, fixing bugs (there are always some), clearing TODOs left in code, improving performance, improving dev tooling or monitoring configuration, cleaning up unused code, improving documentation, ...
And the best part is that since it's not an assigned task, nobody is waiting for it, so I'm under zero pressure.
Sadly it doesn't happen that much as we're always pushing for more new features out.
In SCRUM though if that stuff isn't in the sprint you'll probably get backlash from QAs as it needs testing etc, or questioned why you're bringing in that stuff.
Majority of the things I've mentioned don't need QA. Improving performance of an existing code is fine as long as it passes the existing test suite. Dev tooling / Monitoring is for devs only. Unused code is unused, just needs review from another dev to confirm. Documentation is for devs only.
And I work on the backend in a smaller company these days. Our backend code doesn't pass through QA, we just write tests and another backend coder reviews the tests if new tests are written. QA only handles frontend.
We have 257 python dependencies in our production app (over half of them are direct dependencies). We don't have any upper bounds in our pyproject.toml and we just run `uv lock --upgrade` every 2 weeks through GH actions.
We have good test coverage so if anything breaks the tests fail + we have AI assisted review process for this -> when GH action creates the upgrade PR, an AI workflow uses a python script to list major and minor version updates, finds and links changelogs, summarizes them, and makes the risk factor analysis for each package based on how we use it in our codebase.
It's mostly painless and we don't have to deal with upgrading packages one-by-one, checking which packages are outdated, or having outdated packages. Very rarely something breaks in a way it can't be fixed in our code and we need to wait on a fix from the dependency author (maybe once a year?). And in the past 3 months only one such upgrade required some changes to our code, there were 18 major version bumps in that period.
I wish we could do this on the frontend as well (I'm a full stack dev), but we don't have enough tests on frontend for this to work safely. Tests on the backend are easier to write and are more important so I believe every codebase should have them. And if you do, you can just auto-upgrade everything.
It really is far easier than you'd think if you haven't tried.
Different countries use different definitions of what "small business" or "micro business" is. And people usually use their own local expectations they're used to. I'm not from the US and a company with 100 million revenue is far from a small business to me.
In EU where I'm from the micro/small/medium business sizes are tied to both employee count AND revenue. Micro is below 10 employees and below 2 million € revenue, Small is below 50 employees and below 10 million € revenue, Medium is below 250 employees and 50 million € revenue.
So if you had 100 million revenue you would be a large business even if you had less than ten people.
Also this doesn't just mean more disk space usage, but also longer local build times... for the app I'm working on `exporting to image` takes 71.5 seconds with containerd, without containerd it's 4.3s (the rest of the build takes ~180 seconds). And that's just a 5.76GB image.
That's almost certainly nothing to do with the change. Please report this if you can with commands used.
Buildkit isn't changing behavior here.
Internally in docker there is a shim to make the legacy storage behave like containerd snapshotters (as well as it can, anyway--not perfect due to hard to resolve issues in the old storage).
But it still kept both the compressed and uncompressed versions of images.
What the actual fuck? Customers' expectations shouldn't matter at all if the things they expect is illegal.
And this is already a solved problem.
The city I live in (Bratislava, Slovakia) has some pedestrian-only zones in the "old town", and if you're in one of them, calling an Uber/Bolt forces you to pick a pickup spot where cars can go...
(arguably this still has issues with Uber/Bolt allowing you to choose bus stops as pickup spots, which is explicitly illegal - only buses can stop on bus stops, but it's still better than driving onto a road which does not allow cars in the first place).
EDIT: i mistakenly thought this was about driving on dedicated bike paths, idk why, but this is still a solved problem, the applications already allow to designate some roads as places which can't be picked as pickup/dropoff points...
reply