things often get fixed or changed around once necessary. Not sure if that’s a wise decision here. The JSON exchanged between the servers is probably extra work if changed around later.
Exactly, changing a protocol is not like changing centralized functionality. Not only it introduces mess that could’ve been avoided and mandates some compatibility measures while every client picks up the modified protocol, but it also allows posts to be messed up while this is fixed — without a way to restore the data as it should be, because false data on the comments is indistinguishable from the user changing the selected answer.
Messing up or losing users’ data should be the biggest no-no in web programming, but some people are remarkably carefree about it.
It’s difficult to discuss development in public places like here. There’s always a hundred things on the backlog. People want this, other people want that and someone needs exactly the opposite if all of it. There are a a bazilion ways users can annoy each other and all of it needs fixing. Then a project needs to be stable and reliable. It also needs new features. Performance needs to be right… It’s a proper nightmare job to balance all of it and maintain a mid-sized project. On top of it people will feel entitled, send in security vulnerabilities, complicated stuff that needs review and messes with things, other devs want something to be cleaned up, changed around, want someone to write more or less unit tests… and that also needs time for a plethora of good communication. And then there’s the actual architecture design and coding, which isn’t easy to begin with.
I didn’t study the code. But I’d bet the representation in the database stays the same, no matter which way it’s phrased on transport. It’s some sql relation between answer and post either way. A UI will also want to know how to style a comment at the point it processes that comment, so it makes sense to have it there. On the other hand it makes more sense for the semantics to have it attached to the post. Then there’s who can edit it. We need to trust incoming notes from third parties anyway. And maybe admins or mods can change it as well. They might be on arbitrary instances. So I’m not even sure if it changes anything with security.
And then there’s always many ways to skin a cat in software development. We can have long meetings to write specifications. We can choose to be a bit more explorative and figure things out along the way. We can even choose to make mistakes and fix them later. I think that’s a great thing with computer programming. Fixing mistakes is usually very cheap compared to for example a mechanical engineer who maybe likes to avoid wrecking a $1m piece of equipment. But that also means software developers have the opportunity to work a different way. And there’s a time for each of the methods. The trick is to apply the correct one at the correct time. I really can’t make a good statement here, I’d need to read the code and judge based on all the nuances I just mentioned. It’s regularly not as simple as something appears from the outside.
Wow, that’s amazing crock of a shit of a speech you have there. You don’t know anything about anything, but you’re ready to pump out a whole pageful about it. It’s quite impressive.
You didn’t study shit, but you bet it’s all fine. You bet the database stays the same, and the protocol is all fine, and nothing is ever bothered by anything. It’s all some ‘SQL’ bullshit, why bother about it when smelly nerds can bother about it all they want, right? It’s just some ‘SQL’ fucking nonsense, it means nothing anyway. Just style the UI and process the comment, and it all goes away, you fucking nerd, why are you ever bothered about anything?
sniff
Oh maybe it might in fact make more sense to have it processed by the post instead of the semantics being attached to the fuck of the comment, what the fuck do I know. Just edit the fuck out of it, it makes more sense on the other hand. We need to trust processing by the semantics of the sense, why not. Who can edit it, incoming parties, yeah! Admins or mods, I’m not even sure.
sniff
Then there’s the skin the cat, we can have many long meetings, the specifications, choose a bit, make mistakes, what the fuck do I know. A bit more explorative, make mistakes, fix them, it’s all fine. That’s the great thing. Fixing mistakes. sniff That’s the great thing with programming. It’s very cheap compared to, uh for example to, uh a mechanical, who maybe likes uh to avoid. But that also means. The opportunity. There’s a time bang for each bang of the methods. bang
sniff
I really can’t make a good statement here. It’s regularly not as simple. The trick is to apply the correct one.
Exactly, changing a protocol is not like changing centralized functionality. Not only it introduces mess that could’ve been avoided and mandates some compatibility measures while every client picks up the modified protocol, but it also allows posts to be messed up while this is fixed — without a way to restore the data as it should be, because false data on the comments is indistinguishable from the user changing the selected answer.
Messing up or losing users’ data should be the biggest no-no in web programming, but some people are remarkably carefree about it.
It’s difficult to discuss development in public places like here. There’s always a hundred things on the backlog. People want this, other people want that and someone needs exactly the opposite if all of it. There are a a bazilion ways users can annoy each other and all of it needs fixing. Then a project needs to be stable and reliable. It also needs new features. Performance needs to be right… It’s a proper nightmare job to balance all of it and maintain a mid-sized project. On top of it people will feel entitled, send in security vulnerabilities, complicated stuff that needs review and messes with things, other devs want something to be cleaned up, changed around, want someone to write more or less unit tests… and that also needs time for a plethora of good communication. And then there’s the actual architecture design and coding, which isn’t easy to begin with.
I didn’t study the code. But I’d bet the representation in the database stays the same, no matter which way it’s phrased on transport. It’s some sql relation between answer and post either way. A UI will also want to know how to style a comment at the point it processes that comment, so it makes sense to have it there. On the other hand it makes more sense for the semantics to have it attached to the post. Then there’s who can edit it. We need to trust incoming notes from third parties anyway. And maybe admins or mods can change it as well. They might be on arbitrary instances. So I’m not even sure if it changes anything with security.
And then there’s always many ways to skin a cat in software development. We can have long meetings to write specifications. We can choose to be a bit more explorative and figure things out along the way. We can even choose to make mistakes and fix them later. I think that’s a great thing with computer programming. Fixing mistakes is usually very cheap compared to for example a mechanical engineer who maybe likes to avoid wrecking a $1m piece of equipment. But that also means software developers have the opportunity to work a different way. And there’s a time for each of the methods. The trick is to apply the correct one at the correct time. I really can’t make a good statement here, I’d need to read the code and judge based on all the nuances I just mentioned. It’s regularly not as simple as something appears from the outside.
Wow, that’s amazing crock of a shit of a speech you have there. You don’t know anything about anything, but you’re ready to pump out a whole pageful about it. It’s quite impressive.
You didn’t study shit, but you bet it’s all fine. You bet the database stays the same, and the protocol is all fine, and nothing is ever bothered by anything. It’s all some ‘SQL’ bullshit, why bother about it when smelly nerds can bother about it all they want, right? It’s just some ‘SQL’ fucking nonsense, it means nothing anyway. Just style the UI and process the comment, and it all goes away, you fucking nerd, why are you ever bothered about anything?
sniff
Oh maybe it might in fact make more sense to have it processed by the post instead of the semantics being attached to the fuck of the comment, what the fuck do I know. Just edit the fuck out of it, it makes more sense on the other hand. We need to trust processing by the semantics of the sense, why not. Who can edit it, incoming parties, yeah! Admins or mods, I’m not even sure.
sniff
Then there’s the skin the cat, we can have many long meetings, the specifications, choose a bit, make mistakes, what the fuck do I know. A bit more explorative, make mistakes, fix them, it’s all fine. That’s the great thing. Fixing mistakes. sniff That’s the great thing with programming. It’s very cheap compared to, uh for example to, uh a mechanical, who maybe likes uh to avoid. But that also means. The opportunity. There’s a time bang for each bang of the methods. bang
sniff
I really can’t make a good statement here. It’s regularly not as simple. The trick is to apply the correct one.