Reply to thread

Message: <blockquote data-quote="kingsultan111" data-source="post: 27090641" data-attributes="member: 575252">Dude, I'm a businessman and not Indrajith Gamage. My net worth is well above 25 million USD. I could have been billionaire. I rejected most opportunities due to ethical issues. Nonsense and pure BS. You an engineer if you engineer and build a solution.  You always can go back to chicken-egg drama and learn what's before X abstraction, but it's pointless. World is build on abstractions <img src="/styles/default/xenforo/smilies/default/D.gif"  class="smilie" loading="lazy" alt=":D" title="Big grin    :D" data-shortname=":D" /> He has received some good comments,"Tell me, how does the semiconductors in your process make a CPU? . What are the tempurature and time constraints to form semiconductor ignots and how are they maintainted to produce consistent substrates? How does the Electric grid maintain phase syncronization across regional networks? How do ISPs maintain BGP rounting between their networks? All these and more are "part of the stack". But you don't need to know about all this to write a program. Now it could help to know them but not required. Nor are the things you mention. It depends what they are building. The need to know and be expert in some layer whch may or may not be related to the tasks they need to occumplish. Of course its better that they know deeper than their immediate layers. And sometimes its critical. But its not usually along the dimensions you make out.""A fully biased view far from reality.If a react developer is not good if they don’t know C!Then a C developer is no good if they don’t know assembly?Then a compiler guy is no good if they don’t know how chips are designed?A chip designer is useless if they don’t know how silica gets extracted?Or May be your react developer needs to know the highest quality silica while developing an app?May be the performance will be the best by starting with silica?""But when it comes to the ugly reallity "The End User/ Customer" always results oriented. Let me give you one calssic example. Back in 2013 when we do our MSc, I was the person who got the highest results for the Project which was an implimentation. During the VIVA , I had to explain upto the LDR resistance level and how it casued to create a swith on connected trasnsistor level. (They went to sensor level of my IOT Project). But you did an API Manager and I belive you got many git pulls on you project untill now.I don't think you are also cares about the quality of ABC and Fabric under TarMac road whenever you ride your car. And even I don't know how it works as far as my car is working and running and I do timely service as perventive maintanance.Our new generation is like drivers who dirves their vehicles to their destinations. What we need to ensure is they are well trained on safe driving and aware about the best practices to prevent un-wanted breakdowns. And let vendors/nerds (like you and me) to take care about the basics.There is no point of asking how HTTP Protocol works and how it is being handled from a web developer machan. We know it just becase of we had to setup it manually back then.""Why it sounds to me like you're coming up with trick questions to break people down in job interviews? You likely are hiring node.js developer to implement web APIs, work with other web APIs and databases, likely in your codebase you don't have single use for the file system API, and yet you're asking how node.js implements multithreaded file IO on legacy operating systems where your code is likely never gonna be running.""While this statement is true, I think your introductory examples are too far off track.An engine designer needs to know how engines work. An assembly line worker needs to know how to do their part on the assembly line. If the engine designer keeps designing 4-cyclinder engines because that's what others do (despite understanding deeply how they work) then that's a cargo cult.Many people understand what Microservices are (a very complex distributed approach), but still build small simple projects that way and go over budget. That's cargo cult. They understand everything deeply. In fact that can be the problem, being blinded by knowledge the designer thinks that their instincts are perfect.For Machine Learning, if you are designing a new Neural Net, you need to do ML science. You need to understand the layering, the inputs and the outputs. If you are building a face recognition system for a baby monitor, you only need TensorFlow - to "apply" the correct solution.A programmer at Oracle needs to understand B-Trees, and the tradeoffs with Hash indexing, to then invent a new capability that might be ideal for highly sequential timeseries data. The software engineer needs to choose the right index type.The cargo cult engineer chooses MongoDB because it's the flavor of the month. A competent engineer chooses React over VueJS, because their team has experience with React, and after a prototype VueJS project, the engineer understands there's no big improvement gain that warrants a shift, and in fact, they realise their tooling will be worthless and they'll have a smaller ecosystem of third-party components.Cargo Cult programming is a big problem globally. If we all identify the worst of it together, and talk about the hollow benefits of various overhyped technology, the industry can be improved for the better."The guy is an elitist who hate younger people getting into industry and he fear job security.</blockquote>

Verification: Haya warak paha keeyada? (haya wadi kireema paha)

Top Bottom