Bank holidays would be really awkward. You start wort at 23 and the next day is off so you would just have to work that one hour.

Office workers could probably move hours around. It would get complicated for shift workers though. Paying overtime for work on holidays?

Fuzzy search solves this pretty good

Exactly! All applications can be shit, not just web sites.

People screw up CLI’s all the time (looking at you Google Cloud). They (used to) insist on using my installed python which automatically upgrades and breaks the CLI. Good job python. Good job Gcloud.

Yes you should. I think most comments here are about products that have millions of users where it’s actually worthwhile spending all that extra time and money to perfect things.

For most development, it isn’t worthwhile and the best approach is to wing it, then return later to iterate, if need be.

The same goes for most craftsmanship, carpentry in particular. A great carpenter knows that no-one will see the details inside the walls or what’s up on the attic. Only spend the extra time where it actually matters.

It triggers me immensely when people say “I could have made a better job than that” about construction work. Sure maybe with twice the budget and thrice the time.

That may lead to over-refactoring, leading to unmaintainable garbage code.

102 times if you count the one before the code.

This is more toxic then funny.

I agree. It’s written like “ugh I’m used to timezones, now what?”.

That’s what they meant by Dark pattern.

That leads to focusing on the nitty gritty details first, building a library of thing you think you might need and you forget to think about the whole solution.

If you come up with another solution half way through, you will probably throw away half of the code you already built.

I see TDD as going depth first whereas I prefer to go breadth first. Try out a solution and skip the details (by mocking or assuming things). Once you have settled on the right solution you can fill in the details.

Right,too much coverage is also a bad thing. It leads to having to work on the silly tests every time you change som implementation detail.

Good tests let the insides of the unit change without breaking, as long as the behave the same to the outside world.

As little as possible,I think

Yes that was the wrong comment. Hmm. Someone said they don’t use some of the FOSS tools because they are so bad.

I think the main complaint with Gimp is that it is way more complex than the simpler editors, without actually being excellent for experienced users, like Photoshop is. Photoshop is also simpler to use for beginners to Gimp really missed both targets.

Krita is simpler than Photoshop and Gimp but much more powerful than n base level like Paint.

I’d say layers and masks (and operations that go with that) are the main step up from entry level.

Edit: fix typo

Gimp is a shame, they really had something to begin with. I use Krita now which is way more like you would expect a FOSS image editor to be. Much more similar to Photoshop if you came from there.

At work, we use gimp headless though. The scripting capabilities are great!

They don’t want to pay architect salary to do decorating work and I fully agree. Problem is that stuff like this are often overlooked until someone makes a fuss about it, costing PR. The other 90 % of the overlooked stuff is never found though so it’s still a good decision to skip stuff like this.

I have done 14k edits over six years. I too like it for being therapeutic. I’d rather do micro-edita on osm than play another level of candy crush. Same kind of reward but you are also helping out creating something larger!

Honestly though, I don’t think osm will ever catch up to the commercial alternatives. Mostly because their harsh stance against automatic edits (and lack of version control). Also the lack of standardization is a problem. It’s very hard to create client applications because the data is structured way different in different regions.

Ffrom a dev perspective it’s also often “Yep that would take three days if we worked on it”. Two years later - no progress.

There’s a difference between an estimate and a promise to deliver.

ESC + (shift) ZZ is faster and also saves your changes!

For me, federation sounds simple in theory. In practice it’s not for end users. Forcing an instance to discover a new, unfedeated community is a pain in the ass, let alone finding that community in the first place. All these little services (e.g. listing all instances/communities) are scattered and you kind of just have to learn as you go.

The average user just wants a nice search - that searches through “all” of Lemmy - something that is obviously hard or even impossible (or even not desirable to all users)

I think the above commenter is misunderstanding that the user is also federated. All of these concepts are hard to grasp but will eventually sink in I hope.