[0] https://lectronz.com/products/drv8825-stepper-motor-stepstic...
It's little more than a standard IC on a simple board with a standard pinout.
[0] https://lectronz.com/products/drv8825-stepper-motor-stepstic...
It's little more than a standard IC on a simple board with a standard pinout.
I don't use social media because I think it's a net negative in my life. However YouTube I've always justified by following lots of educational content. I've learned a lot of cool things and gained new hobbies just by watching YouTube. One day, leather-working videos popped up on my feed. Soon I was making my own stuff with leather - it was a heap of fun!
I've noticed over the past few years though, that no matter how much I try to tweak the algorithm, I'm just getting mindless junk. And shorts are the worst of it! They're deliberately designed to hook you in, so they're very hard to ignore.
And so YouTube, I have to admit, has become a net negative. Another place for mindless dopamine hits, zombifying us all. I'm so sad about it!
I think the key is that I subscribe to channels I want to watch and I use the like button on videos I want to see more of.
> I've noticed over the past few years though, that no matter how much I try to tweak the algorithm, I'm just getting mindless junk. And shorts are the worst of it! They're deliberately designed to hook you in, so they're very hard to ignore.
If you're actually clicking the shorts ("very hard to ignore") then you're going to get more of them, period. I get an occasional shorts line in my feed but I scroll right past it.
I have never in my career had to do anything like designing a large scale system. Maybe I'm inadequate, maybe I've been insufficiently motivated, but it hasn't happened. If that's a requirement, say so and don't waste the time of applicants who don't know what a ring tokenizer is.
As it was, it turned into a ridiculous charade session where I watched a bunch of videos and regurgitated them as though I knew what I was talking about. "Oh yes, I'd use a column oriented database and put a load balancer in front".
Without any real-word experience it's just a bunch of BS. I'd never let someone like me design a large scale system - not even close. I don't want to design large scale systems, it sounds boring and like the type of job where you're expected to be on call 24/7.
I've worked with the Linux kernel, I've written device drivers, I've programed in everything from C to Go, and that's what I want to keep doing. Why put me through this?
Giving large scale system design interview questions for a role where someone never has to work with large scale systems would be a weird cargo cult choice.
However, when a job involves working with large scale systems, it's important to understand the bigger picture even if you're never going to be the one designing the entire thing from scratch. Knowing why decisions were made and the context within which you're operating is important for being able to make good decisions.
> I've worked with the Linux kernel, I've written device drivers, I've programed in everything from Fortran to Go, and that's what I want to keep doing. Why put me through this?
If you were applying to a job for Linux kernel development, device driver development, and Fortran then I wouldn't expect your interviewers to ask about large scale distributed web development either. However, if you're applying to a job that involves doing large scale web development, then your experience writing Linux kernel code and device drivers obviously isn't a substitute for understanding these large scale system design questions.
It took us a long time to go from 1080p to 4K. It has taken even longer for 4K at 120-144Hz to be practical.
It’s more likely that you’ll end up with intermediate steps to 5K, 6K, than getting 8K 120Hz.
The other limitation is lack of demand. You need a gigantic monitor for 8K to be worth it, and you need a powerful video card to drive it. The number of people who would buy such a monitor is very, very small.
I agree with the spirit of what you imply: what a waste. On the other hand we do not use titanium everywhere, only where needed. There is best for a specific usecase.
At this point, I think the debate about slow apps is more ideological than reality.
I also think a lot of people are mistaking backend/network latency for front-end slowness. Slack isn’t going to load your scroll back history any faster if the backend is spending all of that time searching the database. People are too quick to blame the front end.
Either that, or some of these posters are running 10-year old hardware and wonder why it’s slow
The argument is rather the following: common knowledge is that it’s not worth optimizing the code and that programming languages don’t matter, because the IO is too slow anyway. This fizzbuzz shows just how bad we are at IO compared to the optimum. So if we were to improve the IO, then faster processing would also make a difference. In this case you get an improvement of 179x compared to Python, i.e. your laptop will do instead of multiple clusters in the cloud.
If this task was the bottleneck in a large scale system then it would definitely get hand optimized after a proper analysis.
But if this is an occasionally run task or something otherwise not business critical that doesn’t bottleneck anything, spending orders of magnitude more time hyper-optimizing it would be a waste of time and money.
Match the solution to the job. Optimizing everything is one of the age-old mistakes in computer science.
It is a very rare quality and few can pull it off - if you find a boss like that, consider yourself lucky.
The worst managers I’ve had were umbrellas, but to such an extreme that they kept us in an isolated island separate from the rest of the company. We didn’t know what was going on in the company and had no chance to integrate that content into our work. It felt good at first, but over time I realized that the umbrella manager was trying to keep us in the dark so they could keep exclusive control over our work and neutralize any possibility of us competing with them among management. The last manager I had like this went so far they they would praise us for our work and give nothing but positive feedback, right up until he cut people for low performance. It felt like everything he did was for equal parts performance (looking like the ideal, happy, positive manager) and control (keeping us isolated from the rest of the company so he was always in full control).
Ironically, that manager now posts frequent leadership thoughts on LinkedIn and has a newsletter.
It’s nowhere near on the level of removing airbags.
In hindsight this should be a “how I quadrupled my salary” story. But I’m sharing it in case anyone who feels anxious about negotiating is selling themselves way too short. Go get more money. Relax about it unless you don’t want to. You’re gonna get more money regardless.
Unfortunately, this is how most "I tripled my salary in X years" stories look when you dig into the details.
I've spent a lot of time coaching people on interviewing and negotiating. With some people, half the battle is detaching them from their original compensation anchor point and re-centering on real market data.
On the other hand, I've also had to gently convince a lot of eager students that they can't expect $300K full-remote FAANG offers right out of college, despite whatever they heard on Reddit and Blind.
> A company going under.
What a wild assertion: The OP hasn’t personally seen a company fail, and therefore software quality doesn’t matter? Bugs and slow delivery are fine?
It’s trivially easy to find counterexamples of companies failing because their software products were inferior to newcomers who delivered good results, fast development, and more stable experience. Startups fail all the time because their software isn’t good enough or isn’t delivered before the runway expires. The author is deliberately choosing to ignore this hard reality.
I think the author may have been swept up in big, slow companies that have so much money that they can afford to have terrible software development practices and massive internal bloat. Stay in this environment long enough and even the worst software development practices start to feel “normal” because you look around and nothing bad has happened yet.