He probably works in consulting, where time matters. When you attempt to implement hard coding standards in consulting projects, they bleed money, and it's perceived to be the fault of the person coding, even though it rarely is. It's even worse when you're in the middle of building a hard standard, and you're not able to "stop the train" as it were. Good code takes longer to write. Client projects are often quoted in flat figures. In other words, your job is to get them out the door quickly. Not to make them scalable and maintainable. Working with frameworks helps, but they can be a drain on resources as well.
Product development on the other hand is a totally different animal, but I suspect that the majority of programmers don't actually work there.
I strongly disagree. Seeing as it's my professional obligation to let you know that your code sucked, and I've replaced it with something superior, because you're a know nothing blowhard. Sure is a good thing that I'm a pragmatic genius who knows everything there is to know about anything. All these edits I made to your program without really understanding the basics of the system could have been hell to iron out otherwise.
Depends. I think you would be shocked to find out how common it is to find shops that use no repository system at all. Unless they've really thought it out, and come to understand that you need a repository system, even when you have only one developer because you don't want to lose your work -- They often just don't implement one. Which leaves new developers in the dark on the history of a project when they come into it. Even in shops where they have multiple developers, you don't always have one.
Nonsense. The real code metric is whether the final product performs as the client expects it to. Your code could have been written by pygmies and have no formatting at all. If it does the job, you've succeeded. Sure, maintainability is nice. But good practice is often a luxury that slows down the process. At least in the world of consulting, nobody cares if you've written a gem or a turd, as long as you've made your deadline.
Outside the world of consulting, maybe in R&D where things like scalability matter, I could see some kind of guided standard of best practices coming into play. But even then, your code is still subject to the whim of people who may determine their best practices based on personal bad habits.
At the end of the day, the best you can hope for is that the next guy who picks the project up understands the basics of the job. In my experience, this is incredibly rare. I've seen volumes of perfectly good code just thrown away and replaced with buggy semi-functional shit because the next guy on the project refuses to understand the basics of the language you're working with. This is very common on PHP and Asp.Net projects in my experience.
Only on Slashdot would there be a debate about what constitutes a tab. Half the reason I love this site. Although, why not bring up when it's appropriate to add a space before or after a parenthetical. Using spaces or tabs, you're going to get basically the same result in your code. The real variance is in parentheticals and curly brackets. Those are all over the board.
Hard tabs should always be kept at 8 spaces, it's the standard, and makes all the tools work as expected without any tweaking. So, unless your code also indents by 8 positions, use spaces.
5 spaces is the standard in general. 8 spaces is too wide, and makes the code too difficult to read. I know people that set their tabs at three spaces. Hence the problem with tabs. Of course, none of that really matters unless you're coding in Python. Inheriting Python code is absolutely awful unless you have document markup turned on in your editor ahead of time (so you can determine that you're not mixing tabs and spaces).
So are we seriously comparing DDOS attacks that any fifteen year old with five minutes and an internet connection can do to Stuxnet, Flame, Duqu, Gauss, and the litany of Isramerica's cyber war arsenal that we haven't even discovered yet? So they can use drones to spy on alleged Israeli nuclear facilities. So what? They wouldn't have drones at all if America didn't accidentally give them one. Point is: To win this, you need brain power. Ever since the Iatolas took power, driving everyone with half a brain into hiding, or exile, they don't have a leg to stand on as far as a "cyber war" goes. And I think it's clear that they understand how paltry their attempts have been.
It's like combining a frapuccino with a pizza. You could do it, but you wouldn't know if you were supposed to eat or drink it. We've done a lot of testing on this, and users don't like cheese in their coffee.
1. Arrogant != successful (these are orthogonal things)
2. Although you have every right to think highly of yourself, others have the right to scorn you. No particular reason, that's just their right.
If there is something to be gained by cooperation (and there usually is) an evolutionary stable strategy is one that cooperates more than not, but punishes folks for being non-cooperative (think a tit-for-tat). If practicing continued arrogance is considered by people to be non-cooperative, it could potentially be out-competed by other strategies (e.g., being humble until confronted with someone that is arrogant). No need to toss religion in there: that's a red herring...
Of course you also have the right to follow a non-optimal strategy in social interactions, but as with all choices, there are potential consequences.
Givalt!
You've totally missed it my friend. Arrogance is absolutely a survival plus strategy.
1. Woman love arrogance. They can't help themselves. They know what it means, and they simply can't get enough of it. That's because evolution has pre-programmed them to seek and mate with men who are confident in their ability to provide. Men provide, women make babies. This is the way nature works. The more incredibly arrogant you are, the more likely that you are to breed. The more likely you are to breed, the more likely you are to survive.
2. Arrogant people are better team players. Sounds counter-intuitive, but it's true. When you've got a team, or a group, you want people that can express strong opinions, figure out the best way to do something and move on. If you've got nothing but passive, humble, sheep like people... you might get the job done, but you'll never get optimum results. Not good for survival, my friend.
There is no such thing as unearned arrogance. If you're arrogant, you've been successful at something, and you have every right to think highly of yourself. It's a trait to be celebrated, not scorned. If you are humble, you see some value in prostrating yourself and exuding weakness. Unless you're religious, there is no reason to promote it as a positive trait.
If you're religious, then being a humble sheep is somehow of some value to you -- and seeing those that are not conforming, and making the sacrifice of self that you have would be reason for resentment. But being religious is a choice like anything else. I should never be asked to change because of the choices you've made. That's not a reasonable thing to ask of another human being.
Shit, I know whachu mean dawg. Jus cuz they be readin my packets an seein someonez downloadin dr who an homeland dont meen that I be stealin no pirate contentz an shit. Serisly its my brothuh. I cant controll what he duz wit my connectionz dawg. I dont wanna even know what he downloadin with his frends in russia. Shit.
I will, but they haven't come to my neighborhood yet. Bitches have only deployed it in Westport and the Plaza so far. So you'll need to talk to the smug hipsters and college kids.
Indeed. But there's a bigger problem. Until such time that you can clearly define what god is, then there's no way to find evidence of him. Science cannot find or validate negatives.
After reading the Haven Co press release they put out towards the end, I got the distinct impression that the whole SeaLand thing was a complete fraud. Did we ever figure out if SeaLand is actually a country, or not?
Slashdot Mirror
Oh yeah... how did I miss independent bots? That's badass too.
The space logo was awesome. It was the only one that was truly original, and it stands out as the best of the competition.
I can totally see Apple having to do this three or four times before they get it right.
He probably works in consulting, where time matters. When you attempt to implement hard coding standards in consulting projects, they bleed money, and it's perceived to be the fault of the person coding, even though it rarely is. It's even worse when you're in the middle of building a hard standard, and you're not able to "stop the train" as it were. Good code takes longer to write. Client projects are often quoted in flat figures. In other words, your job is to get them out the door quickly. Not to make them scalable and maintainable. Working with frameworks helps, but they can be a drain on resources as well.
Product development on the other hand is a totally different animal, but I suspect that the majority of programmers don't actually work there.
So far, the best insight in this thread. Wish app architecture was in scope for this discussion.
Cute. I see you're a Pico fan.
I strongly disagree. Seeing as it's my professional obligation to let you know that your code sucked, and I've replaced it with something superior, because you're a know nothing blowhard. Sure is a good thing that I'm a pragmatic genius who knows everything there is to know about anything. All these edits I made to your program without really understanding the basics of the system could have been hell to iron out otherwise.
Depends. I think you would be shocked to find out how common it is to find shops that use no repository system at all. Unless they've really thought it out, and come to understand that you need a repository system, even when you have only one developer because you don't want to lose your work -- They often just don't implement one. Which leaves new developers in the dark on the history of a project when they come into it. Even in shops where they have multiple developers, you don't always have one.
Nonsense. The real code metric is whether the final product performs as the client expects it to. Your code could have been written by pygmies and have no formatting at all. If it does the job, you've succeeded. Sure, maintainability is nice. But good practice is often a luxury that slows down the process. At least in the world of consulting, nobody cares if you've written a gem or a turd, as long as you've made your deadline.
Outside the world of consulting, maybe in R&D where things like scalability matter, I could see some kind of guided standard of best practices coming into play. But even then, your code is still subject to the whim of people who may determine their best practices based on personal bad habits.
At the end of the day, the best you can hope for is that the next guy who picks the project up understands the basics of the job. In my experience, this is incredibly rare. I've seen volumes of perfectly good code just thrown away and replaced with buggy semi-functional shit because the next guy on the project refuses to understand the basics of the language you're working with. This is very common on PHP and Asp.Net projects in my experience.
Only on Slashdot would there be a debate about what constitutes a tab. Half the reason I love this site. Although, why not bring up when it's appropriate to add a space before or after a parenthetical. Using spaces or tabs, you're going to get basically the same result in your code. The real variance is in parentheticals and curly brackets. Those are all over the board.
It's a standard, whether you like it, or know about it, or not.
A standard is pointless unless it's put into practice. Which standard is it part of?
Hard tabs should always be kept at 8 spaces, it's the standard, and makes all the tools work as expected without any tweaking. So, unless your code also indents by 8 positions, use spaces.
5 spaces is the standard in general. 8 spaces is too wide, and makes the code too difficult to read. I know people that set their tabs at three spaces. Hence the problem with tabs. Of course, none of that really matters unless you're coding in Python. Inheriting Python code is absolutely awful unless you have document markup turned on in your editor ahead of time (so you can determine that you're not mixing tabs and spaces).
If something declines by -43%, you're counting up, not down.
So are we seriously comparing DDOS attacks that any fifteen year old with five minutes and an internet connection can do to Stuxnet, Flame, Duqu, Gauss, and the litany of Isramerica's cyber war arsenal that we haven't even discovered yet? So they can use drones to spy on alleged Israeli nuclear facilities. So what? They wouldn't have drones at all if America didn't accidentally give them one. Point is: To win this, you need brain power. Ever since the Iatolas took power, driving everyone with half a brain into hiding, or exile, they don't have a leg to stand on as far as a "cyber war" goes. And I think it's clear that they understand how paltry their attempts have been.
It's like combining a frapuccino with a pizza. You could do it, but you wouldn't know if you were supposed to eat or drink it. We've done a lot of testing on this, and users don't like cheese in their coffee.
Oye... where do I begin...
1. Arrogant != successful (these are orthogonal things) 2. Although you have every right to think highly of yourself, others have the right to scorn you. No particular reason, that's just their right.
If there is something to be gained by cooperation (and there usually is) an evolutionary stable strategy is one that cooperates more than not, but punishes folks for being non-cooperative (think a tit-for-tat). If practicing continued arrogance is considered by people to be non-cooperative, it could potentially be out-competed by other strategies (e.g., being humble until confronted with someone that is arrogant). No need to toss religion in there: that's a red herring...
Of course you also have the right to follow a non-optimal strategy in social interactions, but as with all choices, there are potential consequences.
Givalt!
You've totally missed it my friend. Arrogance is absolutely a survival plus strategy.
1. Woman love arrogance. They can't help themselves. They know what it means, and they simply can't get enough of it. That's because evolution has pre-programmed them to seek and mate with men who are confident in their ability to provide. Men provide, women make babies. This is the way nature works. The more incredibly arrogant you are, the more likely that you are to breed. The more likely you are to breed, the more likely you are to survive.
2. Arrogant people are better team players. Sounds counter-intuitive, but it's true. When you've got a team, or a group, you want people that can express strong opinions, figure out the best way to do something and move on. If you've got nothing but passive, humble, sheep like people... you might get the job done, but you'll never get optimum results. Not good for survival, my friend.
There is no such thing as unearned arrogance. If you're arrogant, you've been successful at something, and you have every right to think highly of yourself. It's a trait to be celebrated, not scorned. If you are humble, you see some value in prostrating yourself and exuding weakness. Unless you're religious, there is no reason to promote it as a positive trait.
If you're religious, then being a humble sheep is somehow of some value to you -- and seeing those that are not conforming, and making the sacrifice of self that you have would be reason for resentment. But being religious is a choice like anything else. I should never be asked to change because of the choices you've made. That's not a reasonable thing to ask of another human being.
Pot, meet Kettle.
Shit, I know whachu mean dawg. Jus cuz they be readin my packets an seein someonez downloadin dr who an homeland dont meen that I be stealin no pirate contentz an shit. Serisly its my brothuh. I cant controll what he duz wit my connectionz dawg. I dont wanna even know what he downloadin with his frends in russia. Shit.
I will, but they haven't come to my neighborhood yet. Bitches have only deployed it in Westport and the Plaza so far. So you'll need to talk to the smug hipsters and college kids.
I would drop it in the about section, towards the top of the output.
Indeed. But there's a bigger problem. Until such time that you can clearly define what god is, then there's no way to find evidence of him. Science cannot find or validate negatives.
Just "adjust" the database. Problem solved.
After reading the Haven Co press release they put out towards the end, I got the distinct impression that the whole SeaLand thing was a complete fraud. Did we ever figure out if SeaLand is actually a country, or not?
Show me some capable development tools for Android that are at least as capable as Notepad++. There aren't any.