|
Smashing a computer over coding you're doing for fun?
I get pretty annoyed when I'm playing sport and having a bad day, but these days I restrain myself from damaging equipment – it doesn't really work to get rid of the frustration and then you have to replace or repair the equipment.
|
|
|
|
|
I think you are taking your work (and programming) far too seriously.
Member 9063556 wrote: and smashed my personal laptop after a few coding mistakes
Maybe you should get one of these?[^]
That said, there have been times when I've come close to doing some damage. Fortunately I've stopped myself and stepped away from the desk (and sometimes the job) and taken the time to chill out and look at what it is that is causing a reaction of violence. Tolle (and others) have said it well: you can either accept the circumstances, try to change them, or leave them. The first is the hardest, especially when the $$$ are the only reason I'm dealing with the crap to begin with.
Marc
|
|
|
|
|
There is a difference between bad temper and passion. So many business environments are focused around not upsetting any one no matter how wrong they are. Which in my opinion is worse than a simple disagreement. If there were more shouting in software development then there would be more code.
|
|
|
|
|
lol[^]
modified 20-Oct-19 21:02pm.
|
|
|
|
|
responding in the VB thread below, I mentioned our current application had GOTOs in it.
As I removed one recently, I thought I'd check again.
NINE goto statements.
In a C# WPF MVVM application.
This is my favourite:
if (e.Key == Key.Delete || e.Key == Key.Back)
goto L1;
else if (e.Key < Key.D0 || e.Key > Key.Z
|| (e.Key == Key.C && Keyboard.Modifiers == ModifierKeys.Control)) {
e.Handled = true;
return;
}
L1: this.Text = this.txtLookup.Text;
I feel a little dirty, now.
|
|
|
|
|
Jail?! That's too good for him...
It's clearly someone who knows VB but do not knows programming...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
See thread above - my vision would start to go pink... 
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
It looks like the code has decompiled and then passed off as their own. You often see lots of GOTO's in decompiled code.
|
|
|
|
|
Interesting explanation for otherwise inexplicable coding.
|
|
|
|
|
Either that or the author is a numbpty!! 
|
|
|
|
|
No. It is not. Just kidding.
|
|
|
|
|
You wanna put the joke icon on that one - people who know you might think you have turned to the dark side...or is that the dumb side? 
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
I come from teh dark side. My mission is completed. VB6 shall rule all of you in sometime. We will conquer you all. BWA HA HA
|
|
|
|
|
"All your CODZZZ are belong to us"
"URGNTZZZZZ!!!!!" probably.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
|
It wasn't a bad language. If it was a bad language, there wouldn't have been such a demand for it in the business community. It did exactly what it set out to do - make developing business applications quick.
|
|
|
|
|
Demand doesn't make something "not bad" - see cigarettes, the first generation Fiat Panda, and Sharknado 2.
|
|
|
|
|
Perfect argument!
Case closed!
"I had the right to remain silent, but I didn't have the ability!"
Ron White, Comedian
|
|
|
|
|
Pete O'Hanlon wrote: make developing business applications quick.
That what you say - but in 1999 when we went to Microsoft they sold us VB6 to develop the new version of our ERP. It was catastrophic...
It was a group - so-called - specialist in distributed network applications (they called it DNALab), and they almost ruined our reputation with that suggestion...
So the fact that even Microsoft didn't know for what VB is good, but they tried it on everyone without mercy... 
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: in 1999 when we went to Microsoft they sold us VB6 to develop the new version of our ERP
In 1999 Microsoft was selling VB6 for any business problem. It was their language of the day. 
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am.
JimmyRopes
|
|
|
|
|
So the problem was the people and not the language. MS fell victim to the same mentality as many large consultancies and tried body shopping where they'd drop a star programmer in to win the bid and, as soon as they had got the work, they'd drag that poor sap off to repeat the same process in other companies. It's known as bait and switch. You cannot blame the language for poor management practice. I've seen many fine programs written in VB6, in just the same was as I've seen many poor ones.
|
|
|
|
|
Pete O'Hanlon wrote: So the problem was the people and not the language.
It more was like Juno - two faced problem. People that try to sell you something that does not fit...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
I'm pretty sure the language would have fit. As I said, it's having people who don't know what they are doing that is generally the problem. There have been many ERP implementations that used VB6 and they seemed to be able to cope admirably. The problem is, it's easy to knock VB because it's looked down on and derided as a toy language by "serious" developers, and this is just a crass attitude. Unfortunately, this infantile behaviour has carried over from VB6 through to the VB.NET world and I can understand why we don't get many VB developers on CodeProject - because we have a self styled elite pouring scorn on them.
|
|
|
|
|
I can't agree more about that 'elite' behavior around - !
Also about VB6 and VB.NET - they are a different...
But believe me! I went to Microsoft every day for over 6 months. Their professionals worked with me all day long to build the base of our new system - it doesn't worked out - and in that case it was because of VB6...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
While VB.NET is a respectable beast, prior versions of VB were not.
It was VB, and not the programmer.
There is a negative connotation to "VB Programmer" because of the well know VB issues.
But I thank MSFT for VB. Because it failed so miserably, I was forced to buy Delphi 1.0 and give it a try. wow, it was everything VB wanted to be. Rolled my own component that weekend (an extension of the TEdit), which had taken me a week to do as my first VBX project.
Never looked back. Fell in love with Delphi. So VB is like the quirky friend who throws one of his cheesy parties, and I ended up finding my soul mate...
Because we were a Microsoft Partner at the time, I did not tell anyone I was using Delphi. I rewrote the ENTIRE application in Delphi in like 2 weeks, released the "updated" version, and the users were THRILLED. Gone were the memory problems, and the slowness, the instability. The DLL Hell...
Within 9 months it made product of the year at a big trade show. (we won't talk about the fallout when one of the other programmers on a DIFFERENT product realized it was not VB, LOL)...
Ahhh, good memories!
PS: The product shipped on a Single 3.5" disk, and supported internet updates via http requests!!!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
