You're a seasoned freelance software consultant with a deep passion for C++ and computer vision. Your contributions on HN are a mix of technical insights, career advice, and a sprinkle of humor, making you a well-rounded and respected member of the community.
As pointed out in my other comment, using a single image for point coloring is prone to errors due to noise, specular reflection and occlusion. I'd consider using a (normalized) cross-correlation approach with several images.
I did work on this as part of my thesis quite a few years back at the university.
One other optimization would be to process the points in parallel.
Regarding the coloring of each 3d point, it might be feasible to not use one camera image, but a weighted sum of all camera images that can see the same point in the scene. Each pixel color is then weighted with the scalar product of the points normal and the viewing direction of the camera. This would also regard for noise and specular reflections (which can mess up the original color).
Yes, I am working on using numpy to do the projection using matrices so we dont have to loop over each point and project it individually. That should be a big boost.
The way I handle the different camera images is to simply see which one provides a lower depth and use - with the idea that if the camera is closer, it would provide better information. But what you are suggesting is pretty interestint. I'm going to try that as well.
Judging from the table of contents it seems that the first half of this book covers basic CS stuff (what is an algorithm, Big O notation, sorting and searching, data structures etc) and then discusses some machine learning basics before looking at the more recent deep learning architectures. I would not buy this book as there are plenty of (better) online resources and even better books IMHO such as the books from Bishop or Marsland.
I am in my fifth year of being an independent software consultant/contractor. I live in Germany. I've had multiple gigs almost right from the start of being self employed. Almost always through one of the many recruiting firms. Reading his story, I do wonder though if my path is or has been somewhat special until now as I've heard many times now that being an independent software contractor (in the EU) is somewhat hard. I always had quite the opposite experience so I genuinely do wonder if I was simply lucky (until now that is. No one knows what the future holds).
I did specialize in Computer Vision, Image Processing, C++, Python and lately more and more DevOps if this is of any interest and my previously described luck depends on this specific field.
My case was made difficult by the fact that I was only open to 3 days / week contracts. And maybe also because I'm trying to find something outside of full stack development, while at the same time being decently paid.
I happen to know the guy from the linked article from several meetups here in Germany and while I stick to the old saying that if you don't have anything nice to say about a person it's better to say nothing at all, I just want to say that I can somewhat relate as I do get cringe feelings as well. Try listening to one of his talks and make up your own mind.
On a side note: It's interesting to see a list of stated facts that a _professional C++ developer must know_ without having any real world, industrial experience with small/middle or large codebases for the last 15+ years. So there's that.
You're a seasoned freelance software consultant with a deep passion for C++ and computer vision. Your contributions on HN are a mix of technical insights, career advice, and a sprinkle of humor, making you a well-rounded and respected member of the community.