41–50 of 196 posts
Had a $4 mouse from the dollar store. Watched some youtube videos, and decided to splurge and bought the latest and greatest bleeding-edge Mx master 3, at $129 and 3225% more expensive. Despite all the great reviews and hype. I'm kind of hating it. Damn thing is so heavy. It feels like I'm moving a brick around. Was going to return it, but now I'm saving it for a protest.
Had a $4 mouse from the dollar store. Watched some youtube videos, and decided to splurge and bought the latest and greatest bleeding-edge Mx master 3, at $129 and 3225% more expensive. Despite all the great reviews and hype. I'm kind of hating it. Damn thing is so heavy. It feels like I'm moving a brick around. Was going to return it, but now I'm saving it for a protest.
>>It feels like I'm moving a brick around. Was going to return it, but now I'm saving it for a protest. I thought it was still bumble bee tuna.
Had a $4 mouse from the dollar store. Watched some youtube videos, and decided to splurge and bought the latest and greatest bleeding-edge Mx master 3, at $129 and 3225% more expensive. Despite all the great reviews and hype. I'm kind of hating it. Damn thing is so heavy. It feels like I'm moving a brick around. Was going to return it, but now I'm saving it for a protest.
Earlier quoted context omitted.
That sounds like a huge jump! Now I'm curious what kind of solutions where PIC is viable isn't an overkill on Arm? (Or are there really tiny Arms?)
Low end cortex-m cores are pretty cheap these days. More modern designs and processes use silicon more efficiently, so you get more capability for the same raw material cost. Also, you can do a surprising amount with an 8-bit MCU. Lots of very capable 3D printers still run on AVR based controllers. Often times, you're limited by peripherals or memory size more than raw CPU speed. As a baseline, it's relatively easy t…
I really hope the reason isn't "so we could run the mainline linux kernel" or "because we needed a RTOS" or something similarly bloated.
Looking at their homepage it's very hard to understand what they actually provide.
Earlier quoted context omitted.
It's such a difficult line to toe. Especially because people like working with new technology and it does seem to help with recruiting even if it makes actually operating the business harder.
Some people like working with new tech; in my experience most do it not because they like it but because of their resume. I like how I can get really good, cheap and experienced devs for ‘non hip’ tech because they do not want to work with new tech, they want to improve their skill on what they know; java/spring, c#/asp, django etc with jquery/bootstrap. Resume driven/recruiting forces them into all the new stuff but…
> they rather take a pay-cut to work with the stuff they know and are good at.
The question is, are your employees aware of this?
Seems to be this article is about when your product is bleeding-edge tech, but people are commenting as if it were about building your product using bleeding-edge tech (in-house or otherwise). Definitely only do one of these at a time, tho :)
Yes, the article is exclusively about the trade-offs when building bleeding-edge products, like how impossibly hard it is to sell in to customers who have no idea what the product is or why it exists. All of the comments for some reason are about not using latest-nosql-db-from-producthunt in prod.
Seems to be this article is about when your product is bleeding-edge tech, but people are commenting as if it were about building your product using bleeding-edge tech (in-house or otherwise). Definitely only do one of these at a time, tho :)