petster: Pet owner social networks (2016)
A network of friendships among users on catster.com and dogster.com. Node represents a user, and edge exists if two users self-identify as friends on either website. The dogster/catster network also contains family links between dog and dog, cat and cat, as well as dog and cat.
This network has 623766 nodes and 15699276 edges.
Tags: Social, Online, Unweighted
"‘It really is possible to be zero waste’: the restaurant with no bin"
#Restaurants #Food #ZeroWaste
To add a single example here (feel free to chime in with your own):
Problem: editing code is sometimes tedious because external APIs require boilerplate.
Solutions:
- Use LLM-generated code. Downsides: energy use, code theft, potential for legal liability, makes mistakes, etc. Upsides: popular among some peers, seems easy to use.
- Pick a better library (not always possible).
- Build internal functions to centralize boilerplate code, then use those (benefits: you get a better understanding of the external API, and a more-unit-testable internal code surface; probably less amortized effort).
- Develop a non-LLM system that actually reasons about code at something like the formal semantics level and suggests boilerplate fill-ins based on rules, while foregrounding which rules it's applying so you can see the logic behind the suggestions (needs research).
Obviously LLM use in coding goes beyond this single issue, but there are similar analyses for each potential use of LLMs in coding. I'm all cases there are:
1. Existing practical solutions that require more effort (or in many cases just seem to but are less-effort when amortized).
2. Near-term researchable solutions that directly address the problem and which would be much more desirable in the long term.
Thus in addition to disastrous LLM effects on the climate, on data laborers, and on the digital commons, they tend to suck us into cheap-seeming but ultimately costly design practices while also crowding out better long-term solutions. Next time someone suggests how useful LLMs are for some task, try asking yourself (or them) what an ideal solution for that task would look like, and whether LLM use moves us closer to or father from a world in which that solution exists.
Series C, Episode 06 - City at the Edge of the World
DAYNA: You should have killed them.
AVON: Probably.
CALLY: They could sleep through a war.
TARRANT: That's good, because if it is Bayban down there, a war is what we'll have.
https://blake.torpidity.net/m/306/416
One of the problems with vibe coding is that the hardest part of software engineering is not writing the code, rather it's *choosing* what to code, and designing the system (and, later on, maintaining the code/operations/etc)
The barriers and investment cost to writing code is itself a *desirable* aspect of software engineering because it forces you to make careful, good choices before you invest in building something
Because the majority of the time spent writing, say, curl,…
Real-Time Agile Software Management for Edge and Fog Computing Based Smart City Infrastructure
Debasish Jana, Pinakpani Pal, Pawan Kumar
https://arxiv.org/abs/2506.12616
I'm now with my buddy Shaun who sadly recently lost his girl Dotty. I looked after the two of them this time last year, so this time it's just me and the old boy. I've still got my work cut out for me though: Shaun normally likes to walk about 15km per day!
#Greyhounds #AdoptDontShop
I'm now with my buddy Shaun who sadly recently lost his girl Dotty. I looked after the two of them this time last year, so this time it's just me and the old boy. I've still got my work cut out for me though: Shaun normally likes to walk about 15km per day!
#Greyhounds #AdoptDontShop