I’d legit rather the software develop and occasionally spaff it up and break the server for a few hours every once in a while rather than the non-moving 5 year plans of Lemmy development.
Also, usually piefed.social is the only instance that gets hit with this as, being the flagship server - it takes the brunt of more ‘experimental’ features. Most other servers don’t upgrade to the latest iteration until they’re sure it’s not going to break them.
Good thing we have both development models and people can just pick what they like. I know which one I prefer. 😆 And seems Lemmy is approaching a release with their efforts of the last years as well, they’re at alpha.17 these days…
break the server for a few hours every once in a while
That’s not what botching the protocol does. It opens the way to mess up the posts that shouldn’t be messed up, until the devs get around to fixing it in the protocol and implement the fix on the server and all the clients change their implementation. By that time data on the posts can be irretrievably borked unless someone sits down and retroactively reassigns which answer is the the ‘selected’ one, which again might need an addition to the protocol because it isn’t a central database, except the dev also can’t actually unilaterally decide which is the ‘selected’ answer because the user might’ve changed the selected answer themselves.
Does this sound like ‘breaking the server for a few hours’?
This smells of fresh college-grad coding with people who can’t foresee how their programming decisions affect the software’s workings in the future.
You’ve spent 5 hours now raging against this “mistake”.
A mistake that you didn’t realize is only rolled out on their testing instance.
You have more than one dev stating they are aware of it and it’s on the list to be addressed later, despite claiming you had no way of knowing that. You do as of a decent number of hours ago.
You have another dev stating that this thing you think is a horrible development failure would require DB access to exploit in the way you hypothesized. Together with this only being in the bleeding edge test instance, this invalidates the overwhelming majority of your complaints.
And then you have the sheer balls to tell another commenter their comment was worthless, as it was too much speculation? Your entire fucking thrust is based off not just speculation, but a critical misunderstanding of the situation.
If you have the development background you claim, go make a fucking pull request. I normally hate that sort of shit, but after you’ve pulled the shit you’ve pulled in these comments, throwing your dick around like some sort of hotshot?
Put your money where your mouth is.
I’ve only got ten years experience, mostly in IT infrastructure admin/engineering, but one of the biggest lessons I learned early was to save my criticism until I actually understood what was going on. Another big one was to just not be a dick bag. And to apologize instead of doubling down when I was shown I was wrong.
I guarantee that if you bring this kind of attitude to work, the only reason you’ve lasted is because you’re on a large team. You’d be out in the first month at any of the (smaller) places I’ve worked.
I’d legit rather the software develop and occasionally spaff it up and break the server for a few hours every once in a while rather than the non-moving 5 year plans of Lemmy development.
Also, usually piefed.social is the only instance that gets hit with this as, being the flagship server - it takes the brunt of more ‘experimental’ features. Most other servers don’t upgrade to the latest iteration until they’re sure it’s not going to break them.
Good thing we have both development models and people can just pick what they like. I know which one I prefer. 😆
And seems Lemmy is approaching a release with their efforts of the last years as well, they’re at alpha.17 these days…That’s not what botching the protocol does. It opens the way to mess up the posts that shouldn’t be messed up, until the devs get around to fixing it in the protocol and implement the fix on the server and all the clients change their implementation. By that time data on the posts can be irretrievably borked unless someone sits down and retroactively reassigns which answer is the the ‘selected’ one, which again might need an addition to the protocol because it isn’t a central database, except the dev also can’t actually unilaterally decide which is the ‘selected’ answer because the user might’ve changed the selected answer themselves.
Does this sound like ‘breaking the server for a few hours’?
This smells of fresh college-grad coding with people who can’t foresee how their programming decisions affect the software’s workings in the future.
You’ve spent 5 hours now raging against this “mistake”.
A mistake that you didn’t realize is only rolled out on their testing instance.
You have more than one dev stating they are aware of it and it’s on the list to be addressed later, despite claiming you had no way of knowing that. You do as of a decent number of hours ago.
You have another dev stating that this thing you think is a horrible development failure would require DB access to exploit in the way you hypothesized. Together with this only being in the bleeding edge test instance, this invalidates the overwhelming majority of your complaints.
And then you have the sheer balls to tell another commenter their comment was worthless, as it was too much speculation? Your entire fucking thrust is based off not just speculation, but a critical misunderstanding of the situation.
If you have the development background you claim, go make a fucking pull request. I normally hate that sort of shit, but after you’ve pulled the shit you’ve pulled in these comments, throwing your dick around like some sort of hotshot?
Put your money where your mouth is.
I’ve only got ten years experience, mostly in IT infrastructure admin/engineering, but one of the biggest lessons I learned early was to save my criticism until I actually understood what was going on. Another big one was to just not be a dick bag. And to apologize instead of doubling down when I was shown I was wrong.
I guarantee that if you bring this kind of attitude to work, the only reason you’ve lasted is because you’re on a large team. You’d be out in the first month at any of the (smaller) places I’ve worked.
FYI, that user has been banned for a week for being disrespectul