|
|
|
Congrats! That's great. 
By the way, a "return" to sanity implies that ...... Oh nevermind, congrats. 
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Congratulations! 
/ravi
|
|
|
|
|
Very well done. I know how hard that is but also how rewarding.
Anyway, it's done now; sit back and enjoy the fruits of your labor!
|
|
|
|
|
N_tro_P wrote: walked the official graduation ceremony last week and earned my Masters of Science of Software Engineering!
Earning a Masters while working professionally, being the sole earner for a family of 4, being a husband, being a father, and often even a mentor is extremely tiring. It is for the most part an unrewarded venture unless you personally make it a reward. The things I learned and skills I grew were amazing but extremely tiring and nearly at a drowning level. I have no idea how I am still married, have kids that do not have police show up at my house but instead receive Student of the Week awards, and a job that pays quite well.
Sounds like you're doing something right--and if nothing else, then at the very least, setting a great example for your kids. Some people hardly ever seek credit for their own accomplishments, so for all that's holy--enjoy the moment. They're generally too few and far in-between.
|
|
|
|
|
Congrats
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
|
|
|
|
|
N_tro_P wrote: Would it shock you to learn I received an award?
Quote: “It startled him even more when just after he was awarded the Galactic Institute's Prize for Extreme Cleverness he got lynched by a rampaging mob of respectable physicists who had finally realized that the one thing they really couldn't stand was a smartass.”
Well done and all that but ..
Memento Mori!
I am not a number. I am a ... no, wait!
|
|
|
|
|
Congratulations - you'll never, well mostly never work as hard as in university...
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Congratulations .. that IS an achievement.
It's great to have family who understands and supports you... Thank them and the almighty 
Thanks,
Milind
|
|
|
|
|
Congratulations! 
And nice display name too. 
You have just been Sharapova'd.
|
|
|
|
|
Congratulations ! ![Rose | [Rose]](https://www.codeproject.com/script/Forums/Images/rose.gif)
«There is a spectrum, from "clearly desirable behaviour," to "possibly dodgy behavior that still makes some sense," to "clearly undesirable behavior." We try to make the latter into warnings or, better, errors. But stuff that is in the middle category you don’t want to restrict unless there is a clear way to work around it.» Eric Lippert, May 14, 2008
|
|
|
|
|
Congrats!
I started Open University a couple of years ago and I'm still stuck at the first year of college... 
When I started I still even lived with my parents (but I did have a full time job).
No girlfriend or kids, but I still don't move very fast (not at all currently).
Nothing but awe and respect for doing this in four years in your current situation  
|
|
|
|
|
|
|
Congrats!
N_tro_P wrote: It is for the most part an unrewarded venture unless you personally make it a reward.
And there-in is the answer for why you're still married and have kids that receive Student of the Week awards -- because to be successful and a role model, one has to make something that might be intrinsically unrewarding personally rewarding.
I appreciate you writing that, I've been struggling with some motivational issues and what you wrote has helped!
Marc
|
|
|
|
|
I imagine we can all agree that a runtime error (something that blows up the program at runtime) or a logical error (doesn't blow up, but produces the wrong result) are bugs. Of course, there are other categories, like a "performance bug" -- produces the right result but takes too long. In any case...
What about syntax errors -- those things that the compiler (or the IDE) detects before you even run the code, and in fact prevents you from running the code.
Would you go so far as to say that syntax errors are a subset of what we call bugs? Or do you think that something can only be called a bug if it manifests when the program is run?
Marc
|
|
|
|
|
A bug is the failure of code to fulfill business requirements.
|
|
|
|
|
Well, a basic business requirement would be that your code can compile into a binary/runnable format.
|
|
|
|
|
Code that compiles, most basicly
Fulfills the contract and stated purpose. client gets what he paid for or sues/bad reviews
Does not cause RISK (data loss, intrusion, etc), again lawsuit risk
|
|
|
|
|
Nish Nishant wrote: Well, a basic business requirement would be that your code can compile into a binary/runnable format
That would not be a requirement of the business. That would be a technical requirement.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Technical requirements and business requirements have some overlap.
|
|
|
|
|
Business requirements define "what" the system should do, while the technical requirements define "how" the system should met those requirements.
And defining the binaries that are output is most definitely a technical requirement.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
I think this is an excellent, succinct answer, though it doesn't completely capture the 'why' of bugs. A bug is a defect that has to be repaired before the program is in some sense perfect. Mandeep8 wrote: A bug is the failure of code to fulfill business requirements.
means the code is perfect if it perfectly fulfills business requirements.
All kinds of run time errors keep the program from perfectly fulfilling business needs, though if the error is handled, the program may continue to fulfill some business needs. A compile error is a bug in this definition, since a program won't run if it doesn't compile. A program may run without error and still not fulfill business needs if it is incomplete or incorrect. This is a defect in design or implementation. Even if the program does exactly what its developer intends, if it doesn't meet the user's needs for which it was created, it may be said to be defective. This last kind of defect in design is the hardest kind for developers to get their heads around. It's not about what you intended, it's about what the user needed.
|
|
|
|
|
In the old days, they were considered bugs. So there were 3 levels ;
- compiler errors
- runtime errors (program crashes)
- logical/functional errors (program does not crash but gives incorrect output)
Today most people don't consider compiler errors as bugs.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
