Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
eschneider
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
eschneider
11mo ago
The article seems to ignore the fact that many people use the shopping cart as a walker substitute. It's an accessibility aid and it's genuinely difficult for some folks to return the cart and walk back to their car.
32.
▲
by
eschneider
1y ago
I really only use lazy git to review my code before commit it and I inevitably his the wrong scroll key and split the windows in half when I didn't mean to and I have to quit and restart to fix it. That said, you'll pry that app f
33.
▲
by
eschneider
1y ago
Data sheets are usually 'accurate' as far as they go. I'm often working with pre-production samples so not everything _quite_ works and sometimes it's just handy to experiment and see for yourself what happens. As for ge
34.
▲
by
eschneider
1y ago
Yeah, this approach largely works.
35.
▲
by
eschneider
1y ago
TBF, I paid about twice that for the JLink model I have and I've gotten value for money. I'm not complaining.
36.
▲
by
eschneider
1y ago
Yeah, I've been doing that a bit, mostly with STM32G474 (arm core) chips and my own Forth system. I'm not using it for production code, but I definitely use it for prototyping/experimenting with the SOC to see how the system
37.
▲
by
eschneider
1y ago
Large Scale Assembly puts a huge premium on planning and design. If you try to just bang things out, you'll live in a world of pain.
38.
▲
by
eschneider
1y ago
Very much this. Even when programming for constrained environments, it's almost never necessary to self-host anymore. It's easy to use host-side tools to crunch code down to something that'll work on whatever the target is. F
39.
▲
by
eschneider
1y ago
What is wrong with people?
40.
▲
by
eschneider
1y ago
If you pull something into your project, you're responsible for it working. Full stop. There are a lot of ways to manage/control dependencies. Pick something that works best for you, but be aware, due diligence, like maintenance i
41.
▲
by
eschneider
1y ago
> Your CI/CD takes a huge amount of time because you forgot to leverage caching. The bane of my existence are CI/CD systems that get caching 99% right. Chasing down the problems from that last 1% of strangely busted...well, let
42.
▲
by
eschneider
1y ago
TBF, that approach works and you won't go years w/o any deliverables with that approach.
43.
▲
by
eschneider
1y ago
Very much this. There's no need (and certainly never time) to add tests to the world or refactor everything. But it's often practical to figure out "I need to make changes "here" and add tests for that section and d
44.
▲
by
eschneider
1y ago
I remember Kyan Pascal on the Atari. It worked, but I'm not sure it worked _well_. Better than BASIC, but still quite a bit slower than ASM. Action! was much nicer if you were looking to deliver software on the Atari.
45.
▲
by
eschneider
1y ago
The lack of recursion was not a practical limitation on the Atari. Base systems were 16K and you really didn't have space for recursion. And the license fee for the runtime didn't feel that painful compared to the other options.
46.
▲
by
eschneider
1y ago
>The best engineers will tell you why your architecture is wrong, why your code sucks, why your timeline is unrealistic, and why your product decisions make no technical sense. If you're not ready for that level of pushback, you don
47.
▲
by
eschneider
1y ago
Burnout happens for a lot of reasons. And it’s mostly avoidable.
48.
▲
by
eschneider
1y ago
People don't look down on Mustangs, they look down on people with more horsepower than brains.
49.
▲
by
eschneider
1y ago
You use a single vertical line of sensors and resample "continuously". When doing this with film, the aperture is a vertical slit and you continuously advance the film during the exposure. For "finish line" cameras, the
50.
▲
by
eschneider
1y ago
So much this. As I've gotten older, instead of working half the night on a difficult end-of-day problem that I'm stuck on, I just set it aside at the end of the day and by the time I start back up in the morning, I've got a g
51.
▲
by
eschneider
1y ago
Oh, so there's a complete copy (or something that can be reassembled into a copy) completely OUTSIDE of audit controls. That's so much worse. :0
52.
▲
by
eschneider
1y ago
Are ads "blocked" if, instead of being presented to a human, they're redirected and read by an AI? Ad Reading As a Service.
53.
▲
by
eschneider
1y ago
I've been running a text based todo/status doc for about that long and my hack for that particular problem is to occasionally do a scan and copy anything 'active' to the top (or bottom if you append to the end :) of the
54.
▲
by
eschneider
1y ago
Debugging/modifying code generated from someone's undocumented c++ code generator is pretty close to the top of my list of unpleasant things to do. Yes, you can eventually figure out what to do by looking at the generated code and
55.
▲
by
eschneider
1y ago
It's not a good/bad business so much as a _different kind_ of business, with different engineering/sales requirements and different customers. Neither is better, or more profitable over the long term than the other, but you r
56.
▲
by
eschneider
1y ago
Agendas are critical is deciding a) do I care and b) can I help.
57.
▲
by
eschneider
1y ago
Ooof, I still have entirely too many of those on paper. OTOH, when you need obsolete computer reference to do some bug fixes, they can be hard to find...
58.
▲
by
eschneider
1y ago
So novel, they couldn't even come up with an original name.
59.
▲
by
eschneider
1y ago
Just one thing I'd like to throw out here after far too long in the industry: It's very hard to tell ahead of time just how users will put computers/software to use. Lots of generic, off-the-shelf HW and SW get used in ways t
60.
▲
by
eschneider
1y ago
There _used_ to be a huge advantage to pulling everything into emacs rather than having to background emacs, do whatever, then bring emacs back into the foreground. With multiple windows or multiplexers like tmux/screen, it's a lo
More ›