Daycare is completely free in Poland since 2024 (you need to submit an application to ZUS, but there are no limits, it's always accepted), even the private ones.
You only pay separately for food (10 zł per day the child is actually attending to the daycare).
I switched from a Polish company to a German one (both remote), but my pay is more or less the same.
The difference is that in Poland to get that money I have to be a "top performer" with a lot of stress and not a lot of time, while in Germany I can be just a mid dev.
I mean a lot do get reputational damage (e.g. a lot of people hate Jira because how slow it is, or Microsoft Teams - same story) - it's just that nothing comes of it, so "suffered" is perhaps the wrong word here. People curse them and still use them.
It is especially true for MMPBs (mass market paperbacks). It's a specific term for a specific format of books that are just recently being phased out. You can find more info about this online.
There are tons of price cuts that paperbacks (and especially MMPBs) use that they don't bother with on (most) hardcovers, because if you're getting a hardcover you probably don't care about absolute lowest cost.
And there's stuff much cheaper than MMPB but they're very rare (think phonebooks and old catalogs).
Sometimes people open issues without proper information. It cant be replicated and nobody else is jumping in that it affects them. You may suspect its something else, maybe with their environment, but if they don't engage what else can you do? Tell them you are closing it and specify what kind of info you need if they ever get around to providing it and it can be reopened.
"Unable to reproduce" is a fair enough explicit close reason. This is more about those "stale" bots that exist that just kinda close the issues because there hasn't been any response for X days. The annoyance with the practice usually stems from the fact that many of the victims of this comes from a lack of maintainer response.
This sort of bot punishes users for making even valid reports that aren't fixed immediately or missed by the maintainers for whatever reason including transitory ones, etc.
Constantly bumping threads/issues/whatever is generally considered rude, so this is why issue reporters generally don't do it, plus generally the reporter isn't solely focused on that particular issue
And sometimes the maintainer simply doesn't respond to a perfectly acceptable issue due to either the maintainer abandoning the project, not enough maintainers or simple neglect.
Yup. As a kid I could "entertain" (distract is the better word) myself by "drawing shapes" with the cursor, highlighting random things, switching between random cells in Excel, or just like... browsing through the system without any plan or reason.
Procrastination is hell of a drug.
I drew a lot of doodles and did things like that as well, but I think that they're less visually stimulating and simply "slower" so there's still some brain capacity left for learning.
Wait, what, Zed is Tauri? How?
One of their main things was that they implemented the UI layer completely from scratch using their own GPU-accelerated rendering engine.
It's got none of that browser-type stuff.
To extend on that a little bit: they use data centers located in EU, but owned by US cloud providers.
They can still pull the plug ofc, so it's only a small difference, but still
Sort of, they have no "hands", LLMs can only respond that they want to execute a tool/command. So they do that a lot to: read files, search for things, compile projects, run tests, run other arbitrary commands, fetch stuff from the internet etc.
Obviously the LLM inference is super heavy, but the actual work / task at hand is being executed on the device.