DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations
Securing Your Software Supply Chain with JFrog and Azure
Register Today

Trending

  • Understanding Data Compaction in 3 Minutes
  • Core Knowledge-Based Learning: Tips for Programmers To Stay Up-To-Date With Technology and Learn Faster
  • 5 Common Data Structures and Algorithms Used in Machine Learning
  • Opportunities for Growth: Continuous Delivery and Continuous Deployment for Testers

Trending

  • Understanding Data Compaction in 3 Minutes
  • Core Knowledge-Based Learning: Tips for Programmers To Stay Up-To-Date With Technology and Learn Faster
  • 5 Common Data Structures and Algorithms Used in Machine Learning
  • Opportunities for Growth: Continuous Delivery and Continuous Deployment for Testers
  1. DZone
  2. Culture and Methodologies
  3. Career Development
  4. What Facts Should Be Resident in a Developer’s Head?

What Facts Should Be Resident in a Developer’s Head?

How much implementation details should a developer remember when going for an interview? Should you remember whole algorithms by heart?

Oren Eini user avatar by
Oren Eini
·
Feb. 07, 17 · Opinion
Like (3)
Save
Tweet
Share
3.80K Views

Join the DZone community and get the full member experience.

Join For Free

I just finished reading this reddit thread about a guy that cheated to get a job (the original post doesn’t really shed a good light on anyone there) and the comments related to that.

That got me thinking about our own interview process and what kind of things I expect people to have in their head, for interviews, but also in general. In particular, this comment:

Honestly, I wouldn't hire someone who couldn't code a search or sort algorithm on a whiteboard and tell me how e5fficient or inefficient it is.

Another example I heard of in a conference is literally examining people on Knuth. To the point where you didn’t know chapter and verse for Oscillating Sort (literally, in what chapter is that covered), for example, you are obviously worthless and there is no point in continuing in the interview process.

For myself, I don’t think that I bother keeping any actual details about algorithms in my head. Much more important is to know about the algorithms and to be able to have just enough information to recognize that it might be a viable option for my use case and then read up on the details.

In interviews, and in their work, I would expect people to know about big O complexity and be able to tell what kind of complexity a specific piece of code had, as well as whatever this was good or not.

As for implementing a sorting algorithm, I remember some of the details on how quicksort works - but actually writing that from scratch? There are far too many details for this to actually be a viable option.

For example: 

  • Lomuto or Hoare partitioning?

  • What about the choice of pivot?

  • How about parallelism?

  • How do you handle repeated elements?

I just pulled those from the Wikipedia page, mostly because I remembered this post about how to answer such interview questions.

Implementation details shouldn’t matter (beyond understanding costs & complexities), so they shouldn’t take up valuable mental space in your head - that is why we can search for that. The important thing is that you know that you need to look up additional information, as well as know how to do so.

Interview (journalism) code style Algorithm Use case Sort (Unix) POST (HTTP) career

Published at DZone with permission of Oren Eini, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Trending

  • Understanding Data Compaction in 3 Minutes
  • Core Knowledge-Based Learning: Tips for Programmers To Stay Up-To-Date With Technology and Learn Faster
  • 5 Common Data Structures and Algorithms Used in Machine Learning
  • Opportunities for Growth: Continuous Delivery and Continuous Deployment for Testers

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com

Let's be friends: