this post was submitted on 22 Feb 2024
140 points (100.0% liked)

Technology

37708 readers
405 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

That graphic sums up my entire educational experience. https://archive.is/hvZ5q

you are viewing a single comment's thread
view the rest of the comments
[–] reric88@beehaw.org 1 points 8 months ago (1 children)

You're exactly right. I didn't read the article yet, but you can build a to do list app in a handful of minutes if you know your way around. I'm still green as a coder, but have been through dozens of tutorials, one of which was a simple to do list in JavaScript. I managed to complete it in about an hour. Seeing that someone thinks it takes weeks to do, that makes me wonder about them.

[–] jarfil@beehaw.org 23 points 8 months ago* (last edited 8 months ago) (1 children)

you can build a to do list app in a handful of minutes if you know your way around

No you can't. You're mistaking a "hastily thrown together prototype", for an "actual app" with all its requirements, tests, multiple target support, hundreds of tiny features, QA for all that, then deployment, and ongoing support.

Depending on where on the scale between "prototype" and "final product" you look at, it's going to be anywhere from less than an hour, to a full team working for years.

Now, arguably, showing whether you know the difference, can be the real test.

[–] bedrooms@kbin.social 5 points 8 months ago (1 children)

I mean, if you argue that way during the interview I'd pass... Nobody thinks you're asked to do all that in a one-day interview.

[–] Car@lemmy.dbzer0.com 4 points 8 months ago* (last edited 8 months ago)

Why should the interviewee assume that?

This could very well be a test to see if the applicant has an idea of how a project scales or how they need to interact with other departments or track down compliance information. It could also test the applicant's ability to provide a sanity check to a boss's idea before they pitch something that the team can't actually do