Channel for Software Creators and Product Development Enthusiasts. Sharing the things which I believe will help people in creating high quality and functional software.
Please follow me on my other social media channels
yeah, when you work in a space where microseconds matter, thats when you'll be glad you can write C or in line assembly...if you don't need that then stick to modern c++ or use c#
Great video, that's what I always say, C/C++ gave us great powers, but aren's not for incompetent programmers, and new languages accept incompetent programmers in exchange of magical things that corrects their errors, and that's why programmers are becoming more and more incompetent everyday, they got used to commit errors all the time and expect the language is going to solve them for them. C++ is the best language ever, together with C, and languages aren't unsafe, programmers are.
Thanks for sharing your comment, I agree with the last line... Also, no matter which language you use, you need better and competent programmers.. without that some or other problem will be there.
I hear what you're saying. However, if people keep falling off a cliff at the same spot it's probably a good idea to install safety railing there. It doesn't really matter if the problem is with the cliff or with the people. The fact is that people keep falling and we have tools to make it happen less.
Hello, Thanks for sharing your thoughts.. Your analogy is interesting and valid. However, even though safety railing are installed, I don't think that we will allow kids to go there unattended and that's the point. We need people with sense of responsibility to honour the responsibility. If we keep on creating safety railing after safety railings for each and every situation, the programming world will turn into prison without any innovation and creativity. Not saying people should not use memory safe language, if they are comfortable they should, but unless we address the root cause, we can't fix it.
@@Cognitive-Programmer Education, experience, responsibility, and thoughtfulness is definitely part of it. Companies, especially those running around on canyons / in kernel space, should take quality very seriously. I just think we should do a bit of both! The safety railing we have today is pretty good at not getting in our way. For example, the null safety in Python's type hints doesn't cause issues when we do need a None. There's also Any for when we really need it. Good railing have escape hatches, and most of the ones I've used do! I also feel like the concept of "my freedom ends where yours begin" applies. I should be free to write Python without type hints should I wish to. However, just like air crafts have strict standards, I think it would be fair to (for example) require that all Python code written for medical devices is type annotated. Thank you for your response and thoughtful content!
Hello sir, I am a content writer specializing in programming channels, like Cold Mine, which are concise yet impactful. With a strong coding background, I can effectively create engaging content for your team. I also specialize in creating short videos, a crucial element for channel growth. I believe I can contribute significantly to enhancing your channel's content diversity. Thank you for considering my application.
Surprised c++ is even mentioned. That's like blaming the universe for all your problems. It is interesting to see their public GitHub (even though I imagine the actual bug was in their closed source) as you can smell funkiness arising from the this feature (CrowdStrike/falcon-operator/pull/560/files) and similar changes before. The worrying point is that vested interest and politics shrouded between CrowdStrike and MicroSoft has caused a junior level bug to rip through production systems all the while the media/industry argue over the devs and the tools they use. Did nobody stop and wonder if the rotten tree they stem from isn't all it's cracked up to be?
When a field is just starting, you don't have to conform to many guidelines, there is lots of opportunity. If you want the same freedom to create, explore something that's in its infancy.
Hello Thanks for sharing your thoughts, kind of agree to the infancy aspect of it.. but rigid rules are preventing the same as nobody wants to look beyond it
What if you use Optional<T*> to pass in a parameter to a function? and the intention is T* points to nullptr which will be later "filled in" by the function. Checking nullopt on T* is probably undefined behavior ?
Thanks for this video! I used to do first line technical support for a software house, and the competence of programmers is not the only factor - as you rightly say, the bar must always be kept as high as possible. Very occasionally, one of the programmers at my old software house was careless, and simply assumed that the code he wrote would work flawlessly, and he'd release it without testing, and occasionally it would wreck the system. I'd love to know how the defective Crowdstrike update was created and then released - then, some programmers and testers might also become famous!
Hello Thanks for commenting on the video and sharing your thoughts. I really appreciate the same. Also, I am not sure if companies would like to make famous the programmers and testers as they will blame it to process or something else.. Don't think people would like to handle that mess
You saved me! Was using CELERY_QUEUES(kombu.QUEUE(...), ...) and CELERY_ROUTES= {...} but all messages went in default queue "Celery" without creating my queue, that I declared in CELERY_QUEUES. Now all is working perfect!
hi ,i am interested to learn GO-lan. your way of explanation and examples are too gud. can i get any kind of notes or some more information about Go-lan.Please reply.
Thank you sir, had my head breaking how to initailize attributes from different classes without knowing abt **kwargs....finally found the solution in your video
If you don't know for sure about bugs, that just means you are not God (and have not even spoken to God). There is God and even other perfect beings who can know things for sure. Why don't you accept a guru? Also, there is a certain size, below which we can completely comprehend some software and prove it to be bug-free.
I had to replay the video to grasp the info. First play only went on watching the background. It's so beautiful. I wish we Indians learn to maintain our own surroundings well in India as well.
Thank you for this video! It helped me understand the reasoning behind using ProcessPoolExecutor on CPU intensive tasks. Very thorough and clear explanation!
thank you for a very nice tutorial. real case challenges - interface functions will not be virtual always, my component may not always have references.
the part where you explained about how celery used all the cores of the machine by default to support multiprocessing is very well done. thank you sir.
