HN user

fix4fun

38 karma
Posts0
Comments32
View on HN
No posts found.

It's a beautiful idea :D

Imagine then, after many years during some awards: and the best support role goes to ... NMAP :D

Fear of failure is a stumbling block for science.

That's why many universities declare in their charter that research doesn't have to be practical. The practicality of RSA asymmetric encryption only became practical with the advent of the internet ;)

Thank you marginalia_nu for article and this comment (word stats).

I got similar feeling. I'm new here, but got a feeling that some comments are like bot generated.

Such low p-values are proof that something is going on.

Hipotesis (after your recent word statistics): that some bots are "bumping up" AI related subjects. Maybe some companies using LLM tools want to promote some their products ;)

marginalia_nu respect for your work :)

Thank you for checking :) I was unable to find any details about it. 30 days are impressive, so I was curious if there is some special battery in Time 2.

Yes, that's true ASR-33 was first application, but IBM has impact on ANSI/ASA comeete and ASCII standardisation. In 1963 IBM System/360 was using BCD with digits quick "parse" and in it's peripherals. I remember it from some interview with old IBM tech employee ;)

For me was interesting that all digits in ASCII starts with 0x3, eg. 0x30 - 0, 0x31 - 1, ..., 0x39 - 9. I thought it was accidental, but in real it was intended. This was giving possibility to build simple counting/accounting machines with minimal circuit logic with BCD (Binary Coded Decimals). That was wow for me ;)

Really nice project – respect :) Finding that boot ROM mode by bridging GPIO lines is a great catch. Having a hardwired 'safety net' makes custom firmware projects much more viable. When you were testing the flasher, did you find the CXD2687's flash interface to be deterministic in its failure modes, or did you run into any race conditions/timing issues during the erase/write cycles?

Thanks for sharing your experiences :)

You mentioned "harness engineering". How do you approach building "actual programmed tools" (like screenshot scripts) specifically for an LLM's consumption rather than a human's? Are there specific output formats or constraints you’ve found most effective?

A Broken Heart 6 months ago

`git bisect` is interesting option. I haven't heard about it before. Thanks for info. Still learning something ;)

I'm old school. I used to do "manual bisection" on git history by just `git checkout <commit_id>` until I find first introducing bug commit.

Then another "bisection" on commit changes until minimal change found.

Deterministic bugs are quite "fine". For me personally worst are randomly occurring bugs in specific conditions for eg. some race conditions.

Tractor 6 months ago

Thanks for info. And once again really nice project :)

Tractor 6 months ago

Really nice project - respect :)

Got two questions: 1. How fast it can ride ? If I good estimate (based on max 2750 RPMs for electric motor MY1016 350W 36V, gear ratio ~100:1 and height of rear wheel ~0.5m) it should got about 0.8 m/sec. So really safe for kids and dad :)

2. How long does the battery last ?

667 - “fax number of the beast” - that was funny ;) The thing about mathematics is that it can tickle your brain - in a creative way.

It's becoming increasingly difficult these days, with so many things competing for your attention and "brain-deadening" you. It was a wonderful thing to be bored and play around with math. My favorite moments were the epiphany - that there is some hidden connection between math areas or something got new meaning.

Bunny Database 6 months ago

Yes, libSQL would fit better in that case. But all of it is marketing for better audience ;) (SQLite got x69 more searches than libSQL in Google).

Yes, that's true, because as developer you have to check if "generated" code meet your standards and if is handling all edge cases you see.

When you are an experienced developer and you "struggle" writing manually some code this is important warning indicator about project architecture - that something is wrong in it.

For such cases I like to step back and think about redesign/refactor. When coding goes smoothly, some "unpredicted" customer changes can be added easly into project then it is the best indicator that architecture is fine.

That's my humble human opinion ;)