debh
Re:C++ exception handling mistakes and how to avoid them
on Wednesday August 03, 2016 @08:17PM (#12222500)
Thanks - I'll check it out. I'm thinking to compile a list of good resources and add it to the current article.
C++ exception handling mistakes and how to avoid them
How to Connect to Azure Compute Emulator Running on a Remote Computer
Re:The Quest for a Perfect C++ Interview Question
on Sunday June 05, 2016 @03:42PM (#11842727)
What you say is true - but the idea is not to use this in production code. It's just a means of testing some fundamental C++ concepts which I outlined in the post.
The Quest for a Perfect C++ Interview Question
Re:The worst programming interview question I've even seen
on Monday May 30, 2016 @06:54PM (#11803668)
Nice one :)
Re:The worst programming interview question I've even seen
on Monday May 30, 2016 @06:42PM (#11803636)
Kindof - if you're a startup and hiring for a position that requires knowledge of java, then IMHO it's a fair question. Most startups don't have the resources to train employees for 6 months.
But yes - the testing material in most certifications is not a good indicator of problem solving abilities and I wouldn't make any hiring decision based on them.
Re:The worst programming interview question I've even seen
on Monday May 30, 2016 @06:28PM (#11803583)
In my experience, pure mathematical knowledge just by itself seldom translates into good coding skills. This is after I've TAed Maths, CS and Physics courses for almost 4 years.
Typically we have 45 minutes to interview someone and asking a question where one has to derive a mathematical formula using induction/ calculus is not well served to gauge their programming abilities.
But I totally agree with you on your last point - just because someone is not a good hire now, does not mean they never will be - that's why even if you don't crack an interview, you can reapply in 6 months time.
The worst programming interview question I've even seen
Re:Top C++ header file mistakes and how to fix them
on Saturday May 21, 2016 @09:01PM (#11746972)
Yes - it's mostly applicable when you're creating APIs and developer solutions. But even in case of internal tools/ exes, you might need to share functionality with a internal partner team and it's helpful if they don't have to read code they don't need to use.
Top C++ header file mistakes and how to fix them
Re:Mistakes to avoid with C++ 11 smart pointers
on Sunday May 15, 2016 @06:49PM (#11703162)
Thanks for reporting this. Someone else noticed it on a nexus tablet as well. I'm looking into getting this fixed.
Re:Mistakes to avoid with C++ 11 smart pointers
on Sunday May 15, 2016 @06:36PM (#11703116)
Good points ! I ran into some difficulty translating the boost::shared_ptrs to C++ 11 standard shared_ptrs a while back while adopting some open source tech for xbox.
Also you're spot on about people touting the smart pointers as a silver bullet for all memory issues leading to an overuse of these otherwise fantastic tools.
Re:Mistakes to avoid with C++ 11 smart pointers
on Sunday May 15, 2016 @06:31PM (#11703097)
Yep - thanks for calling this out. I should have put out a version that's safe in multithreaded environment. I've updated the article to reflect this.
Re:Mistakes to avoid with C++ 11 smart pointers
on Saturday May 14, 2016 @10:02PM (#11699018)
I think for self referencial data structures, passing them by a const& unique_ptr is a reasonable way to do it.
Thanks, Deb.