philote

More like "We can track you better in the app"

I'm getting out of my comfort zone (software) to work on a telepresence robot for my D&D games. My main motivator for this is that I'm often the only person remote for these sessions and it's difficult to hear just the DM talk when everyone else is talking. So I thought that having binaural audio would be helpful, and even moreso if the microphones can be aimed at the person talking. So, now I have some 3d printed pieces that fit together with a couple of servos that can turn the entire thing on a lazy susan base and also rotate the head up and down. My soldering skills suck, so I'm currently stalled while I figure out why the PWM controller isn't being seen after I rewired everything (in an attempt to clean up the cable mess). But, I have(had) gotten a Raspberry Pi set up and working with the servos and two microphones and once I get my issues sorted I can start playing more with the software for it.

Yeah I loaded it up and had no idea what to do.

Yes, a public database like this would be acceptable. That way the info isn't paywalled behind some white pages site or similar. And then maybe I could even update my own info to be correct. Contact info is pretty much out there for most people already. Hell, I put it on my resume and send that out to many people and put it on public sites.

I don't disagree, but broadening your network is a very different skill (being social) than handling investment portfolios. And for some of us, it's not that we necessarily despise creating or maintaining a network, it's that we suck at it.

I recently had a coworker open my eyes to why vibe coding, or AI-assisted coding is so popular. He likened it to a slot machine, where pulling the slot's arm is like asking an LLM to code something. You get crap most of the time, but when it works, it's like getting a payout. That dopamine hit keeps them pulling, hoping for another hit, and they then believe it's a better way to develop software.

I'd argue genes nor life has a "goal". They are what they are because they've been successful at continuing their existence. Would you say a rock's goal is not to get broken?

Just curious, what metrics would you use to track how well your results are?

I took a Computer Science class decades ago that used that book as the core of the class material. I don't remember a single thing about that class now except that I hate that book and the professor bragging about designing cockpit instruments or some such. I learned more out of a cognitive psych class.

https://github.com/dcramer/mangodb

I use Xreal Air Pros for gaming and sometimes working if I'm mobile. Resolution isn't great, but I find them better than looking at a small-ish laptop screen or the Steam Deck screen. You can definitely read text on them, but maybe not small text. It also helps to have prescription inserts.

And now I'm curious if the Steam Frame allows inserts or fits well with glasses on.

It depends, the frameworks I've seen require a ton of boilerplate (ie. the things tools like create-react-app sets up for you) and have quite a learning curve. Using what you already know is simpler, and some of us know vanilla html, css, and js. It also very much depends on what you're making. Many sites don't necessarily need much interactivity or to constantly receive updated data.

Yeah, sounds like Tiddly Wiki or similar except with the need for a backend component.

Edit: actually it looks more like a library/framework to make such apps. And now I'm not sure if it needs a backend component or nodejs or not.

I think the answer to "classic mode" browsing is at the bottom of the site: web rings.

From what I've heard anecdotally, there have been a bunch more PRs and bug reports generated by AI. But I've also heard they're generally trash and just wasting the project maintainers' time.

It's hard to take a developer seriously when they don't document their code and think unit tests are a waste of time.

I always pick apart previous teams' work.. it's how I learn. I question most every decision because I'm curious why they made those decisions. And it lets me think about how I'd do it better. And yes, I know that many poor decisions are not necessarily the developer's fault. It could be bad specs, lack of time, etc.

For those of use that haven't use Angular, can you explain what this is doing? And what's it do that we can't already do with asyncio? Also, it's weird you have to call `asyncio.sleep(0)`. Seems like you should be able to `await count.set(5)`.

I did look at the repo, but I couldn't easily understand the use case and what exactly it's doing from examples alone.

Babies also aren't rectangles.. you could lay a row shoulder to shoulder, then do another row upside down from the first and their heads would fit between the heads of the first row, saving space.

Edit: it also doesn't account for the fact the moon is more or less a sphere, and not a flat plane.

Smaller instance can become big. Say you set up a small instance and invite your family. Then family members want to invite their family, or friends, or whomever. How do you manage that?

I think the answer is what we see with Mastodon, etc. and that's federated/distributed social networks.

I think you're missing the entire point of the article. It's attempting to classify a fictional, alien species with a real taxonomy (the only one we currently have available to us).

And yes, "just because they superficially resemble some arthropods in some features doesn't make them an arthropod".. but at the very beginning they point out they cannot use DNA sequences to help classify, so they are only using known physical characteristics.

That sounds great for moving fast, but not so great for sharing and keeping info about these projects. If/when someone quit, how would their projects get split up for other devs to maintain?

I skimmed it, but couldn't find what the "doodle theorem" is. It's only mentioned in the title.

Yeah I had no clue what this site was until reading the comments. I saw you could move things on the page around, then gave up because I had no idea what the point was. I didn't even find the github link until I saw your comment and decided to play around more.

I have Xreal glasses, and it's handy to be able to pin a window to a physical spot (well, direction in this case). I used that feature to have basically a virtual TV on my laundry room wall while I watched a video on how to fix my dryer as I was fixing it. But if I'm playing a game or watching other content, I don't want to have to focus on a single spot, so I have the window always in front of my face.

I think employers with remote employees can also do a better job in many cases with getting people to socialize. It's definitely easier to socialize when in the office, but several remote jobs I've had didn't really do much for this even though everyone was remote. I feel managers of remote employees need to do more online social events, have a water cooler chat, etc. in order to get team members to talk to each other. I'm currently on a team that doesn't do this well, and it's very isolating to barely know and talk to your teammates.

If they're shipping notebooks to production and having so many crashes, I'd question that they even know how to do Python.

That's what I don't get about this. Instead of writing code that may or may not be correct, it's writing tests that may or may not be correct.

I started playing for the first time a few days ago, and in VR. I've never really looked at any information about the game, so I pretty much went in blind. I'm having an absolute blast. Just this morning I got to watch my rescue ship get blown up, and enjoyed every second of it.

At my current employer we do allow this. It's handy for testing and not a big deal if we have users doing this to make multiple accounts (they don't gain anything by doing that). But at a previous job it was a bigger deal and we'd strip off the sub-address part because we were trying to match up email addresses across client sites (this was due to a bit of a shady thing the company was doing and part of the reason why I left).