I disagree. I think the default option should be what users expect, and users expect “copy” to do exactly that: copy without modifying the text.
I like programming and anime.
I manage the bot /u/[email protected]
I disagree. I think the default option should be what users expect, and users expect “copy” to do exactly that: copy without modifying the text.
Yes but karma makes it worse. It incentivizes getting getting upvotes because you don’t want to “ruin” your karma. Expressing controversial opinions, even if they don’t generate downvotes, are discouraged with karma. Even OP says he gets a dopamine hit by seeing the karma number go up.
I don’t like karma. It incentivizes short, meme-y posts since those are things that get gets a lot of karma.
Yeah that’s a good point. It’s telling that inheritance is by design difficult to change unless you follow very specific rules of good OO design patterns.
I guess it’s easy to write bad code in any programming paradkgm but inheritance makes it easy to screw up.
Most of us have bad memories of over-complex hierarchies we regret seeing, but this is probably due to the dominance of OOP in recent decades.
This sentence here is why inheritance gets a bad reputation, rightly or wrongly. Inheritance sounds intuitive when you’re inheriting Vehicle
in your Bicycle
class, but it falls apart when dealing with more abstract ideas. Thus, it’s not immediately clear when and why you should use inheritance, and it soon becomes a tangled mess.
Thus, OO programs can easily fall into a trap of organizing code into false hierarchies. And those hierarchies may not make sense from developer to developer who is reading the code.
I’m not a fan of OO programming, but I do think it can occasionally be a useful tool.
If the work I’m doing is on a feature branch on remote or locally, why does it matter to the rest of the team? My integration steps can be done on a server instead of locally. TBD forces teams to collaborate synchronously since changes are pushed straight to trunk. Rebase or squashes are irrelevant here.
Another poster put it great: TBD is trying to solve a culture problem. Feature branches and pull requests into main is much more flexible. The only time TBD make sense is for small teams - like 2 or maybe 3. And even at 2, I’d much rather create feature branches that merge into main.
Precisely. In practice, trunk based development just means your branch is local instead of on remote.
That or messages getting delayed so sorting is out of order. If you are using a score based sort, votes also come in late too. Could also just be bugs.
Federation is buggy and lagged behind especially with the influx of users. It’s currently not scaling very well.
Edit:
Also see this PSA: https://programming.dev/post/17801 which is a setting for site admins to improve federation, but then again, it may help that much.
There also may be issues between federating between different version of Lemmy.
Yep, though federation syncing is really slowing down. This post from [email protected] is at 44 comments from programming.dev but 112 comments on the beehaw instance.
People forget that when Reddit first started, it only supported link submissions and then later self submissions. That’s how imgur got started - it was a gift to the users. It was only relatively recently when Reddit supported image and video hosting.
Ehhh, I don’t quite agree with this. I’ve done the same thing where I used a timestamp field to replace a boolean. However, they are technically not the same thing. In databases, boolean fields can be nullable so you actually have 3-valued boolean logic: true
, false
, and null
. You can technically only replace a non-nullable field to a timestamp column because you are treating null
in timestamp as false
.
Two examples:
A table of generated documents for employees to sign. There’s a field where they need to agree to something, but it’s optional. You want to differentiate between employees who agreed, employees who disagreed, and employees who have yet to agree. You can’t change the column from is_agreed
to agreed_at
.
Adding a boolean column to an existing table. These columns need to either default to an value (which is fair) or be nullable.
Totally agree with the dope domain name. Not going to lie, a big reason for picking programming.dev
was to be /u/[email protected]
Super cool to see this instance getting great exposure.
TIL about the squircle
Nothing wrong with recommending a Mac. I’m not a Mac guy myself but I am pretty productive with one.
The code in the community’s banner is in python 2. Can we get that changed?
Yikes, looks like there are some serious query problems. Paging in postgres and ordering by an unindexed column.
A new community to request new communities instead of using the meta community. How very programmer of you.
Yes it can be an issue because the GPS doesn’t know where you are and thinks you are on an aboveground street. Freeway tunnels can have multiple exits too.