Applying the Linus Torvalds “Good Taste” Coding Requirement (article)
-
My rules are as follows:
- Don't change shit unless you have to.
- Don't change shit unless you understand what it is doing.
- If you do need to change shit, change as little as possible.
Those have served me very well.
-
@lucas1 said in Applying the Linus Torvalds “Good Taste” Coding Requirement (article):
My rules are as follows:
- Don't change shit unless you have to.
- Don't change shit unless you understand what it is doing.
- If you do need to change shit, change as little as possible.
Those have served me very well.
Don't forget "If you don't know what a dev branch is for, delete the whole branch". :D
-
@lucas1 said in Applying the Linus Torvalds “Good Taste” Coding Requirement (article):
My rules are as follows:
- Don't change shit unless you have to.
- Don't change shit unless you understand what it is doing.
- If you do need to change shit, change as little as possible.
Sadly, you are in the minority. The prevailing attitude seems to be "If it ain't broke . . . break it", and over the past few years, most software development has looked like this:
-
@El_Heffe For client development I am using boring stack.
A front end framework that isn't crap + C# + SQL Server. Works well no problems with the volumes I am dealing with. (a few thousand).
-
@El_Heffe said in Applying the Linus Torvalds “Good Taste” Coding Requirement (article):
over the past few years, most software development has looked like this:
I remember reading something decades ago: Never use any software with a version number <= 1.0; it's certain to be full of bugs. Never use any software with a version number >= 10; if it's been around that long, the whole foundation is probably outdated. Of course, that was before software companies started trying to outrace each other in releasing "major" versions.
-
@El_Heffe said in Applying the Linus Torvalds “Good Taste” Coding Requirement (article):
@lucas1 said in Applying the Linus Torvalds “Good Taste” Coding Requirement (article):
My rules are as follows:
- Don't change shit unless you have to.
- Don't change shit unless you understand what it is doing.
- If you do need to change shit, change as little as possible.
Sadly, you are in the minority. The prevailing attitude seems to be "If it ain't broke . . . break it", and over the past few years, most software development has looked like this:
I think I'm guilty of that in my own project... (A Minecraft server plugin). Heh. I think I should start paying attention to some of you guys more.
-
@HardwareGeek said in Applying the Linus Torvalds “Good Taste” Coding Requirement (article):
Never use any software with a version number >= 10;
Is Windows 10 still NT version 7?
-
@Jaloopa It was never version 7. It was version 6.4, and then they changed it to 10.
-
@Yamikuronue said in Applying the Linus Torvalds “Good Taste” Coding Requirement (article):
I guess the thing is, I have a more devopsy philosophy: make safe systems where you know right away if you broke something, and then go nuts experimenting.
The problem is that you never know all of the crazy things your users are doing and now rely upon.
-
@boomzilla said in Applying the Linus Torvalds “Good Taste” Coding Requirement (article):
you never know all of the crazy things your users are doing and now rely upon.
Why not? Safe systems involve monitoring so you can find out what the heck they're doing.
-
@Yamikuronue said in Applying the Linus Torvalds “Good Taste” Coding Requirement (article):
Why not? Safe systems involve monitoring so you can find out what the heck they're doing.
Even if you knew all of their key strokes and mouse clicks you couldn't know how they were using the information and what assumptions they were making about the system and how it works.
What sort of monitoring are you doing there?
-
@flabdablet said in Applying the Linus Torvalds “Good Taste” Coding Requirement (article):
Really the only way to find out is to time the walking of a long list on the CPU you care about; and if you actually do care that much about the performance of a linked-list walk, it really is time to look at whether or not the linked list is the best data structure for the job at hand (clue: probably not).
QFT, especially the second part. Unless you have a really good reason for picking a linked list, you're probably better of with a vector by default.
-
@boomzilla Oh, I figured you were talking more about people using and depending on undocumented features. For that sort of thing you'd need to talk to the users.