A group of researchers was studying how different people solve problems. They gathered a physicist, a mathematician, and an engineer and gave them each a problem: find the volume of a red sphere. The mathematician solves it first. Asked how, he explains that he used a simple formula. The physicist solves it next. Asked how, he explains that he submerged the sphere in water and measured the rise in water level. Hours later, they find the engineer buried in paperwork. Asked about his progress, he says “I can only find a table of values for the volume of blue spheres.”
post
Ha. I had a convo with a programmer in the 90s. He was explaining a complex problem and the steps to solve in the code, to adjust things based on user choices and parameters.
And I said why wouldn't you presolve all of them and then provide a lookup to go get the solution from a list. And he just looked stunned and walked away.
Ah my prior manager suggested something similar... Dynamic views that would adjust based on user set parameters... We set up canned views and called it a day.
He was let go, but always pushed for the art of the possible (even if it would take a few extra sprints to wrap)
Fun fact, most Tetris clones have a 4D table of all pieces and their rotations. Or multiple user selectable. The actual game generates them (look up "tetris recomp site:github.com").
why is this upvoted
Because he hadn't thought of what I suggested and it was much easier than what he was trying to program. I wasn't suggesting he write the program, solve it and table it; it was more like empirical knowledge/common sense stuff to narrow options, then fill the rest in based on what made sense. Then its just a horizontal or vertical intersection to find the outputs required instead of a complex calculation every time
Red thinks you’re making up words

B.S.
Dijkstra would have loved the lookup table solution.
He HATED complexity.
disappointing. no such algorithm.
yeah I looked it up
I would say Computer Scientist in place of software engineer.
Yeah, software engineers are the sanitation engineers of programming. Source: am one
Scientists research. Engineers do. We are the more practical of the two.
Also, any CompSci grad I've worked with couldn't write code for shit unless they learned how outside of their schooling, and yet so many go the CompSci -> programmer route instead of doing like SW Eng or something like that.
any CompSci grad I’ve worked with couldn’t write code for shit
Damn, that sounds pretty bad.
We had tons of math and theoretical work too, but we also programmed a fair amount: We had to write a renderer in one class, a compiler in another, various Android apps in a third, and in one elective I took we wrote a micro kernel OS as well.
It's not like the CS program is devoid of programming, norb would I say the SWE students are that much better off without outside education. CS is about half theory half practical for core education at least. The difference is you learn why and how which is more beneficial long term. After the first 6 months on the job the difference between the two on programming ability should be about the same with some more optimal solutions found by the CS student if any difference. It's a pretty short term problem.
It really depends on what you're building. In an embedded shop, lookup tables are first class solutions to most problems. Computer scientists though, 100%!
Depends on the available memory and size of the tables. I've worked on cases where time to compute didn't matter as much as shaving off three more bytes did. Large lookup tables would have absolutely killed us compared to running some math.
Good point! Good point.
I've seen bubble sort implemented because we had data that said it was faster and was slightly smaller for the exact type data we were sorting and its expected distribution.
I fondly remember the time I hired a QT expert onto an embedded app team and on his first project he imported a sort algorithm from std. He found the system got weird and glitchy, and often crashed.
Yeahhh turns out the algorithm he chose needed to make a copy in memory and the thread he was working in only had 2048 bytes of stack, so larger inputs would corrupt the stack allocated to the next thread. I had to explain to him that we had a full second to complete the math before we had to give back our semaphore, so saving a couple milliseconds on the sort was not a priority. Fun times.
not doubting you because the customer can be funny but wha?
if time to compute doesnt matter there are likely more minimal hardware options to optimize for look up tables and memory cost/space
There are so many situations where you can't just swap hardware. Robots on an assembly line? Yeah you've gotta use hardware that's gone through safety testing. They're not going to just swap hardware to make things easier. You want to ship an update, you do it in software and under strict testing regiment. Some of that hardware is 20 or 30 years old. Medical. Aeronautics. Aerospace. All of them and more are using older hardware that's often memory limited but can often just sit and process their next step, and they often don't have built in complex hardware features because those add potential failure points.
the hang up for me is more the not caring about time to compute
aeroish is my experience, and for me those have all cared about time to compute
generally that’s one of the biggest constraints to the point of being super strict
like major money being spent on modeled approximations and processing speed costs eclipsing pretty much everything on the design side
tables for weather, angles, altitude, position this would be tiny compared to some we’re using
30 year old equipment is even more taxed given the likely feature creep in my experience
I'm guessing you were doing in flight aero stuff? I've been more in the medical and manufacturing space but the aero I did we were doing post-flight processing for reports. We had almost no memory to operate on, probably because of all the tables you're referencing that others were using.
IIRC, Elite used lookup tables for trigonometric functions on certain target platforms (maybe the NES) because memory wasn't as much of a constraint as computing performance. It's a barrel of game compressed into a pint of code.
Your MOM is marginally optimal, nerd!
Hah, gottem.
It's either "gotcha" or "got 'im".
Nope. You’re wrong.
There is no such word as "gottem". This is a recent bowel movement from ignorant people. "Gotcha" has been around for generations, and the use of the apostrophe is quite simple.
holy shit.
you might be the biggest fucking nerd ever for being so thoroughly "em" who just got "gott"
hahaha gottem
(no but seriously dictionaries are descriptive not prescriptive; they add new words as the language evolves. if you were correct about new implementation of the language being "bowel movements from ignorant people" then you should be speaking Shakespearean English as that is Proper English™. the language wasn't finished changing when you stopped going to school, pal. I'd recommend you research linguistics as it seems you have a weak grasp on the concept and it's bringing your nerd card into question.)
Okay. So it's not a word. That's fine. The popular expression in this context is indeed "gottem" and it doesn't matter if you think that's a word or not, that's just objective reality. Suck it, nerd.
Gotcha addresses the person you're talking to, gottem is used to address a real or fictional audience, highlighting for them what you did.
When I was a kid and my mother was teaching me to read SQL, she really drove home that Elegance is in the eye of the beholder. While a C++ dev finds beauty in reducing a signal processing step to O(n) by recursing through five lines of bitwise ingenuity, a SQL dev finds radiance in completing the task without using any loops at all.
Alright to anyone who would question this statement. I am a mom, and have had extremely similar conversations with my kid regarding programming and perspectives.
Seriously it's important for problem solving to not get caught up in perfect solutions or solutions you think are the right path be cause of your own bias'.
Sometimes to solve a problem you are stuck on, or is proving too challenging the best course of action is to figure out why you are trying to solve it that way, and what other solutions there might be.
When I was a kid and my mother was teaching me to read SQL
Why would a mother do this, I'm horrified
In the case of my mother, she's pretty autistic and a very well known data scientist. This was her way of teaching me how she relates to the world - I'm quite grateful to her for it; it has given me a love of programming and allowed me get a great deal closer with her.
I am disappointed when someone comes into my career (systems analysis) without the ability to do even a simple SQL statement and it's become common since my employer realised they had too few analysts and hired 20 in my area for three of us to train
More mothers should teach their kids to query
Meh, Mongo and Elastic are the future, SQL is for... moms!
I expected the bottom to say something like "instead of cloud-native scalable microservices using AI models that cost an average US household salary per day to run", but maybe I've been in corporate for too long.


top 76 comments