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.
I don't quite get what you mean by "experiment the same". As for the profile? It's just how my head works. By no means did I, nor would I, spend a lot of time on it.
Taking a leap at what you want - it's really just nature. Various people on and off CodeProject have their own nature and that leads them to how the do 'things' that can be done many ways. Coding does reflect quite a bit of the coder's nature.
Mine - I don't seem to have any boundaries in how my mind stores information. The cost of my last purchase of Jamaican Curry powder could be mentally adjacent to how a foreach loop is written in php. It doesn't matter - all things are part of all problem solving. There's a Latin quote for that: "If I cannot find a way I'll make one" - it's Hannible or Alexander the Great, or someone like that. That kind of view along with embracing insanity with gusto.
Look below, if you wish, to the link "Ravings en mass"
Me? - I'm heading home within the next few seconds.
I'm with you on that one. I have an app that was supposed to demonstrate to the user that we could gather their data from multiple sources, ingest it and spit it back out on a webpage. New items kept getting added to it for "demonstration" purposes. It has now been in prod for 3+ years and they just keep adding to it. It's a horrible POS I have to maintain.
Oh, god. I have something similar. I'm withholding names and won't go into specifics to protect the innocent.
At a previous job, I'd been telling the boss for years something he wanted automated couldn't be automated, unless he hired somebody to maintain the automation code, pretty much as a full-time job. Basically, the process being automated was a moving target.
So one day he decided to go ahead anyway and wrote the code over a weekend. It only worked for a week. And yes, somebody had to maintain his code all the time from that point forward.
Although the available choices could be scary, they are not really terrifying.
For bone chilling scares, I would point to decisions made to update old, large (1 million LOC and up), MFC based projects. Here are a couple of samples off the top of my head:
- We need a 64-bit version of the application(s).
- We want to introduce the application on the Chinese market, so let's add Chinese UI.
- Let's change the projects from Multi-Byte to Unicode Character Set.
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
Last Visit: 31-Dec-99 19:00 Last Update: 28-Jan-23 13:13