Most people I know would happily sign a document that states 'We hold these truths to be self evident that all men are created equal', even though the world shows us every single day that it isn't true.
In technical fields, getting that document approved would be a nightmare.
Maxwell's equations on the other hand are easy to get approval for. They are 'self evident'. Because they describe what we see, not what we want to see.
So thank god for Jefferson penning that line down and effecting how everyone thinks, because it shows us for some problems, the ambiguous kind, were truth is what we want it to be, technical fields will struggle to provide answers.
Its very fortunate, esp to make progress on all the ambiguous problems, that society props up a Jefferson now and then.
How did Jefferson get into that position and not some jackass, is the most important question. And the answer to that, with a modern developing understanding of networks and graph theory, has only recently started moving from the abstract and ambiguous to the more technical - https://www.youtube.com/watch?v=07KKYostAJ0
Looking at the code can tell you whether it was “implemented properly” - or at least, if it was done reasonably competently.
Relationships, though, can help you know if that properly implemented code was likely a fluke or not. Does the person ask questions? How do they ask questions? How do they communicate? How do they capture requirements? How do they push back when something seems unclear or unwise? etc.
Now, I've seen plenty of "demo-ware" software that has been presented as something that was much more than it actually was, but again, stuff like that always falls over, riddled with bugs and crumbling under load, when it gets substantial use.
Some things you really can't fake, and software engineering is one of them.
Input lag on devices has doubled or tripled from the 1980s while clock speeds have increased drastically. Reddit and Hackernews do essentially the same task, yet Hackernews' load times are almost instant while Reddit takes more than a second to load at times.
It's true that you can't fake a minimum viable product, but it seems to me there is a long way from that to actually making something good.
Noone wants to write low level code because learning it costs money, so instead we just throw more hardware at the problem until it goes away...
Human time is expensive, so it makes sense to throw anything cheaper at the problem first.
You'd think people who got that far would be confident enough to rely on their own skills/study to get ahead BUT even at that level, there is a lot of butt kissing to get ahead.
Is this actually true? You can bullshit coding...
How do you go about proving this? In the real world people are going to dismiss it. If you are playing against a politician you will be told that you simply have a bad memory thinking that some things exist that really don’t.
Same with the guestbook. It may even work. But on the inside it’s a pile of unmaintainable crap.
I've learned that most problems are easily dismissed by people as being "easy", "simple", just do this, just do that. I've found software forces you to really think through, "just do this" is easier said then done, how to do it?
Real problem solving is hard, and I do think computer science humbles you in that sense.
Here's an example, my friend always tells me he thinks we shouldn't take anymore refugees. Alright, I'm not even going to debate the the morals or anything like that. He just think, whoever is letting the refugees in is dumb and shouldn't do that. That's surface level thinking to me. How do you do that? There's a boat arriving to the shore, full of refugees, it's not turning around? What do you do?
This is a hard problem, no matter what you think you want the features or use case to be, how do you do it? The logistics are difficult, how do you scale it? What about all the edge cases? What about the cost?
In that sense I think CS can help you learn how to really think through a problem from understanding the full implications and complexities and the challenges. We learn this by trying to model problems and their solutions very formally.
It’s funny you take this example because your point of view is precisely surface thinking too. I bet you don’t have any concrete plan to fund housing, education, healthcare for those people, nor you have one for them to become productive members of the host society. They are dozens of factors that makes irrational to allow any of them, and a lot of countries (Australia, Japan for instance) have in fact a successful policy of allowing only a bunch of them.
When people are coming to your border in large trove, not letting them in is easier said then done. You can't just "not let them in". To keep my analogy going, this requires an algorithm of some sort. First you need to find something that works, and then you need to take into account cost consideration, scaling, etc.
Your example would work as well. Someone who were to say, whoever is stopping them from coming in is stupid. This would also be surface level. What do you do with them once they're in? Housing, education, integration? Does our system have the capacity to handle such load or will it collapse? Just letting them in may not be enough, it could cause problems down the line, what are we doing to prevent those.
The right conclusion to take from my comment is that problem solving is hard, there's a lot of variable at play, a lot of considerations to take in, and it is never as easy as you assume at first. Recognizing this is part of being humble, and I think computer science teaches you that.
Thinking you have the answers because you thought about it for 5 minutes and not realizing you skimmed and hand waved over all the direct and indirect complexities and considerations and are skipping multiple steps of the solution. Thinking that there is an easy solution and then advocating for it strongly when you haven't begone to recognize and understand the complexity of the problem itself. This to me is an indication of a lack of some form of critical thinking. I think computer science can to some extent teach people better about this, by having them practice concrete problem solving exercise on a computer which can assess to the solution working or not. And learning formal problem modeling techniques and validation strategies. It's a useful skill.
But they're not...? GP didn't say he want to take refugees in, they merely said their friend want refuse refugees without specifying how exactly they want to accomplish that.
>I bet you don’t have any concrete plan to fund housing, education...
I don't think this assumption is fair.
I don't know about Japan, but Australia allows in large numbers of immigrants.
This is very naive point of view. Think of how car repair shops bullshit customers (especially what was before some mitigating laws) and then multiply it by Pi or more
There are industries where lying is simply a stable equilibrium.
You need law to keep those businesses going and fair. Otherwise the lemons spoil it for everyone.
I don't know how to raise this issue at work without being insensitive.
No that's not true, that something works is beginner level stuff in many cases. In some cases you're right though, because what has been asked is a super tough problem to crack.
I'll showcase the moments in which the "it has to work" requirement is not enough.
To show this example, I already have to break 2 conventions that are a no no, in my opinion. To other devs: I'm commenting everything (I can't assume someone who works in law to know code, he/she might, he/she might not) and I'm using globals for easier variable reassignment, to ease the example for readability.
Let's get started. The requirement: print 5 to the console of your browser [1].
Open up Chrome Dev Tools (view -> developer -> developer tools -> console)
Type in the following:
five = 1 + 1 + 1 + 1 + 1 //compute 1 + 1 + 1 + 1 + 1 and save it in the computer with the name five
console.log(five) //outputs 5
five = 0 //reset
// loop 5 times, and every time the pc adds 1 to the saved part of the computer named five
for (loopCount = 0; loopCount < 5; loopCount = loopCount + 1) {
five = five + 1
}
console.log(five)
five = 5 //save the number 5 in the computer with the name five
console.log(five) //outputs 5
console.log(5) //also outputs 5
FIVE = 5 //all-caps is a convention for that something is a constant, like a constant number such as 5
console.log(FIVE) //outputs 5 as well, and also probably the way programmers want to see it.
Some of these methods have been really silly and if you catch that during an interview, you won't pass. People can point out that most of these methods happen one way or another, but not when you have a simple requirement such as "output 5". In fact, if that truly is the requirement, then I would go for: console.log(5)
And I'd consider the first 2 entries totally nonsensical (unless I asked it with a funny voice or asked them to do whatever / be creative), the 4th entry slightly questionable but fine and the 5th entry fine.[1] Read the following link to have some context about what the JavaScript console is. Don't worry about not understanding the code or the technical terms. You're not missing anything, as far as context is concerned, I checked. Read it until the first paragraph of "Running JavaScript".
https://developers.google.com/web/tools/chrome-devtools/cons...
You can always screw around with code, redefining code blocks in C would be fun to do.
But I did have situations where FIVE = 5 changed to FIVE = "five" or FIVE = "5" or FIVE = "vijf" (Dutch) or FIVE = "....." (ok, the last one is hypothetical, but maybe you want five points because you tick them off in a for-loop? I've seen something clever-ish like that in a particular fun Fizz Buzz example).
The layer indirection is indeed a classical trade-off that you do or do not want to make.
Regardless of that, your question proves the point I want to make to kbos87.
I think one advantage of computers is that what you produce at the end has to work - and if the code doesn't work or you don't know what you're doing, you're quickly exposed as a fraud. This is not the case in other fields like law, academia, politics, and even the corporate world where the results and methods are more abstract and given to opinion.
Unfortunately much of the world is run by people who excel in the abstract fields rather than the technical ones.