|
After a little thinking: You don`t need a laser, just a big box.[^]
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
That would work if you had the box at the door and the burglar had to pass through it.
Be fun to watch!
I'm not sure how many cookies it makes to be happy, but so far it's not 27.
JaxCoder.com
|
|
|
|
|
Make the box temting enough and let him steal it. He will open it at home and you have no mess.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Like the guy that created the exploding Amazon box. Funny!
I'm not sure how many cookies it makes to be happy, but so far it's not 27.
JaxCoder.com
|
|
|
|
|
Maybe you feel similar about it as I do - before approaching Other People's Code, poke it with a stick from a distance.
As I've coded I've become less judgmental of other styles, but not of lack of craft (code with anti-patterns, obvious bugs, or just rube goldberg contraptions)
Still at the end of the day, if you build something, you should be forced to use it/rely on it. Suddenly software would be a lot less rickety. 
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: if you build something, you should be forced to use it
 Dogfooding should be mandatory!
Either that or be forced to handle end user support for the products you deploy to the world. When my main objective is to keep the support line from ringing, I put a lot more care into what ships. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
kmoorevs wrote: Dogfooding should be mandatory!
Hear, hear!
/ravi
|
|
|
|
|
kmoorevs wrote: Dogfooding should be mandatory!
Either that or be forced to handle end user support for the products you deploy to the world. When my main objective is to keep the support line from ringing, I put a lot more care into what ships.
These two items should be in the company employee manual.
Do not hire any people unless they agree with these.
|
|
|
|
|
gosh i was hoping to never hear that phrase again after i left Microsoft.
Real programmers use butterflies
|
|
|
|
|
Nice idea in principal but maybe not practical in reality. I generally use the code I write a lot, but not the end product. I've worked on sites for holiday companies, insurance companies, printer companies, sweet companies, building companies...in my entire career I think there has been one website I have worked on that I would actually use as an end user. Not because they're bad products, just because I am not the intended consumer.
|
|
|
|
|
|
honey the codewitch wrote: if you build something, you should be forced to use it/rely on it.
I'm glad that's not the case for home builders. 
Social Media - A platform that makes it easier for the crazies to find each other.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
haha
well i do think maybe they should stay in a home they built. Just not someone else's
Real programmers use butterflies
|
|
|
|
|
lol, actually "builder's own home" in a sales description should make you run. I learned the hard way (a long time ago) it was his first house. We both learned much.
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
|
|
|
|
|
honey the codewitch wrote: you should be forced to use it
The irony is in many many cases, I can just look at the code and figure out how to break it. Forget trying.
|
|
|
|
|
Right? I spent part of my youth going places online where i wasn't supposed to be, by breaking things like printd which for some reason a lot of people kept public facing back in the day. I learned a lot but when I grew up I put away childish things, to paraphrase Paul.
I have a knack for breaking things that might even surpass my knack for creating things (i guess entropy is easier though )
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: I have a knack for breaking things that might even surpass my knack for creating things (i guess entropy is easier though )
I can relate to that, but in my case is not because I see the error, it is because the error finds me.
I have had IT problems with things where I had to say "I don't have a clue why that happened" with things that I would have granted as "stable" and nobody else had problems with.
I always say... I am a innate beta-tester... other say I am just the "unlucky fellow"  
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
That's a superpower!
You can do some proper damage if you're strategic about it.
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote:
You can do some proper damage if you're strategic about it.
I can't be stratetgic with things that seem random.
If I could I would play lottery. 
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
But it is a very valuable ?skill?.
Frank got Ed to try out his database program -- then fixed it -- repeat. Made a good team.
|
|
|
|
|
Yeah, in that cases yes. I agree.
But it annoys the hell out of me when I got hit by things that nobody in my range can repair and I have to call the IT Hotline to open a ticket.
99% of the time, they don'T believe what I say. They have to remote log in, then try some stuff (that 99% of the times bring nothing), then I have to show them what is or how comes (at least most of the times I can repeat the problems) the problem, then they try another bunch of "pre-compiled" steps and then say... "I will pass the ticket to the level 2 support"... and then start over again.
I have had tickets that went up to level 4 and I was still being more informed that the supposed specialist. The problem is... I have almost no rights to do things that could be done to fix it.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
With the applications that I've had to take over these past 12 months, I've learnt to scream in silence as the previous dev's are no longer around.
I've seen one application with all the controller actions, business logic and models in one file over 3000 lines long
Another application is written in MVC (no issue there), 47 business logic projects for each schema - nothing more than simple database logic in each project. Typescript used for the navigation and JQuery used for the validation
Every day, thousands of innocent plants are killed by vegetarians.
Help end the violence EAT BACON
|
|
|
|
|
Simon_Whale wrote: the previous dev's are no longer around
Oh I hate that.
Simon_Whale wrote: Another application is written in MVC (no issue there), 47 business logic projects for each schema - nothing more than simple database logic in each project. Typescript used for the navigation and JQuery used for the validation
What a mess. Probably some was a cut, paste, and modify job (navigation vs validation)
I don't envy you. I really don't like bizdev. I find it tedious, usually repetitive and often suffering from "designed by committee" syndrome because the client, the employer, and the devs each have their agendas. Outside of front end web development, business applications like online storefronts are my least favorite.
Real programmers use butterflies
|
|
|
|
|
I dislike your opinion (but like you still). Others people code is great; yours is, innit? For me, your code is.
I don't like VB6; but there was a German company paying money for this brownfield (an existing [succesful] project) nearby. Best lunches ever, by the way. We had German meats, and cheap. And lots of coffee.
I learned a lot from others people code', and happy with that; the project was several years old, containing code of several (intelligent, but not know-it-all) people. Accumulated knowledge of ten people, over several years. A brownfield in every way, but success written all over it. Our company made money and I learned from other's mistakes and their sometimes brilliant ideas (no sarcasm, YET).
Then there's this monthly report, relying on "bits" encoded as strings. So a 0 for no, 1 for yes, but as a VARCHAR string. Putting that in a (Crystal) report, asking why it is slow. Most of out code was like that, but users found it workable. Reason was one of our programmers had the idea that it'd be efficient to store bits as a string. That idiot was my boss. He knew better than the accumulated knowledge of the codebase, because his title was "manager".
He made the judgement to do a total rewrite, instead of a gradual migration. Within a two years the company died. I've not become less judgmental, but a lot more. If I don't like your code, I'll delete it and commit the improvement. No explanation either. Those who want to learn will ask what they did wrong; all the others don't deserve to be writing code in the first place. As you could guess, he was promoted and I was fired, and I made it pretty clear to be happy with that situation.
Others' people code is mostly a learning experience; it contains the combined efforts of all programmers involved in the years it existed - so respect the brownfield, you may learn from it. You may prefer a greenfield, but it will never be as mature as a brownfield. Existing products with a predictive revenue are to be treasured. If you new to the field, go for a brownfield and learn.
Dis years ago. Do we hold a grudge? Aw, we do. Aw, yes, we do. CodeProject knows our temperament. It harsh, but honest. We don't forgive. We don't forget. And we need not be anonymous, we sign with our name and be proud. Bismallah, pray to us. Pray to us; if you include enough silver, we might actually answer which Allah would not.
AND IF THERE ANY GODS LEFT TO CHALLENGE US, BISMALLAH, THEY BETTER LEARN QUICKLY.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
modified 1-Aug-20 8:08am.
|
|
|
|
|
I don't disagree with you. The post was intended as tongue-in-cheek, and something to reflect that (at least I think) most of us have experienced having inherited a nightmare codebase.
Honey is my name. I don't use my last name online because I don't need employers nor recruiters to be able to troll my online profile without my permission. I'm not ashamed of being somewhat anonymous. I do use my personal pictures online as my avatar, and like I said, my first name. That's enough to keep me out of most google searches.
I don't believe people should have that sort of power over other people.
Real programmers use butterflies
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
