News for hackers. Stuff that matters.
Re:Why I'm usually unnerved when modern SSDs die on us by pkaye on Tuesday December 11, 2018 @12:56PM (#18657184)
I worked on SSD firmware for quite a long time and here is my perspective.

Early flash used to fairly reliable with almost minimal error correction. However with increasing density, smaller processes and multi level cells, it has gone progressively less reliable and slower. Here are some of the things that we need to worry about: https://www.flashmemorysummit.com/English/Collaterals/Procee...

To compensate for all these deficiencies, the SSD architecture and hence the entire FTL becomes very complicated because any part of it can become damaged at any time. We always have to have backup algorithms to recovery from any scenario. Its difficult to build algorithms that can recovery from arbitrary failures in a reasonable time. I cannot have a drive sitting around for 20 minutes trying to fsck itself.

Another problem is that the job while rewarding is not very lucrative. The chance of a multi million dollar payoff for an employee is low. I have a higher chance working on a web connected gadget to become a millionaire. So that means it is really hard to recruit those who are top notch programmers who known how to figure out the algorithms, write the code, debug the hardware. Most new grads these days are interested in python, javascript and machine learning.

Re:Why I'm usually unnerved when modern SSDs die on us by Matthias247 on Tuesday December 11, 2018 @01:39PM (#18657604)
> Another problem is that the job while rewarding is not very lucrative. The chance of a multi million dollar payoff for an employee is low. I have a higher chance working on a web connected gadget to become a millionaire. So that means it is really hard to recruit those who are top notch programmers who known how to figure out the algorithms, write the code, debug the hardware. Most new grads these days are interested in python, javascript and machine learning.

That seems unfortunately true for most low-level infrastructure software. I am very good at those things, and have a medium amount of experience of building web software. Yet I can find a lot more jobs on the latter domain, and they probably won't pay worse (most likely even better).

Besides pay the non-rewarding things in this domain are mostly that the high complexity is often not properly understood by management, rewarded or taken into account in planning. Which then leads to suboptimal products that have been delivered under time pressure.

Re:Why I'm usually unnerved when modern SSDs die on us by agumonkey on Tuesday December 11, 2018 @02:19PM (#18657970)
I don't know how the system could / should interface with stupid trends sucking resources (high complexity projects, smart individuals, long term).
Re:Why I'm usually unnerved when modern SSDs die on us by snazz on Tuesday December 11, 2018 @06:25PM (#18659952)
Infrastructure almost always becomes a commodity, or at least moves behind the scenes. For it to be lucrative, interesting technical position, you have to have a large-scale enterprise (like Google), serving millions of people, and you have to promote it as a worthwhile career path (also done at Google as the SRE position).
Re:Why I'm usually unnerved when modern SSDs die on us by dgzl on Tuesday December 11, 2018 @02:46PM (#18658213)
The business would have to offer employees something lucrative they otherwise wouldn't earn. I'm not sure what that would be however.
Re:Why I'm usually unnerved when modern SSDs die on us by the8472 on Tuesday December 11, 2018 @05:23PM (#18659555)
open source all the things, get to collaborate with smart people all over the world.
Re:Why I'm usually unnerved when modern SSDs die on us by ams6110 on Tuesday December 11, 2018 @03:02PM (#18658376)
Let's be honest, the chance of a multi-million dollar payoff for an employee is low regardless. Young entry-level devs are optimistic and also vulnerable to believing a line of bullshit on how much their options might be worth some day. I do agree it is a "higher" chance in web/mobile technology, sort of like how your chance of winning the lottery is "higher" if you buy 10 tickets instead of 1.
Re:Why I'm usually unnerved when modern SSDs die on us by woolvalley on Tuesday December 11, 2018 @04:30PM (#18659092)
You still get paid a lot more working at google working on generic backend protobuf shuffling than you will working on SSD firmware at a hardware company or intel's C++ compiler.
Re:Why I'm usually unnerved when modern SSDs die on us by monocasa on Tuesday December 11, 2018 @06:39PM (#18660047)
For those doubting you, the going rate for embedded engineers out here in the Denver area where a lot of these SSD controllers are designed is ~$90k. Embedded engineers get peanuts for some reason.
Re:Why I'm usually unnerved when modern SSDs die on us by bacon_waffle on Tuesday December 11, 2018 @07:24PM (#18660298)
I've noticed the same thing, and suspect that it's related to the way that higher level software scales compared to embedded.

If a line of code is written to run in a customer's browser, then that line of code may be deployed to millions, maybe billions, of customers. But, if an equivalent line of code goes in to firmware for some widget, then you're doing pretty good to get that line in to a million widgets at all, and it's going to take a lot longer too.

Re:Why I'm usually unnerved when modern SSDs die on us by londons_explore on Tuesday December 11, 2018 @09:23PM (#18660882)
Write an embedded bootloader and there's a good chance your code will be used by a billion people within a few years of writing it.

You'll still get paid peanuts for doing it.

Re:Why I'm usually unnerved when modern SSDs die on us by ajmurmann on Tuesday December 11, 2018 @09:42PM (#18660967)
I think it's a issue related to the visibility of the quality of the work. If the product is even 20% more reliable (whatever that exactly means), hardly anyone will actually notice. Nobody notices the absence of an error. That's although it probably took a huge effort to achieve this. Making a user flow just a little bit nicer is very visible and gets attention.

I always felt that ISPs suffer a similar problem. Nobody cares if everything works as expected, but we'll get upset of it doesn't. However, there is hardly anything outside of what we take for granted they can do that we will actively appreciate. What could a embedded engineer working on SSDs do that will be noticed, appreciated and not taking for granted by customers?

Re:Why I'm usually unnerved when modern SSDs die on us by bacon_waffle on Tuesday December 11, 2018 @11:18PM (#18661361)
Yes, and that's just it.

If a software product takes off, that can happen incredibly quickly, and the new product is primarily composed of code. If a hardware product takes off, the change can't be nearly as fast as it's bound by manufacturing, and the code is just one component in each thing.

I happen to be working on firmware for a VOIP phone today - we'll end up making N million of these things, over some number of years. If I were working on an Android app with similar functionality, that app could conceivably go to N million people tomorrow, or 10N, or 100N...

Anyway, I don't think I have a particularly clear or concise (or even correct) argument here, but it's the only way I've been able to rationalise what we've observed.

Re:Why I'm usually unnerved when modern SSDs die on us by lake99 on Tuesday December 11, 2018 @09:28PM (#18660904)
I agree with your comment about scaling, but I think you have underestimated the firmware deployment figures.

Ultimately, whatever we write that goes into firmware is hidden from the customer. The customer pays a price per unit, and other hardware vendors are competing against your product. This competition keeps the overall cost low. Except at the very top level like Intel or Samsung, semiconductor manufacturers seem to be fighting one financial crisis after another.

Competition does not work like that in Software. The products (even in the same domain) are all too different from each other, so though they may be competitors, they are rarely in direct competition.

Re:Why I'm usually unnerved when modern SSDs die on us by nickpsecurity on Tuesday December 11, 2018 @10:59PM (#18661288)
Nah, it's just management incentives with nothing on liability side for the product countering that. They keep labor costs low. The company still makes piles of money off the product. There's no liability for devices, esp cheap, that fail randomly after such and such period of time. So, no negative outcomes for keeping labor cost down for firmware. So, they keep doing it.

That simple.

Re:Why I'm usually unnerved when modern SSDs die on us by kabdib on Tuesday December 11, 2018 @10:03PM (#18661047)
In Xbox, many of the firmware hires the hardware folks made seemed to be payed poorly. Also, there were tons of contractors, and not much institutional knowledge was retained. (At one point they had to pay a consulting firm to decompile the firmware for a controller because they had lost the source code).

"Why do we need source control? It's all there, right on my laptop. Source Depot is just a bunch of trouble." [rough quote from memory, maybe conflated from a couple of engineers]. I'm happy to report that things got better.

On the software side of Xbox the people were much better compensated, and we wrote lots of firmware, too. It was probably harder to be hired, though.

Re:Why I'm usually unnerved when modern SSDs die on us by optimiz3 on Tuesday December 11, 2018 @10:10PM (#18661067)
"Why do we need source control? It's all there, right on my laptop. Source Depot is just a bunch of trouble."

I've threatened to withhold paychecks from employees who have said this to me. The job isn't done till the code is checked in, building, and backed up.

Re:Why I'm usually unnerved when modern SSDs die on us by brokenmachine on Tuesday December 11, 2018 @07:08PM (#18660209)
Weird, I thought embedded would be much more sought after and rare.
Re:Why I'm usually unnerved when modern SSDs die on us by Matthias247 on Tuesday December 11, 2018 @10:10PM (#18661070)
There's A LOT less people. But the demand is also lower than for people than can build simple websites. It seems like the latter is a lot more important than the first for setting the market rate on salaries. Or maybe it's about the fact that embedded work is often done be electrical engineers, which are seen in a different pay category in some countries.
Re:Why I'm usually unnerved when modern SSDs die on us by PhasmaFelis on Tuesday December 11, 2018 @10:11PM (#18661076)
I know what you mean--they could get paid a lot more elsewhere--but it still weirds me out that techies consider $90k/year "peanuts". I know people trying to raise children on one-third of that.
Re:Why I'm usually unnerved when modern SSDs die on us by sytelus on Wednesday December 12, 2018 @06:06AM (#18662881)
The hardware companies are not super profitable in the first place. Most just struggle to keep light on in their quest for hitting the margin bottom. Also, lot of these improvements don’t usually translate to higher sales because MTBF data is typically not even published for many consumer SSDs.

The solution for this would be to open source such projects so engineers from many smaller companies can collaborate. These companies needs to understand that they will not be able to attract top talent and collaboration instead of competition is the way forward.

Re:Why I'm usually unnerved when modern SSDs die on us by Moral_ on Tuesday December 11, 2018 @07:18PM (#18660255)
Can confirm former Intel SSD in longmont 95k -- shit RSUs.
Re:Why I'm usually unnerved when modern SSDs die on us by vermilingua on Tuesday December 11, 2018 @07:04PM (#18660186)
~$90k is now peanuts. Interesting.
Re:Why I'm usually unnerved when modern SSDs die on us by zanny on Tuesday December 11, 2018 @09:41PM (#18660966)
If you took the doubling of productivity since 1975 and inflation adjusted the median income from then ($7750) you would get about $68,000. In practice wages haven't risen against productivity and GDP so the real figure is $45,000.

To make it look even worse, the GDP tripled but population only rose 50%, so if you adjusted wages against total economic growth instead of productivity median should be around $110,000. Median.

So yes, $90k is pretty much peanuts for how much money an embedded engineer would be on average making for their employer.

Re:Why I'm usually unnerved when modern SSDs die on us by monocasa on Tuesday December 11, 2018 @07:17PM (#18660252)
That's less than 30k in 1980 dollars. Yeah, that's next to nothing.
Re:Why I'm usually unnerved when modern SSDs die on us by losvedir on Wednesday December 12, 2018 @08:16AM (#18663571)
Er, what? Are you thinking of "$30k" in today's terms. $30,000 in 1980 was a lot of money! That's more than $90k in today's dollars...
Re:Why I'm usually unnerved when modern SSDs die on us by checkyoursudo on Tuesday December 11, 2018 @07:43PM (#18660389)
Re:Why I'm usually unnerved when modern SSDs die on us by barrkel on Tuesday December 11, 2018 @08:08PM (#18660533)
Compiler hacking, OTOH is a lot of fun and actually quite rewarding when other devs use your product.
Re:Why I'm usually unnerved when modern SSDs die on us by woolvalley on Wednesday December 12, 2018 @02:12AM (#18661954)
Intel pays not so well, other companies pay better, like apple, fb, google, etc for doing compiler work.
Re:Why I'm usually unnerved when modern SSDs die on us by loeg on Tuesday December 11, 2018 @01:00PM (#18657223)
Users and administrators almost certainly prefer a 20 minute IO latency over data corruption. Host operating systems should probably flag an IO as failed long before 20 minutes and then you know 1) nothing made it to disk and 2) have some chance to avoid introducing additional corruption, if e.g., the OS is smart enough to kick out the drive when this happens.

> Another problem is that the job while rewarding is not very lucrative.

Do you mean it's lower paying than typical bigcorp software jobs outside of FAANG, or just that there aren't a lot of startups with astronomical valuations in the media FTL space?

Re:Why I'm usually unnerved when modern SSDs die on us by xyzzy_plugh on Tuesday December 11, 2018 @01:19PM (#18657391)
Both, and usually significantly.

Last I checked it was nearly twice as lucrative to be a Ruby-on-rails developer than an embedded engineer.

Embedded also attracts a certain type of engineer, usually very smart and able to manage extreme complexity with attention to detail but at the cost of anything resembling readable, let alone maintainable, software. The fact that anything at all works in the modern world is amazing.

I left the embedded space and have never looked back.

Re:Why I'm usually unnerved when modern SSDs die on us by howard941 on Tuesday December 11, 2018 @02:25PM (#18658020)
So $SALT_MINE, a highly profitable privately held Fortune 500 just decided to revamp their pay scales. They've now decided that they want to be at the 50 percentile remuneration-wise in the durable goods sector. That is the white goods sector, washing machines and such.

I predict we will lose all of our engineers - embedded dudes included.

Re:Why I'm usually unnerved when modern SSDs die on us by chrisbennet on Thursday December 13, 2018 @06:36AM (#18671556)
Yeah, but their numbers will look good for a year or two and by then they (CEO, etc) will have moved on to another company before things crash.
Re:Why I'm usually unnerved when modern SSDs die on us by Rinzler89 on Tuesday December 11, 2018 @03:54PM (#18658756)
May I ask how did you manage to leave the embedded world and where did you go after? I'm asking since after investing 6 years into this field, which I love, and jumping a couple of companies I realized the market(Europe) is really bad for this gig. Not only is our work highly challenging it's also poorly paid while at the same time our CEO is crying to the local press they can't find devs(to work for peanuts) and is forced to look for them in Asia.
Re:Why I'm usually unnerved when modern SSDs die on us by xyzzy_plugh on Thursday December 13, 2018 @12:06PM (#18673896)
I just went to do something else. I'm definitely a generalist, and now work mostly with "big" data.

I had zero embedded experience when I started doing embedded dev, and then I had zero data experience -- but a surprising amount of general experience is applicable!

Re:Why I'm usually unnerved when modern SSDs die on us by nickpsecurity on Tuesday December 11, 2018 @11:03PM (#18661305)
"Embedded also attracts a certain type of engineer, usually very smart and able to manage extreme complexity with attention to detail but at the cost of anything resembling readable, let alone maintainable, software. "

Heaven for generalists that always love doing new kinds of things. Once I learned about it, I knew I probably should've done embedded instead of security research. Of course, now there's significant interest in overlap. Might not be too late to learn all that stuff after all. :)

Re:Why I'm usually unnerved when modern SSDs die on us by mcv on Thursday December 13, 2018 @05:39AM (#18671304)

  > Heaven for generalists that always love doing new kinds of things.
Really? That's me. I'm in web development, and I've always felt that embedded was far too specialised for me.

Though I do prefer readable, maintainable code.

Re:Why I'm usually unnerved when modern SSDs die on us by loeg on Tuesday December 11, 2018 @01:21PM (#18657416)
> Last I checked it was nearly twice as lucrative to be a Ruby-on-rails developer than an embedded engineer.

Yeah, yikes. That does not sound appealing :-).

Re:Why I'm usually unnerved when modern SSDs die on us by godzillabrennus on Tuesday December 11, 2018 @01:16PM (#18657359)
As someone that identified a bug in a Drobo firmware once and was offered a job on the spot I think the problem with attracting talent is two fold.

The first problem is really two parts, not only is it rare to find people who have passion for storage related technologies but very few will gain exposure to these technologies to develop that passion.

Kids don't routinely grow up with a SAN in the house. They do tend to grow up with lots of internet connected consumer caliber devices and can easily gain exposure to working with these technologies.

I was fortunately able to explore this type of technology in depth because a family owned business let me tinker with their server equipment in high school.

After college I then co-founded a startup back before the cloud became big. That meant we needed to make use of old hardware to provide service to our customers at a price point that made our service profitable. Old drives were not a reliable way to do that. New drives were extremely expensive for old servers back in the day when SCSI was the interface that you expected for a server. We had to get creative and play with JBOD devices. ZFS was an amazing tool for us in those days, and it still is for anyone who wants to tinker.

The other aspect is that while these skills are valuable for creating a "job" they do not have potential for creating "massive wealth". Why learn about storage if you aren't going to be part of the first 10 employees at a company that has a $10B exit? Let Amazon and the other cloud vendors worry about that stuff.

Knowledge is power though. I recently came across an AI startup that I'm now helping. They were spending significant money using GPU computational power to provide artificial intelligence training through a cloud provider. They blew through about $300k in credits within the first year to give you an idea of how much money that type of power can cost.

I am now helping them cut over to their own co-location facility. The first year alone they will save so much money it will pay for the next three years.

Then you read articles like this: https://www.newyorker.com/magazine/2018/12/10/the-friendship...

Reading that helps reinforce the idea that no matter what path you are on in the field there is potential that some random thing you learned about an SSD firmware helps you optimize some growth stage companies product and ultimately that helps you build wealth.

Re:Why I'm usually unnerved when modern SSDs die on us by ezoe on Tuesday December 11, 2018 @03:11PM (#18658459)
>very few will gain exposure to these technologies to develop that passion.

This, exactly.

SSD firmware is opaque, hard to learn from outside. On the other hand, trending web-based framework has all the source code opened, with great documents, and ready to use tools. No wonder young people of today find passion on other things rather than SSD.

Re:Why I'm usually unnerved when modern SSDs die on us by loeg on Tuesday December 11, 2018 @01:20PM (#18657406)
I'm mostly curious because I work in a storage-adjacent field (NAS) for a BigCorp and the pay is pretty good, if not quite FAANG level. It's not a startup by any means, but I will easily become a multi-millionaire in a handful of years. I was curious about the other side of the fence.
Re:Why I'm usually unnerved when modern SSDs die on us by apetresc on Tuesday December 11, 2018 @02:56PM (#18658314)
Huh? If you're going to "easily become a multi-millionaire in a handful of years", then your pay is more than pretty good, and certainly not worse than FAANG level.
Re:Why I'm usually unnerved when modern SSDs die on us by loeg on Tuesday December 11, 2018 @04:29PM (#18659087)
Sorry, handful of years from today. I've been working for 7 years now. FAANG comp would probably be 20%-25% higher; I'm mostly good at keeping my expenses down and saving a high proportion of my income. I've also had the good fortune of the bull market working in my favor for the entire time I've been employed.
Re:Why I'm usually unnerved when modern SSDs die on us by mandelbrotwurst on Tuesday December 11, 2018 @03:42PM (#18658656)
Maybe his hands are larger than ours ;)
Re:Why I'm usually unnerved when modern SSDs die on us by loeg on Tuesday December 11, 2018 @04:33PM (#18659117)
Only the ten digits ;-)
Re:Why I'm usually unnerved when modern SSDs die on us by mandelbrotwurst on Tuesday December 11, 2018 @07:20PM (#18660267)
Even at that pedestrian level, if you pack them tightly enough I could imagine fitting a few billion years at least into the volume of an average-sized handful!
Re:Why I'm usually unnerved when modern SSDs die on us by hueving on Tuesday December 11, 2018 @03:47PM (#18658700)
What is a handful of years? That sounds like FAANG pay to me.
Re:Why I'm usually unnerved when modern SSDs die on us by loeg on Tuesday December 11, 2018 @04:30PM (#18659091)
Sorry, handful of years from today. I've been working for 7 years now. FAANG comp would probably be 20%-25% higher; I'm mostly good at keeping my expenses down and saving a high proportion of my income. I've also had the good fortune of the bull market working in my favor for the entire time I've been employed.
Re:Why I'm usually unnerved when modern SSDs die on us by brokenmachine on Tuesday December 11, 2018 @07:16PM (#18660242)
>As someone that identified a bug in a Drobo firmware once and was offered a job on the spot

Just curious how you did that. Did you disassemble their firmware?

Re:Why I'm usually unnerved when modern SSDs die on us by godzillabrennus on Saturday December 15, 2018 @08:53PM (#18691344)
It's been about 5+ years at this point so I don't recall all of the details. I can recall that they offered me a job after I pointed out the bug. From what I recall, I politely declined but I helped them test a beta firmware for a while.
Re:Why I'm usually unnerved when modern SSDs die on us by thfuran on Tuesday December 11, 2018 @05:05PM (#18659398)
>The other aspect is that while these skills are valuable for creating a "job" they do not have potential for creating "massive wealth". Why learn about storage if you aren't going to be part of the first 10 employees at a company that has a $10B exit? Let Amazon and the other cloud vendors worry about that stuff.

That seems like a completely ridiculous way to try to organize your life. Almost no companies have $10B exits.

Re:Why I'm usually unnerved when modern SSDs die on us by klaasvakie on Tuesday December 11, 2018 @03:16PM (#18658486)
> Users and administrators almost certainly prefer a 20 minute IO latency over data corruption.

If the drive part of a RAID setup I would actually prefer it just reports itself failed and doesn't slow down access to the array by scanning itself for 20 minutes.

As far as I know, that is one of the main differences when buying enterprise or nas drives compared to consumer drives. With nas drives, the firmware gives up very quickly since the drive is assumed to be part of an array with redundancy. Consumer drives will retry reads for a very long time before reporting i/o error.

Re:Why I'm usually unnerved when modern SSDs die on us by loeg on Tuesday December 11, 2018 @04:34PM (#18659129)
Potato, potato. If your array doesn't kick out a drive that stalls for 30 seconds, much less 20 minutes, why not?
Re:Why I'm usually unnerved when modern SSDs die on us by russdill on Tuesday December 11, 2018 @01:34PM (#18657548)
This is a bit of a misrepresentation. The only flash that never had ECC was NOR. Some embedded systems had NOR, but I'd be incredibly rare to find a consumer SSD with NOR.

When designing a NAND memory product, you aim for some max allowed error rate. You choose the error correction algorithm based on that target. Error rates for NAND products are precisely what the designer intended.

Because SSDs are so large and there is such a large number of them, errors can still occur (at a known rate). FTLs should take that into account. Critical data structures can add checksum redundancy which can reduce the error rate for those to an even lower value, which is usually necessary anyway since power disturbances during erase or program can cause programming errors.

There are of course a number of patterns that increase error rates that FTLs have to be programmed to prevent. Encrypting is the first important step, since it makes the data unlikely to be uniform. The second is mitigating read disturb.

Re:Why I'm usually unnerved when modern SSDs die on us by pkaye on Tuesday December 11, 2018 @03:54PM (#18658753)
I don't mean to imply NAND flash never had ECC. Just that the early flash had needed maybe 1-3 bits of ECC and I would never see an 1-bit error until maybe a few months of use. Things were a lot easier back then. Scrambling and read disturbs were not a issue until later on. All the things you suggest can be done. Just so many opportunities to screw up in the implementation despite the best efforts.
Re:Why I'm usually unnerved when modern SSDs die on us by russdill on Tuesday December 11, 2018 @01:35PM (#18657557)
Oh, and as someone noted below, spinning disks have also long had error correction in order to reach some target error rate.
Re:Why I'm usually unnerved when modern SSDs die on us by Vadoff on Tuesday December 11, 2018 @10:23PM (#18661126)
You can even offer 0 equity, but pretty sure if you offer a $180k salary you'll have a flock of new grads apply.

The reason you're not getting enough new grads is probably because your compensation isn't competitive enough.

Re:Why I'm usually unnerved when modern SSDs die on us by SolarNet on Tuesday December 11, 2018 @07:56PM (#18660463)
I'm surprised no one has mentioned the real difference here. In most startups employees are granted equity. They are closer to worker collectives than they are corporations. In corporations only the capitalist gets any return, they are extracting value from their employees.

The point being, the solution to this sort of systemic problem is for more corporations to become worker owned. If the guy writing the SSD algorithms has a say in governance and a cut in the profits they will want to stick around. It's the stable version of startups.

Re:Why I'm usually unnerved when modern SSDs die on us by feelix on Tuesday December 11, 2018 @11:16PM (#18661355)
Sorry to spin off topic, but perhaps having the chance to speak to someone that's worked on SSD firmware for the first time...

is there any feasible way to recover data after a TRIM command has been issued that you can think of? Is there any way to trick the firmware into not returning 0's when reading the blocks of a deleted file? Mostly interested in doing so for Apple

TRIM destroying the entire data recovery and forensics market seems like such a big deal, I still can't believe it although it started years ago

Re:Why I'm usually unnerved when modern SSDs die on us by ezoe on Tuesday December 11, 2018 @03:02PM (#18658375)
But why is that the pay is not so high?

Manufacturing the hardware requires a lot of capitol to begin with. Why these SSD vendors can't afford the high salary to lure the top talents?

Re:Why I'm usually unnerved when modern SSDs die on us by ams6110 on Tuesday December 11, 2018 @03:03PM (#18658383)
Hardware is a ruthlessly competitive business and profit margins are very thin.
Re:Why I'm usually unnerved when modern SSDs die on us by mcv on Thursday December 13, 2018 @05:50AM (#18671345)
Even so, I'd imagine more reliable SSDs would be able to fetch a higher price.
Re:Why I'm usually unnerved when modern SSDs die on us by sebazzz on Tuesday December 11, 2018 @04:43PM (#18659201)
Are you saying that TLC SSDs are essentially unreliable and it is a miracle we don't see higher failure rates?

Regarding your point regarding languages: I would be interested and motivated, but I probably don't have the skill (probably, only did some x86 ASM/C++) nor the location (Europe). Usually someone doesn't just start with C++ but with a managed language, and once someone lands a job becomes demotivated or just doesn't have enough time.

Re:Why I'm usually unnerved when modern SSDs die on us by howard941 on Tuesday December 11, 2018 @02:21PM (#18657986)
It's not any harder to recruit for that role than any other bare metal, embedded position where new grads are expected to be top notch programmers who know how to figure out the algorithms, write the code, debug the hardware, and bring decades of experience. IOW you're recruiting for unicorns and the pickings are slim.
Re:Why I'm usually unnerved when modern SSDs die on us by jiveturkey on Wednesday December 12, 2018 @11:50AM (#18665421)
> Another problem is that the job while rewarding is not very lucrative.

Why is this a problem?

Let's not forget, we live in a capitalistic society. The job of the capitalists is to exploit labor. The cost of labor is a direct result of the market demand (or not) for a more complex or, by your point, a more robust product.

It need not simply be a market reaction, though. A vendor can create the market for a more complex/robust product. But still, their job is to exploit the available labor so if the people capable of such are available at a lower cost, so be it.

> I have a higher chance working on a web connected gadget to become a millionaire.

As others have noted, perhaps true but the numbers are so small it may as well also be zero. However, as you should now be pointedly aware, the perception doesn't match reality.

Question: do new grads (or let's say up to 3 years experience) working on SSD firmware, making $90k, have to clock in 60+ hours / week and live in insanely high cost regions where their $120k startup salary qualifies them for housing assistance programs and they have to live with at least one if not more roommates? Or is $90k (per another comment) quite good in relation to the total picture?

IOW, my guess is that you are not competing for talent on salary or total comp. My guess is you are competing on general industry attractiveness. The entire mindset around embedded vs web/consumer programming is different. So I think to frame it as a compensation problem is wrong, and by misframing it you will never "solve" it.