111–120 of 138 posts
Peruse README and source code
x=pico-usb-wifi
tnftp -4o"|unzip -p /dev/stdin $x-main/README.adoc $x-main/src/*.c" \
https://gitlab.com/baiyibai/$x/-/archive/main/$x-main.zip \
|tr -cd '[ -~\n]' \
|lessIt's pretty cool, I have to say - especially for us old Oric folks, who never did quite get a full BBS ecosystem for these machines, unlike others. Its on like donkey kong now though, thanks to wonderful PicoW projects like this!
I would like to ask the author, what do they mean when they say 'I spent 2 days and 1M claude code tokens' Did you completely vibe code this? or did you create a spec and asked claude to implement that? How many times did you need to course correct claude when it deviated if it did? How much of your own experience as working in WiFi industry was useful while building this project? And what would be different if you h…
Earlier quoted context omitted.
Wifi printer, where both your machine and the printer are connected to the same AP? yes If you'd rather just expose a USB printer to the network, a Pi Zero is a better fit.
No. The printer cannot connect to the wifi network that the macbook is connected to. I don't want to expose a USB printer to the network. I just want to allow the printer to connect to an AP created by the Macbook/PiZero/ESP32/insert_cheap_widget device and then allow the Macbook to connect to the printer's IP.
What the Macbook can't do is have multiple wifi connections at the same time, so you'd have to disconnect from its primary network (which also rules out the Macbook serving as an AP that the printer connects to).
Interesting that Gemini said it was infeasible. It should be aware that using a Pico W as a transparent ethernet bridge has been done several times over in open source projects, for example on BlueSCSI (emulating a Daynaport SCSI-Ethernet adapter) and PicoMEM and my own PicoGUS project (emulating an NE2000 Ethernet adapter).
My experience with questions to LLM is that they mimic reddit a lot: ask them an apparently simple thing that is not possible, and they will bend backwards to tell you it's possible and give you tons of convoluted possible solutions. Ask them a thing that is possible but complicated, and they will be overly dismissive. The good thing however is that between those two banks there's a wide river of utility...more often…
ya, that is my experience as well
I would like to ask the author, what do they mean when they say 'I spent 2 days and 1M claude code tokens' Did you completely vibe code this? or did you create a spec and asked claude to implement that? How many times did you need to course correct claude when it deviated if it did? How much of your own experience as working in WiFi industry was useful while building this project? And what would be different if you h…
I've often thought that if I ever did get around to publishing any of the stuff I work on that I would probably also publish any AI usage verbatim. Like, the full logs of all of the chats, at least as a sign of "here was my thought process" and "here's how I convinced the text machine to give me the right text". That somehow feels more honest than "I made this thing, but actually I vibe coded this thing."
Google Gemini is that naysayer senior developer who confidently tells you it can’t be done. Claude is that easy to get along with smart hard working guy who just gets on with it and builds it double quick. ChatGPT is the eager senior developer who says it can be done but can’t actually work it out and fluffs it.
ChatGPT is very good at code-reviewing Claude’s work and finds the howlers in it fairly reliably
I’ve been looking for a good solution for doing the exact opposite, being able to connect stuff through USB in my bench, and see them pop up in my office desktop as if they were usb devices. The closest I’ve gotten is using a raspberry pi in the workbench, but for some weird devices that’s sometimes not good enough.
I would like to ask the author, what do they mean when they say 'I spent 2 days and 1M claude code tokens' Did you completely vibe code this? or did you create a spec and asked claude to implement that? How many times did you need to course correct claude when it deviated if it did? How much of your own experience as working in WiFi industry was useful while building this project? And what would be different if you h…
https://gitlab.com/baiyibai/superbird-host-mode
I also did not look forward to trying to build in wireless functionality in to NixOS, because it also took 30 minutes to flash the device - I had to lower the transfer block size and add more retries in the flash utility because it kept crashing.
ultimately both the SuperBird work and the RPI pico firmware was about 300 prompts of investigation, research, creating potential approaches, architecting, designing, debugging, testing/validating, and documenting.
Regarding your last two questions... I started out 25 years ago by studying for a CCNA in high school and joined the industry just as first generation 802.11ac devices began hitting the market. From my position, I've worked on every layer from the SoC, PCB, to software. I want to be very careful and say software estimation is very difficult. The main bug (issue #1) I encountered would have been very difficult to diagnose and resolve ten years ago using traditional development workflows.
Buried the lede by calling this a "usb wifi adapter" and not "magic Ethernet adapter that you don't have to plug a cable into". This will come in handy for my systems that are normally air gapped or currently connected to something else, but sometimes I need to get another network connection on there for a few minutes. I don't always have a USB ethernet adapter on hand or enough cable, but I almost always have a Pico…
Now I need to make a nice 3D-printed case.
I admit, I almost couldn't believe it when I turned off my regular blazing fast 802.11ax NIC in the KDE network manager and switched to the pico-usb-wifi and I watched the YouTube "stats for nerds" buffer fully fill up and playback was totally smooth.