Not in 1982. CD players were very expensive to manufacture and buy and making discs was harder too. Over time it got cheaper because a potato could do the decoding and the lasers got cheap and economies of scale allowed it. But at first it was very expensive, discs cost like twice as much as vinyl albums.
A record player is mechanically and electrically much simpler. And vinyl disks are just pressed vinyl. You can buy a toy kit to build a record player, a CD player is just too complicated.
> You can buy a toy kit to build a record player, a CD player is just too complicated.
you don't need a toy kit, to get sound of a vinyl. but yes it's basically impossible to build a laser and tech to read cd-da and than get audio from it...
You're probably correct. That means the audio CD offered cheaper manufacture and superior sound. (Vinyl lovers will dispute the superior sound claims.)
Call CD sound "more accurate". Vinyl lovers historically loved vinyl precisely because they love the particular inaccuracy it imparts. CDs are more accurate. Brutally so at times, even. Especially when they're being really, really accurate at conveying clipping brought on by the loudness wars.
(Now I suspect vinyl's main purpose in life is as a marker of being a discriminating consumer who doesn't want to be a victim of the loudness war, since you can't overdrive a vinyl record in the same way for physical reasons. It is unfortunate that one must go to such measures to opt out of "music that sounds like crap because you ruined it, you stupid music companies".)
I find this is the best for teams with competent developers. I have seen it abused however, which I guess is why micromanagement is popular in the first place.
From what I saw, at least 90% of the people can work like that. They don't need to be particularly competent, unless by competent you mean "show up at work and do something". It really is a very flexible system as far as complexity and hand-holding on the tasks can go.
Are you really gonna worry about 10% who are unable to learn to work in such a system? At some point, you will probably have to dismiss them anyway.
I think the key point is to give people enough perspective (and stick to it if possible) so it makes sense for them to learn something in a bit of depth, new skill, new module, etc. (Sometimes "code ownership" can be good too - if you know you're gonna continue working on it in the future, you might as well do a better job now.)
This is what micromanagement doesn't provide, in fact, it gets you used to the expectation of the opposite - there is no need and motivation to learn and study anything a bit deeper than to just accomplish the next small task. Micromanagement is literally motivating people not to grow, and not to think for themselves.
Yep, agree. 95% of the code I write is owned by my employer and is under NDA various other privacy / IP laws. The 5% that isn't, has no place in an interview. It's a bunch of brittle glue code automating and backing up data between my devices.
"Passion projects" in my "spare time"... maybe once the kids have grown up and flown the nest...
Leetcode is easy... I memorise a bunch of stuff, do the dance and pass the interview. If i'm lucky I get a problem i've not seen before and actually have to use my brain during the interview.
Isn’t the time spent memorizing leetcode similar to the time spent building a side-project?
I took a look at leetcode when I was interviewing and decided it was a waste of time for me to learn that dance. I was happy with my chances with the companies that didn’t use it in their interviews. And it worked out fine.
No, it’s not, because take home assignments are not typically reusable. Learn leetcode and it is valuable at most companies you will apply to. It’s more respectful of your time.
I was comparing leetcode to sideprojects, not take home assignments. The parent company was also talking about side projects.
Side projects will help you learn useful skills and it is the suggestion of OP that it should be used by more companies in place of leetcode interviews.
Btw, a lot of companies don’t use leetcode for hiring. In my last job hunting season, I would guess than less than 20% of processes used leetcode. Pretty far from “most” companies.
Completely agree re the value of having side projects. I wish I had the luxury of time right now, maybe in a few years once the kids are older.
The leetcode dance is, at least for me at this point, much lower effort than starting a side project on the understanding the code I produce will be reviewed during interviews. It's like Sudoku, once you've done a "few", you get to the point where you're able to solve them quickly.
> Isn’t the time spent memorizing leetcode similar to the time spent building a side-project?
The nice thing about leetcode it is easy to bound the time to what you can handle. I do one puzzle a week and set a timer for 20 minutes. Then I get the answer and browse the forum. It's basically the equivalent of solving the Sunday crossword for me, and it keeps my algorithm skills sharp. Probably no worse than burning a lunch hour on HN.
> 95% of the code I write is owned by my employer and is under NDA various other privacy / IP laws.
True, but would your employer care (if they found out) if you copy/pasted a small portion of code that’s not considered critical IP (like util functions, and an integration syncing records from your backend the Salesforce, or something tangential to the business outside the core product)
May technically be breaking your employment agreement, but I can’t imagine it would be too hard to pluck out a decent amount of code, and re-write portions of it if necessary to “anonymize” it for interviewing purposes.
Or if you happen to be interviewed by someone like me, my approach is simply “if you can’t show me the code, show me the UI and explain how the backend / frontend works, and a discussion ensues.
As mentioned in my original comment, if someone isn’t comfortable showing me the source code I simply ask for them to describe how it works, challenges in building it, how they built it, etc.
I could do this and would welcome this type of interview experience. I'd be able to talk in general terms about the problems I work on and their solutions but not the low level specifics.
To add some context, my work is in Financial Services, trading systems and whatnot.
While I don't see English becoming official it's very true Swedes are proficient in English. At least in tech you are pretty much required to be able to switch to English if anyone non-Swedish joins a meeting.
Outside of work I haven't really met anyone native below the age of 50 who can't communicate in English. That said we are doing an awful job at making it easier to immigrants to learn Swedish, as soon as any Swedish diffuclty is detected a lot of us auto-switch to English.
I have all three, for steaks/burgers I exclusively use the cast iron. Just doesn't brown as nicely on the stainless steel. Not sure if the same applies on gas/induction ovens though.
"I might need it one day when I look for a job" is not accurate at all for me, it finds jobs for me without me even having to interact with it beyond messaging recruiters back if I'm interested. I wouldn't be at my current employment if not for a recruiter finding me on Linkedin.
I'll preface this with I've not had a look at any Kaggle competition, but I always assumed Kaggle competitions was on par with programming competitions in terms of how the skills transfer professionally. A great programmer is not necessarily great at programming competitions after all.
No, there's way more to data science than competitions. But for someone who is already a data engineer more or less, I think it could be a good window into the complexity of modeling.
I've often figured out a GUI faster than it would take me to sift through to the relevant part in a manpage. They work well enough as a reference but I don't understand how people genuinely think they are the ideal tool for learning how to use some new software.
I think so, too. This doesn't mean the CLI is less discoverable (assuming good design), just that active knowledge is harder to aquire than passive knowledge. Passive knowledge is enough to use a GUI, because you can just see where you need to click. There's a lot of "information in the world".
I find that CLIs are usually a little bit harder to learn, but often so much faster if you've learned them, that all professional developer tools should at least have CLI as a possibility.
No, it has a real meaning. How many new businesses are started each year in the US vs the EU? For an existing company, how easy is it to enter a new line of business? How easy is it to hire new workers?
Those things are how dynamic the economy is. It's hard to measure in a rigourous way, but in the US it is distinctly easier for a business to start/expand than it is in the EU.
Digression, so I can get shot at from all sides: This dropped under Obama. Again, it's hard to put concrete numbers on it, but things started happening more slowly - I suspect because regulation became more onerous.