- eschneider parentAlas, AI generated code is usually more tech debt.
- Is my remote experiences strange or do other remote workers not have some sort of chat where people ask if you've got a minute and drop in a video conference link if they need a quick chat on something?
- I've had to cook from scratch for many years because I've lived with people with various food restrictions and sometimes that's just the easiest way to do things.
That said, you really don't need to spend 1-2 hours a day on cooking. If you put a little time in and level up on some basic skills, you can make shockingly good meals in 10-20 minutes.
It's mostly a question of figuring out what you like and getting good at making those things, then generalizing the skills you have into making more things.
- screams incoherently
- They'll figure it out. As Charles de Gaulle said "The graveyards are full of indispensable men."
- Comments are a gift to future you. When you pick up the code again after 6 months/years/however-long-in-the-future and it looks like something you've never seen before, the comments you left should be notes you need to build context around what's in the code and (sometimes more importantly) what's NOT in the code.
- Hmm...a lot? For a complex work, you'll sometimes do some number of sketches and studies and drawing and underpaintings...Lots of things get tried/discarded/modified before you land on a final painting.
- As my old art teacher used to say, "You work on something and it gets better and better and then it turns to shit."
- 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.
- 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 from my cold, dead fingers.
- 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 getting a new C++ image on new hardware, usually it's just a few days for something basic.
- Yeah, this approach largely works.
- TBF, I paid about twice that for the JLink model I have and I've gotten value for money. I'm not complaining.
- 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 actually behaves.
A simple Forth REPL gives a nicer environment for poking at the low level hardware than going back and forth with C/C++.
I could easily do production code this way, but TBH, I work with other people and have to share code, so C++ is generally the way to go there. :)
- 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.
- 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.
From a practical standpoint, one of the few modern uses where FORTH shines is as a REPL for new chips/SOCs so you can play around with the hardware and see how things actually work/debug the databook.
- What is wrong with people?
- 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 is ultimately your responsibility.
- > 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, lets just say that if you want TENSION at work, good way to get it. :/
- TBF, that approach works and you won't go years w/o any deliverables with that approach.
- 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 do whatever cleanup helps for that bit.
- 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.
- 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.
- >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't actually want the best engineers.
Then they'll help you figure out how to get where the company needs to be, on a feasible timeline, with the resources available.
- Burnout happens for a lot of reasons. And it’s mostly avoidable.
- People don't look down on Mustangs, they look down on people with more horsepower than brains.
- 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 slit is located at the finish line and you start pulling film when the horses approach. Since the exposure is continuous, you never miss the exact moment of the finish.
- 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 good idea how to solve it.
Does it mean THAT problem gets solved later? Sometimes, but often not. And more importantly, I'm maintaining a pace that's SUSTAINABLE. I can crank on hard problems almost constantly, but I leave myself some space so I don't get burned out.
- 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
- Are ads "blocked" if, instead of being presented to a human, they're redirected and read by an AI?
Ad Reading As a Service.