HN user

saidinesh5

1,575 karma

:D

Posts3
Comments488
View on HN

I think the steam deck proved otherwise too..

I haven't had enough motivation to sit on my couch and game after a long day ..

But the same game, in bed, on my deck was so much nicer..

All I can now say is having a dedicated device, that's not your laptop/computer to play games is definitely a market - be it Steam machine (/custom builds), hand held gaming, or just regular consoles..

Chances are you'll run out of ram trying to run a browser inside another browser on a TV with 1-2GB ram usually.

You might have a better luck with network level ad blocker like pi-hole or adguard for eg

It's definitely the port too. I changed the cable and the connection is still loose. Not as bad as the previous cable, but still bad..

Yesterday, I had an interesting situation where a colleague was using LLM to type up the chat responses to me.

They used an LLM to come up with a Hackathon idea. They tried to use LLM to get to the implementation part. One of the permissions they (/the LLM) were asking for wasn't even needed for their project. When I pointed that out, I got a response from them that starts with "You are right about the permissions".

Today they've successfully finished the project too.

Not sure what I even think/feel about this but it's definitely weird to think about this.

I think my only big complaint with USB C these days is that the sockets wear out quickly.

The charging port on my motorola phone got so loose that I frequently end up with an uncharged phone after a full night of "charging", just because the cable's own weight keeps yanking it out of the phone. The phone is not even 3 years old.

It would be nice to get a user replaceable USB port. Meanwhile, I'm not sure if those magnetic USB cables help this situation any bit or they further damage the port.

The best part of this is you can daisy chain tunnels and have a network connection between any machines you can ssh into.

If you have a private server with a public IP, you don't need localtunnel etc.. you can just use ssh tunnels to expose your home network services over public IP.

I don't quite understand why "embedded" has historically meant learning a completely separate tool. I've been building for x86 and ARM servers for 5+ years now, so why should targeting an ARM board be any different?

Because embedded usually means dealing with complete functionality provided by the soc, bare minimum for the init system to get quick boot times.

If you just want to boot the CPU and run some IoT app, device tree + kernel + uboot should be enough.

But for anything with a GUI, You'd probably need the vendor provided binary blobs for GPU accelerated UI, proper gstreamer packages with all the patches to make it work with the binary blobs... properly packaged Qt etc ... Not to mention read only rootfs and A/B partitions for upgrades to deal with power loss headaches.

I haven't used Nix for any of these but most of these things are available ready to use with the vendor provided buildroot or yocto setups. And it would've been just more work to get this all working with yet another build system/package manager

Fun story: A few years ago, I worked for a small company that customized off the shelf routers to enable businesses provide Wifi Hotspots.

The routers were very basic model with very limited flash memory (~4MB?). I was brought in to build firmware for those routers. I ended up customising openwrt - removed all kinds of packages to make their packages fit on those routers. At the end, I had less than 4KB space, And I needed to implement a "heart beat" service. A lot of routers were behind firewalls that only allowed http, https and a couple of other protocols. Libcurl was too heavy. So I ended up writing a shell script that used this feature of bash to send out heart beats.

Fun times...

We faced a lot of this this year. Eager new joinees sent 100s of lines of CLs to review to "improve" little things.

Not only did the new changes did not fix what they thought it would fix but it broke other things in unexpected ways.

I brought in two changes after that:

* I'm not reviewing/reading anything that you yourself did not read / test in the target environments properly. If all it takes is an LLM prompt, I could be issuing the same prompt to make my life easier.. and If you're sending a CL, you should be owning the code you send.

* Me being more involved in the design process so review burden itself becomes lower. A bit of pair programming from time to time helped too.

Not sure how things will turn out after this but so far they seem better.

The worst part of this is half of these are the same white labelled tuya devices that can simply bind to each other's apps or the original tuya app..

And half of them completely disable local network access... Like why?!

Mosh instead of ssh. Works well enough for as long as it works.

Road warrior even supports it.

But i keep going back to regular ssh or shpool with roadwarrior.

I think things might have changed in the last 6-7 years? That's when I switched away from Nvidia.

Or does your laptop have no other igpu?

My last Nvidia laptop was a Hybrid optimus laptop. I almost always ran it on the built in Intel igpu because of the really bad issues with the Nvidia cards. Video tearing, bad power management etc... I remember even switching the GPU wasn't easy... And performance wasn't as good either ..

Putting all the cynicism side.. it's amazing how big the changes in how we deal with information in our life time changed..

When I was younger, to solve a problem, we had to memorize a large amount of information. Or know someone who does. Or visit libraries and pray they have a book on what you need.

Then came the internet. All of that memorizing was replaced by web searches. You just focus on solving the problem, figuring out what you don't know and searching for that.

Now, it feels like we're automating the searching, connecting the dots and most of the problem solving. We focus on the high level problem description, verification of the results.

I wonder what they'd be adding to this curriculum.

Now, it feels like we're even offloading

Honestly, LLMs have been quite good at helping me procrastinate less on my pet projects.

It took me a weekend to build a little esp8266 gadget that automatically turns off my parents' water heater after a fixed time. They saw a dip in our power bill thanks to that. I did not want the complexity of a full blown home assistant setup there. And the Philips Wiz socket did not support setting timers/simple automations.I wanted to test out micropython too for this instead of the usual C++/Arduino/etc..

I started on a saturday and went from 0 to 90 that single day. The product I had after that day was mostly complete but it was crashing at odd times. I spent another day to get to the root cause of the issue - caused by the LLM mixing up async and sync functions. One prompt to the LLM and the problem is gone. The product has been running flawlessly since then - for months.

Every weekend I spent with Antigravity - I was able to push out something totally usable. Water Heater monitor, configurations for the custom Tuya devices I installed in my home, a chrome extension I wanted to use at work.

I am honestly impressed at the pace at which this whole thing improved too. Just 2 years ago - it was a totally useless tool that couldn't even match the speed or accuracy of my text editor snippets.

The standard advice is always to buy a transmitter and get started with the simulator. Then buy / build your custom racing drone that suits your flying style and area. Anything from 20 gram whoops that fly indoors to 5" racing quads that need a lot of open space.

But with dji neo 2 / avata you get a fairly beginner friendly set up. Once you're used to it, you can upgrade to a good racing drone by building one yourself.

With micropython or some of the js based frameworks for microcontrollers, it's really not that new/different.Especially with ESP32/Pi Pico W/their clones...

In fact it's a lot more straight forward to not have to deal with Network Manager config files or systemd unit files or read only rootfs headaches of Linux world.

Mostly for the network stack. Economics, also, sometimes.

These days, with ESP32, Pi Pico W etc... things have changed a lot.

But before they got popular, Why deal with MCU + wiring some weird peripheral for wifi / ethernet when you get a Pi Zero W / Clone with built in wifi for the same price?

It might be developer fantasy but half of the giants in the mobile market really did take off this way:

* xiaomi with their miui skin/custom ROM - "bringing iOS like polish to Android" back then

* oneplus with their initial devices with cyanogenmod - clean aosp interface without any bloat and lots of features.

In fact, when my brother was buying phones for my mom (neither of them were really that technically inclined), he bought a Motorola mostly because "it doesn't have all those ads like redmi at the same price"

I think the main difference due to weight boils down to you riding in one gear lower when not using assistance.

On flat roads, I usually ride on 3rd or 4th gear (out of 7), now i ride in 2nd or 3rd.

But where i ride, the road isn't even and has a lot of steep slopes. There I'm on 1st gear all the time anyway and the assistance i get totally saves my knees, and ensures I'm not all sweaty when i reach my destination. Even compared to the light weight regular bicycles i rode before, this is better.