- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Frist, paging @Fox.
Admin
I was waiting, just for you.
Seriously though, do you not recognize your own work? If anything I did every come back to me, I'd know, because my name would be right there in the About box (my pride is just that big for that), and even if I don't have the source code, I'd at least remember a little about it.
For example, anyone want to ask me about my attempt for simulating Windows on the Ti-83+ using the on-board TI-BASIC interpreter?
Admin
Does not having proper indexes really make it that much slower than the original FoxPro version?
Admin
Well, since he didn't have "the source code", he probably made all of the columns
CHAR(MAX)(or whatever the MySQL Equivalent is). The amount of IO to do a table scan for everything...Admin
Maybe there were multi table joins on blob or character columns without indexes. One of my early MySQL projects I forgot an index and search would time out: adding a few select indexes reduced the search time to less than a second for 10000s of records!
Admin
for mua?
I'm honored
Admin
Although I failed the inb4 @paula
Admin
:rofl:
Admin
-hmph-
always forgetting the resident vixen, aren't we?
just because his name is fox, does not mean he's the only one!
:tangerine:
Admin
Paging @accalia too!
Admin
This ending is rather unsatisfying. It brushes over (what i assume is) the part where the old guy tries to implement the new system and hits a brick wall of loading and processing times and proceeds to rage at the young developer, which is arguably the climax of the story. Instead it just skips over to "they used the old system until the old guy retired" without mentioning the good part of how they arrived at that decision.
Admin
Took you long enough *shakes head*
Admin
Sorry, no points for you. One thing I learned from being married is that you don't get any credit from doing what a female asks after she asks; you only get credit for it if you did it without being asked. Also no credit if it's something you normally do anyway. Also no credit if you did something without being asked, but it wasn't the thing she wanted done but hadn't yet asked you to do. Also no credit if ...
Admin
QFT.
5 points to
GryffendorHardwareGeekAdmin
Continue?????? WHERE DOES IT END?????
Admin
:thats_the_point.bmp:
Admin
I thought my over-exaspirated WHERE DOES IT END????? made that obvious :)
Admin
"Sadly, he couldn't find the original sources for the program anywhere" --- that's TRWTF, right there.
Admin
Btw, I remember by the time of Win98, Apache is still in v1.x and still use fork() (i.e.: multi-process instead of multi-thread. Since Windows favors multi-thread over multi-process, there were known performance issue. And what's more, you don't get connection pooling this way), maybe that could be accounted for certain level of slowness in the story.
Also, depending on how the original program is written, since data in FoxPro never actually leaves the program (the data engine itself IS running in your program), there are some way of writing code that will NOT cause performance issue on FoxPro but will cause problem on virtually every other programming languages, if the way he process data is such way, he'll need to refine the order to fetch data or it'll surely cause problem.
To give an example, in FoxPro, if you select all data in a table then use code to do filter, there will not be much performance difference than select data with "where" clause even if on a very large table. Try doing that on any other programming languages. :stuck_out_tongue:
Admin
In answer to the Article's question: No.
He has no "bright future" (and the phrase bright future is as used by those in software management speaking about themselves). After a "disastrous" start (the product worked as expected first time out of the box) he recovered and showed potential with V2. But he threw that away by having nothing more to do with it when it didn't work. I.e. He passed up the opportunity, even with the incentive of up front cash with oodles of more cash available, to increase the complexity or make it more "enterprisy" without actually fixing anything.
Admin
HardwareGeek must be single it ends with "No credit at all."
Admin
There's the one we like and the one we like...to :trolleybus:.
Admin
10 points to
Slytherinrc4Admin
:smile:
Admin
Isn't that a bit microaggressive?
Admin
Back in the 1990, programmers used to design the algorithm first, and then translate that into code. This lead to the effect that many programs didn't only run at the first try, but even ran correctly.
At that times this was considered acceptable.
Nowadays, we've overcome those outdated ways. We prefer
shittystilistically, buzzwordically and sementicully approved documentation and an iterative convergent process™ that takes much more time but has the undeniable advantage of being enterprisey® and capital sink effective.Obviously, that guy did it according to best accepted practice both times.
Admin
No.
It is at the same time accurate and macroaggressive, as any :trolleybus: can confirm.
Admin
Admin
They weren't real clients, they were scientists and other nerd folk. And/or the guy next desk. Or yourself.
And even if they didn't know what they wanted they knew after a bit of chit-chat.
Admin
As a QA person, I can't wrap my head around the idea that devs know what the fuck they intended to code before they sat at a keyboard and drooled all over it. :trolleybus:
A lot of the time, the important algorithms are known in advance. If you hand an accountant an algorithm in pseudocode of how to calculate their taxes, they can spot the mistakes that would have taken hours of testing to find.
Admin
Admin
Admin
On the second thought, no. It would make your posts even more confusing and stupid.
Admin
Liar! We all know what you do while watching fox porn.
Admin
Admin
Admin
The joke's on him: all that camera's filming is a cracked floor tile :stuck_out_tongue:
Admin
My plan folded ...
But I did got this one ...
[image]Admin
Admin
A crack is a crack and it could be filled!
Admin
Ps. @RaceProUK you need to hitch a ride on the roomba again ... I see a lot of dust in the crack.
Admin
:giggity:
Admin
Yes, when are you going to do something about that flooring?
Admin
When you pay me the cash monies :stuck_out_tongue:
Admin
RacePro: Professional cam babe :D
Admin
I usually imagine who the program I'm writing will be work before actually writing code, so if no one change my basic assumption on how the code works I can code the program correctly at the first time.
Now if any of the fundamental assumption change, my world breaks and all kinds of
chaoserratic bugs sneaks in what I create.I really hate requirement changes... especially those who are made before consulting the clients, and require me to change back next time. Three or four back and forwards and I'll lost my mental image on the program, and will have to resort to what they call convergent process™.
Admin
Yes, every single one of yours.
Admin
:)
Admin
it's never going to be blatant sarcasm if you continue to omit the <sarcasm> warning tags.
Admin
That kid's name ..... Albert Onestone