silentbicycle

9 ms·

1. 31.▲
   by silentbicycle 12y ago

   There's value in knowing how it's implemented.
2. 32.▲
   The Fisher-Yates Shuffle – An Algorithm Every Developer Should Know(spin.atomicobject.com)

   1 points by silentbicycle 12y ago|0 comments
3. 33.▲
   0x20 Lessons Learned as a Professional Developer(spin.atomicobject.com)

   2 points by silentbicycle 12y ago|0 comments
4. 34.▲
   Callaloo Radio System: Part 3 – Publishing Status over MQTT and HTTP(spin.atomicobject.com)

   11 points by silentbicycle 12y ago|0 comments
5. 35.▲
   by silentbicycle 12y ago

   I decided against software USB because the receiver is already spending much of its time trying to meet the real-time limits from the radio decoding, and the USB would be its own big undertaking. As I stressed in the preceding post ( http:&
6. 36.▲
   by silentbicycle 12y ago

   Hello, author here. As I said, mostly stressed in the first post, I'm doing things the hard way as a learning exercise, building a bunch of infrastructure myself. I would use a better radio transceiver and a chip with actual USB and UA
7. 37.▲
   Callaloo Radio System: Part 2 – Building a Homebrew USB Device(spin.atomicobject.com)

   19 points by silentbicycle 12y ago|4 comments
8. 38.▲
   by silentbicycle 12y ago

   There's no way to know that the payload has been received - they're transmitters, not transceivers. The messages are idempotent anyway, so just retransmitting makes the whole system simpler.
9. 39.▲
   by silentbicycle 12y ago

   Thanks for letting me know. I made sure the ATtiny84s could be re-flashed in circuit in case something like this came up. (I also have 315MHz modules, and will prefer those in the future. Swapping out the transmitters and receivers will onl
10. 40.▲
    by silentbicycle 12y ago

    Software Defined Radios are also fascinating! That's a very different post, though. :)
11. 41.▲
    Setting Up a Radio System from Scratch(spin.atomicobject.com)

    80 points by silentbicycle 12y ago|17 comments
12. 42.▲
    Setting Up a Radio System from Scratch(spin.atomicobject.com)

    5 points by silentbicycle 12y ago|0 comments
13. 43.▲
    by silentbicycle 13y ago

    Short names also make sense if the same conventions appear over and over throughout the code base. While they can be quite opaque at first, they're very consistent, and people with experience in other APLs will recognize many of them.
14. 44.▲
    Getting Started with MQTT(spin.atomicobject.com)

    3 points by silentbicycle 13y ago|0 comments
15. 45.▲
    Editing the Future – Light Table, and Atom, and Then What?(spin.atomicobject.com)

    2 points by silentbicycle 13y ago|0 comments
16. 46.▲
    More Practical Uses for strace(jvns.ca)

    3 points by silentbicycle 13y ago|0 comments
17. 47.▲
    Tools for Debugging Running Ruby Processes(spin.atomicobject.com)

    2 points by silentbicycle 13y ago|0 comments
18. 48.▲
    by silentbicycle 13y ago

    Excellent, thank you. Those also compile differently for me, so it probably appeared in a newer version of gcc.
19. 49.▲
    by silentbicycle 13y ago

    Would you mind elaborating on that? I don't see this behavior with GCC 4.2.1 on OSX or OpenBSD at -O3 when I look at the disassembly.
20. 50.▲
    by silentbicycle 13y ago

    You might want to read this, then: http://exple.tive.org/blarg/2013/10/22/citation-needed/
21. 51.▲
    Ruby FFI for Quick Prototyping(spin.atomicobject.com)

    2 points by silentbicycle 13y ago|0 comments
22. 52.▲
    by silentbicycle 13y ago

    That did speed things up a bit further: https://github.com/atomicobject/heatshrink/commit/38b8025895...
23. 53.▲
    by silentbicycle 13y ago

    Good idea! I'll try it out later, thanks. Kind of a variant of Boyer-Moore. I had thought about BM, but ruled it out because the search string length isn't fixed.
24. 54.▲
    by silentbicycle 13y ago

    Thanks! There are much better indexing algorithms if you don't have such tight resource constraints, but it may be a useful trick to speed up inner loops in some other algorithms. I realized yesterday that it can also be used as the ba
25. 55.▲
    Lightweight Indexing for Small Strings(spin.atomicobject.com)

    36 points by silentbicycle 13y ago|5 comments
26. 56.▲
    by silentbicycle 13y ago

    I think it could work like this: SUITE_LIST(suites) { suite1, suite2, // ... }; GREATEST_MAIN(suites); but, again, I don't know if that's necessarily an improvement. RUN_SUITE
27. 57.▲
    by silentbicycle 13y ago

    Also, a minor nitpick: the 591 line header is the whole thing. The 133-line .c file is only an example.
28. 58.▲
    by silentbicycle 13y ago

    Unity alone doesn't, but ceedling and CMock do. I was referring to them as a group, because I usually see them used together, but you're right. (I work with most of the maintainers of those tools, and have some minor commits mysel
29. 59.▲
    by silentbicycle 13y ago

    In my experience, unit testing is more common in embedded C development, because the code is held to much higher standard of accountability. Sloppy embedded code can kill people, or at the very least lead to incredibly expensive hardware
30. 60.▲
    by silentbicycle 13y ago

    Thanks! I use GREATEST_MAIN_BEGIN and GREATEST_MAIN_END so that people can put other things in main, around them. Also, there are often several RUN_SUITE calls, and I can't depend on vararg macros portably without also depending on C99