this post was submitted on 17 Feb 2025
410 points (95.2% liked)

Technology

63010 readers
3536 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
410
New Junior Developers Can’t Actually Code. (nmn.gl)
submitted 5 days ago by [email protected] to c/[email protected]
137 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 4 days ago (1 children)

judging them by their approach, not end result, should be fair.

Yup, that's the approach. It's okay if they don't finish, I want to know how they approach the problem. We absolutely adjust our decision based on the role.

If they can extend existing code and design a new system (with minimal new code) and ask the right questions, we can work with them.

[–] [email protected] 1 points 3 days ago (1 children)

I’m just getting started on my third attempt at changing careers from sys-admining over to coding (starting with the Odin project this time). I’m not sure the questions you ask, while interesting, will be covered. Can you point to some resources or subject matter to research to get exposure to these questions? The non coding, coding questions are interesting to me and I’m curious if my experience will help or if it’s something I need to account for while learning.

[–] [email protected] 1 points 3 days ago (1 children)

We stay away from riddles, and instead focus on CS concepts. We'll rephrase to avoid jargon if you don't have a formal education, or it has been a while. Here are a few categories:

  • OOP concepts like SOLID
  • concurrency vs parallelism, approaches for each (generators, threads, async,' etc), and tradeoffs
  • typing (e.g. is a Python strongly or weakly typed? Java? JavaScript?), and practical implications
  • functional programming concepts like closures, partial application, etc
  • SQL knowledge
  • types of tests, and approaches/goals for each

And some practical details like:

  • major implementation details of our stack (Python's GIL, browser features like service workers, etc)
  • git and docker experience
  • build systems and other dev tools

That covers most of it. We don't expect every candidate to know everything, we just want to get an idea of the breadth and depth of their knowledge.

[–] [email protected] 2 points 1 day ago

Love it. So much to look into. Appreciate your time.