4 ms·
That's a bit odd. Are they unaware of the last 30 years of computer history? Even as someone with a background in mechanical engineering the degree of complexi
by MichaelZuo 4y ago
That's a bit odd. Are they unaware of the last 30 years of computer history?
Even as someone with a background in mechanical engineering the degree of complexity behind some software products, such as Windows, is really impressive.
- Tempest1981 4y ago(Probably a rhetorical question, but...) It's hard to overcome preconceived notions. As we know from politics, emotions are much stronger than logic. You can't simply say, "be logical!" or "change your view".
- sho_hn 4y agoI suspect "hardware is real engineering" is really just "hardware engineering is where you can find prestigious employment in this country". It used to be quite similar in South Korea until the more recent rise of domestic software giants like Naver and Kakao Corp. In a lot of the East Asian countries, there is a large gap in desirability between the large, established employers and smaller companies due to outrageous differences in pay grade, benefits and job stability. So new business has a tougher time making it to escape velocity and offering significant numbers of jobs.
- smahs 4y ago+1. I have vague memories of my time at a Japanese automation vendor out of the uni. I had quit out of frustration that the software was super buggy, there was no one to help except just a couple of people in Japan who knew the software but would not reply to emails. I also remember feeling neglected as folks working on the hardware or on customer projects were paid higher than me. A recent experience at a neobanking startup from SE Asia reaffirms the point. Despite the product built around an API-only model, the firm was operations heavy when it came to decision making and investing in people, as it was believed to be the core company strength (for a variety of reasons including the institutional bureaucracy, corruption in these markets, etc.) TL;DR people work where the money flows. Companies get what they pay for. And the investors pay for what they think is the strength or is likely to sell at inflated valuations.
- 0x445442 4y agoI too have a background in Mechanical Engineering and while many software products are complex I wouldn’t categorize all of them as engineering projects in the historical sense of the word. That’s not to say there are not quality software products that satisfy real businesses requirements. But it is to say that a lot of software projects would be WAY too expensive if they were engineered the way a passenger jet or a skyscraper was engineered. The software development field is quite new compared to the other engineering disciplines and many, many decisions are made on gut feel, intuition or out right personal preference. Alan Kay has some very good talks on this specific subject, referring to the current state of our field as a Cargo Cult. However, I would also say firmware would be the least expensive to engineer because the requirements for that type of software are better known and more rigid.
- sho_hn 4y agoAutomotive and other mixed-criticality systems is where these two worlds butt together and have a lot to learn from each other. Mech eng processes on one side, ASIL-style safety requirements in the middle, and someone wishing to pour a bucket load of Android apps into the same computer from the other end.
- derefr 4y agoAre they ever really "the same computer"? I don't think that's true even in entirely software-mediated-control vehicles like Teslas. The discipline of robotics (which is really what you're talking about here — cars are just very manually-micromanaged robots these days) is all about subsumptive distributed architectures: e.g. the wheels in an electric car don't need a control signal to tell them to brake if they're skidding; they have a local connection to a skid sensor that allows them to brake by themselves, and they instead need a control signal to stop braking in such a situation. This is why, in anything from planes to trains to cars, you see the words "auxiliary" or "accessory" used to describe infotainment displays et al — the larger systems are architected such that even an electrical fault (e.g. dead short) in the "accessory" (non-critical) systems can't impact QoS for the "main" (critical) systems. I really can't imagine a world where they've got engineers building the car that understand that, but who are willing to let Android apps run on the same CPU that's operating the car. They'd very clearly insist for separate chips; ideally, separate logic boards, connected only by opto-isolated signals and clear fault-tolerant wire protocols.
- sysadmindotfail 4y agoI have family members who consider themselves "real engineers" compared to me, an SWE. They have backgrounds in Mechanical and other "traditional" engineering fields. About once a quarter I am subject to conversations where they remark condescendingly about how flabbergasted they are at SWE salaries. I stopped engaging beyond "Mmm if you're interested you should learn more about the field". This interaction is beyond grating and is detrimental to our relationships.
- Tempest1981 4y agoYep, sounds like one of those "agree to disagree" topics. Or diffuse using mild humor, like you have tried. Or redirect, and blame supply and demand, or social media.
- ndriscoll 4y ago> perfection is finally attained not when there is no longer anything to add, but when there is no longer anything to take away In traditional engineering, there's at least a BOM and manufacturing processes that create pressure to keep things simpler. If physical items were engineered like software, you'd have people bolting a keyboard onto the monitor chassis they're designing because they needed an 'on' button, and keyboards have buttons. Obviously they'd then also have to add in an always-on raspberry pi to plug the USB keyboard into and emit a GPIO signal when the button is pressed. You'd get a lot more complexity, but for most of it, "impressive" would be the wrong word.
- m4rtink 4y agoThe IBM S390 HMC (Hardware Management Console) is basically a thinkpad bolted on the massive S390 case.
- MichaelZuo 4y agoThat's a pretty insightful analogy! Bolting an entire keyboard on to a monitor to add a single extra button... Thankfully the cost of adding physical atoms prevents such outrageously dumb ideas.
- robinsonb5 4y agoI think part of it is that hardware is tangible, software isn't, so for some reason people resent being expected to pay for software. Building software thus has less legitimacy in some peoples' minds. I see this in the retro computing scene: people will quite happily fork over large amounts of cash to have an old bit of kit repaired, or buy a newly-developed expansion for old hardware, but those same people - even the people doing the repairs and building the new hardware - can be incredibly hostile to the idea of someone asking for money in return for new software for those old platforms.