gregmac

15 ms·

1.
by gregmac 9mo ago
> To put a bit more colour on this, I think the fear of most devs with an ultra-simple framework like this is that eventually you hit a wall where you need it to do something it doesn't natively do, and because the only thing you kn
2.
by gregmac 10mo ago
> if your source code is based on newer .NET you have to update to a new version each year .NET has a really refreshingly sane release life cycle, similar to nodejs: - There's a new major release every year (in November) - Even numb
3.
by gregmac 11mo ago
It's good to move to Zigbee/thread/z-wave anyway because they're all better protocols for smarthome stuff. Plus wifi means you might be buying stuff that relies on cloud, which is a non-starter for anyone that doesn&#x27
4.
by gregmac 11mo ago
> there’s not good support for very low power devices that use WiFi That's why we have Thread. Wifi just isn't a very efficient protocol for using with deep sleep. The radio takes more power to run, the overhead of connecting i
5.
by gregmac 11mo ago
When I first saw the iPhone I remember thinking how silly it was that a device calling itself a "phone" only had the phone function as of many apps. Other phones had internet and other features, sure, but their "home" sc
6.
by gregmac 1y ago
It sounds like you think I'm victim-blaming here and that's not my intent at all. Part of being in business is anticipating risks and having a plan -- which could be deciding to accept the risk. What sucks is you're implicitl
7.
by gregmac 1y ago
> refuse to let them export it Honestly, it's hard to feel too bad for people making the choices to use this stuff without considering an escape plan or safety net and then getting burned by it. You choose to not get fire insuranc
8.
by gregmac 1y ago
> for example, I've seen N+1 problem sneak past because at the time the performance was good enough but once there was enough data it crumbled This is a super-common problem I've had to help with many times. It generally happen
9.
by gregmac 1y ago
Am I the only one struggling to decipher this? I thought web3 was supposed to be some kind of decentralized compute, where rather than run on your own hardware or IaaS/PaaS you could make use of compute resources that vary wildly day-t
10.
by gregmac 1y ago
And you're used to the weight of the glass, which you instantly recognize when you pick it up. If it was a different weight than you were expecting, you'd probably slow down and be more deliberate. If you were to just do the exact
11.
by gregmac 1y ago
> It's so shitty and slow because it's a bloatware Bloatware is unwanted software, usually pre-installed or otherwise not installed by the user, that slows down your computer and takes up space. So if a user wants Office, it
12.
by gregmac 1y ago
> As the neighborhood becomes denser, rents might go down, but land values will go up, since a given piece of land can now be used to build a more profitable apartment building. You're taking about the wholesale destruction of neigh
13.
by gregmac 2y ago
Yeah, I was afraid for a second there. I have a few Wiz bulbs and was hoping that ecosystem wouldn't suddenly die
14.
by gregmac 2y ago
Yep, agreed, and IMHO in a lot of cases, as-is, terraform wouldn't be viable as a closed-source product. At least, I would have got frustrated and ditched it. I haven't personally found a real bug in terraform or a provider yet, b
15.
by gregmac 2y ago
Having debugged this sort of thing before, it's actually really hard to figure that out. The entire stack is kind of bad at both logging and having understandable error messages. You get things like this: ╷ │ Error: googleapi
16.
by gregmac 2y ago
Good point, but it's still a very useful way to ensure it doesn't get swapped out underneath you. Transitive dependencies are still a problem though. You kind of fall back to needing a lock file or specifying everything explicitly
17.
by gregmac 2y ago
> Where you end up in this spectrum is a matter of cost benefit. Nothing else. And that calculation always changes. This is where I see things too. When you start out, all your value comes from working on your core problem. eg: You'
18.
by gregmac 2y ago
I echo this. No pull requests is awful. The only time it's worked well for me is with 2 or 3 people sitting next to each other, with the same mindset and coding style. Every other time I've seen or worked with teams doing it, thei
19.
by gregmac 2y ago
5% off your next lunch and 5% off your next car are very much not the same thing.
20.
by gregmac 2y ago
Yeah, at the core of it I see this as a value problem. If you charge a lot, it's a tough or impossible sell for users who aren't yet sure they'll get that amount of value from it. If you charge too little, you're leaving
21.
by gregmac 2y ago
The author's blog also explicitly defines color: #111; background-color: #fdfdfd; which is a contrast ratio of 18:56:1.
22.
by gregmac 2y ago
FWIW that's not even how Alexa or Google Assistant work. Both listen locally for the wake word with onboard processing, and only when they recognize it do they send the audio stream to the server to fully interpret. You can test this i
23.
by gregmac 2y ago
Yeah, the physical barrier is key. It's not that hard, and provides absolute certainty. As indicated by this thread, software experts (rightly) don't trust software by itself enough. It's by the same rationale software people
24.
by gregmac 2y ago
I'd argue "friend of a friend" is strong transitivly because it's explicitly chosen by all parties involved. Trust in a professional relation - a doctor, especially - is actually very strong, because of the professional
25.
by gregmac 2y ago
Which also means never assume the exhaustive list is 100%.
26.
by gregmac 2y ago
I haven't read the book, but my experience is that the way to make things flexible is to make them simple as possible. When I've used (or built) something that was built in the style like you're talking about, it's almos
27.
by gregmac 2y ago
I get that, and like anything it's a matter of trade-offs. To me, in most cases, 4 or even 10 minutes is just not a big deal. It's fire-and-forget, and there should be a bunch of things in place to prevent bad deploys and ultimate
28.
by gregmac 2y ago
> If you fix some UI bug with a button in the React SPA, why would you also deploy the backend? Why would you bother to spend the time figuring out whether or not it needs to get deployed? Why would you spend time training other (and new
29.
by gregmac 2y ago
To me, monorepo vs multi-repo is not about the code organization, but about the deployment strategy. My rule is that there should be a 1:1 relation between a repository and a release/deployment. If you do one big monolithic deploy, one
30.
by gregmac 2y ago
> if you were a big celebrity, you could get an "unlisted" number (I think you had to pay for it), but that was relatively rare. Anyone could do it. It almost seems like extortion: "pay us $$ or we'll publish your nam

More ›