News for hackers. Stuff that matters.

aaustin

Re:Ask HN: Who is hiring? (September 2016) on Thursday September 01, 2016 @12:20PM (#12406558)
Senior Node.js Developer | Interactive Intelligence | Durham, NC | ONSITE

Interactive Intelligence (NYSE:ININ) is hiring a senior Node.js developer to work on our cloud-based chat service.

We make software to manage call centers. Our chat service is just a small piece of the PureCloud Collaborate product. You can see read more about the overall product here: https://www.inin.com/unified-collaboration

The role on my team is specifically for developing a highly available service built entirely on AWS and use technologies like Socket.io, DynamoDB, XMPP, Redis, & Kafka. The team is currently 4 developers and two developers focused on integration testing.

The interview process is straight forward: 1) phone screen with team lead 2) small coding exercise 3) half day in person interview.

You can email me your resumes directly at [email protected] or read the full listing here: https://www.inin.com/careers/job-listing?p=job%2FovuJ2fwu

Re:Ask HN: Best practices for software development? on Sunday August 28, 2016 @11:51PM (#12379900)
Read "Code Complete". Read "Mythical Man Month." Maybe read "The Pragmatic Programmer." If you're interested in learning more about testing, read "How Google Test Software." If you work on a lot of other people's code, read "Working Effectively with Legacy Code"

Good unit tests are absolutely crucial to any kind of future refactoring effort. They are helpful at finding regressions and give you some confidence that you do not break the paths that are tested. If you work in a team larger than one, code reviews are a must. Code reviews allow both participating parties the opportunity to learn, improve the overall codebase, and catch bugs. I also think writing code comments and documentation is absolutely important. Mostly so the "next guy" understands why the code is doing what it is doing. Most of the time the "next guy" ends up being you.