How I look at the algorithm nerd on my team who just wrote code that is tightly coupled across 3 layers of the codebase.
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.
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.
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.)
Gotcha addresses the person you’re talking to, gottem is used to address a real or fictional audience, highlighting for them what you did.
Talk to a linguist about how languages evolve.
Gottem.
Everyone interviewing candidates believes they’re Dijkstra.
How BE guys look at you when you use flex-grid instead.
If you hand out a problem and only accept one solution out of multiple valid ones, you’re part of the problem.
When I interview (experienced) devs, I often ask way too generic questions. Something along the lines of “can you explain what a hash is?”, without stating what kind of hash and in what context
The primary goal isn’t really to explain it in detail, but to see if they get confused and ask for clarification. Way too many people just start assuming something, when a task is not defined properly. I need coworkers that push back on bullshit, and not blindly implement whatever runs along their desk, no matter how little sense it makes
If I don’t hear at least one “it depends” during an interview, I don’t have high hopes
I had this with one of my guys. He spent a week working on something and the validation at the end wasn’t jiving.
He started showing me the complex solution and end results and so I said show me how you started and walk me through it.
It was step 1 the origin location of data was out of position.
I said if you start at this origin the rest of the numbers and data will work out.
He replied that the origin wasn’t shown measured from somewhere, so how would we know location.
So I pointed out that the data to origin wasn’t directly spelled out but if you take this measure and subtract this one that is your data origin start.
He said OMG I worked on this for a week trying to get the formulas working. I feel so stupid because you solved it in 1 minute.
I replied its not a question of smart or stupid (because my guy is way beyond me for formulae and programming) its just slowing down and following a process. And if you are confused, ask more questions, rather than just continuing.
Hash? Sure I can hook you up.
Are you sure you’re management material?
(This is a complement)
Two’s complement?
Man, I hope not
Related sidenote: I don’t think I have any form of tism, but something activates when people ask computer science terms where my terrible memory goes “oh yeah I remember the dictionary definition perfectly, punctuations included, let’s recite!”
Also I love the hash exampple. If they start talking about checksums and whatnot you know it’s their hobby to mess with computers lmao.
Fair point, but depending on the interviewee, you might get very different answers and/or follow up questions.
Even if they assume something, it might be just for the sake of the example. If they’re competent, they’ll follow up with another example and so on, depending on how exactly you pose the problem.
If you present it as an abstract question, one possibility is that you get an abstract answer. If you present it like a ticket with no description, you might get prompted to clarify.
If you want something to blindly implement a vague task by making a ton of assumptions, just use AI.
@SkaveRat
in college I had a prof tell us to get into teams, then give us lego sets to assemble.they were in the original boxes but the directions had been removed. I was the only one to go up front and ask for the directions and she gave them to me.
Apparently that was the whole point to the excersize. “ask for the resources you need"
Your candidates aren’t mind readers though. If you want people to ask clarifying questions, you have to ask them things other than comp sci trivia questions.
It could be on a different subject, but it has to be a trick question. If they were prompted to ask more, that would undercut the whole point of the test, since OP wants employees that always ask or question.
I don’t think asking someone a trick question in an interview is a good way to gauge if they’ll push back and ask questions on the job. Also, I think that behavior is more related to the employer creating an environment where employees feel safe doing that, and isn’t really something you can draw out of a candidate during an interview, of all times.
I mean I’d probably go super generic and say something like “it’s a deterministic function which turns a block of data into a usually smaller block of data, usually for comparing equality to the original block of data” which covers most of the uses?
If you ask a generic question, you’re gonna get a broad answer, and if you want to draw clarifying questions, you need to ask a more complex question and provide insufficient information to answer it. Even then, making that question something you can easily look up online, and you either know or you don’t, doesn’t achieve as much as making the question something that you objectively won’t know, and have to learn on the spot, as that shows your ability to learn new things including things you can look up on the Internet.
The point is that in a real software engineering process, specs and requirements are rarely defined precisely from the start, and the programmer should be able to identify the gaps and clarify them. A generic answer doesn’t help as much as a clarifying question.
A common but amateur mistake is to just make assumptions about how something should work and then forge ahead. As a programmer in a company, you are building things for somebody else (your boss, your client), so you need to ask them first.
Sure but as I said, that’s a knowledge question and not an engineering problem to solve. They’re very different and unless you work in software consulting, you’re not gonna get a problem that looks remotely like that from a client.
You actually get them all the time, because the programmer is more deeply knowledgeable about the features they wrote and can identify gaps better.
Boss: “Can we move the widget to the left side of the page?”
Programmer: “Sure but that means when the sidebar opens it will obscure the widget, making it hard to see both at the same time. Do we want that?”
Boss: “Hmm I didn’t consider that. Let me ask the UX team what they think.”
“Can we move the widget to the left side of the page” is not in the same category as “what is a hash” though?
So, to start off, I’m someone who does not typically perform well during interviews because of anxiety (but through some miracle has had no issues with employment), so take this response with whatever bias that brings.
I believe this is bad too. You’re still essentially asking a gotcha question, expecting one phrase in your answer and failing the candidate if you don’t hear that phrase. And, in fact, I disagree with the premise. I think the question is defined quite well in the context of programming, given that someone answers with the possibility that there are many ways to hash something and many uses of hashing.
The hash question is just something from the top of my head. I normally fit it to the situation.
I absolutely take nervousness into account, as I can relate to it.
The thing is, I need to know if the person can push back in some way. it’s a hard thing to do in interviews, but also the first point for me to check how a person reacts
I’ve been bitten too many times, with dev coworkers who don’t give at least a little resistance when vague or stupid tasks show up. Only to notice hours or days later, when something was done completely the wrong way
Sounds like you need to fire the person handing out vague and undefined tasks to everyone 😂
Every task starts out as a vague idea that, at some point, needs to be narrowed down to something specific and actionable.
If you’re at a sufficiently large organization and you get lucky, that happens before it makes it to a developer. For the rest of us, it’s an important skill to be able to take a task, ask clarifying questions, and narrow it down to something actionable.
Listen up every client ever, I’m sorry but I’ll have to let you go.
The only definition of hash that I know is an identifier for an object created from that object’s data. Everything else stems from that central idea. What other types of hash are there?
Yeah, it’s basically that, but it has different uses - two main things I can think of right away are 1) verifying data when downloading large files and 2) cryptography (e.g. when storing credentials). Oh, and hash tables too.
Well, but the question wasn’t “what is a hash used for”, but rather “what is a hash”
Then it’s not all that ambiguous and could be answered with one sentence.
Technically, the question was even easier (yes/no), but I agree with the sentiment
I smoked some on the way in here to make interviewing more tolerable
Harold Shipman meme.
software engineers met the table¹ in web design and never looked back. does a table “mean” tfoot and all (arranged at top)? thead, that sorts(, by server link without javascript)? a “table” in the web means all sorts of sorty things and offset things, and paginated things, by navigable server links. and the two tables nested for layout, oy vey! so many ways with all that engineering the web fell to the broken manual✨️🤷🏾♂️✨️
¹ (for layout) https://www.w3.org/TR/web-sustainability-guidelines/#progressive-enhancement
(╯°□°）╯︵ ┻━┻
┬─┬ ノ( ゜-゜ノ)
Flipped table, sorted table.
B.S.
Dijkstra would have loved the lookup table solution.
He HATED complexity.
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.
Depends on the scale of the project. Some apps you would get a promotion if you could get them to (reliably) run on just 50k a day.
I am torn between this and “AAA videogames should be optimized more.”
disappointing. no such algorithm.
yeah I looked it up
Good news, you can invent it!
Red thinks you’re making up words
They’re all real words, but not in an order that makes sense. And I’m not sure what algorithms there are by a Ross or Maxwell.
This wholly depends on where this code is running. If it’s running on the server, you want the best algorithm for most cases, to try to minimize work and power consumption, and maximize capacity. If it’s running on the client, just use whatever.
If it’s running on the client, just use whatever.
Because who cares if it’s the user that has to buy more RAM or gets terrible battery life, that’s not our problem. /s
This is why we can’t have nice things.
I agree. I guess it wasn’t obvious that I was being sarcastic.
THIS IS WHY SOFTWARE DOWNLOADS ARE 75 GB WHEN 20 YEARS AGO THEY WERE ONLY 200 MB.
I would say Computer Scientist in place of software engineer.
Yeah, software engineers are the sanitation engineers of programming. Source: am one
All these job titles don’t really have a formal definition. Software engineer = programmer = software developer. Computer scientist sure does sound fancy though. There’s no committee that will say “actually you’re doing too much math to be a developer sorry.” We all do the code-y thing. Businesses seem to pick one at random based on seniority. I just call myself whatever my most recent job title was.
Your industry will affect your specialisation and skills much more than anything else.
- Software Engineer (Maths)
I don’t even go that’s far. I “work in IT”. Enough for 99% of social interactions / official forms.
You’re taking my comment a little too seriously. I just know that what I do is essentially playing with other people’s legos, to make a CRUD app, to show my industry’s equivalent of cat pictures. I leave the heavy math and theory to the real computer scientists.
sounds reasonable to me! why reinvent the wheel right?
I just use wheels that will others have built and call it my car 😎
I couldn’t tell how serious you were being, sorry. Some people get weird about this specific topic and gatekeep the labels lol
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.
I feel like it would CS professors and not software engineers who would give that look.
Well, it is Dijkstra in the picture.
