Manticore

That's fair, and you raise good points. Thank you for sharing and explaining your perspective.

The perception of cycling in general is already negative, but I suspect it has less to do with idiots on bikes and more that bikes can't help but be in drivers' way. Yet I still hear NIMBYs actively fight against bike lanes because they think cyclists are entitled, and don't want to lose parking spaces to them, or get longer commutes if roads are converted to one-way. That's not something responsible cycling can fix; that's a direct result of car-centric culture being resistant to having a smaller slice of the pie.

EDIT: One thing to add. Human psychology is weird, and it treats being inside a car as like being in one's own house. 'Road rage' is a real phenomenon of drivers feeling 'territorial' in protecting 'their' space. It means theyre more reactive, more impulsive, and often more spiteful. No doubt in part because driving is a highly demanding activity mentally, especially at higher speeds, so adrenaline spikes easily.

By comparison, we don't get widespread 'supermarket rage' with our shipping trolleys, because it feels like a public space in a way 'inside of my car' doesn't (and we're slower and have time to think). And unfortunately, there isn't anything cyclists can do about that, either.

Also, correction: I didn't say all the things that piss off drivers are being done to make us safer. I said all the things that make us safer still tend to piss off drivers. Part of the Road Rage issue is that drivers get pissed off over any perceived infraction, regardless of context: even if their own inattention is at fault (like blaming people on the footpath for being in their way). Usually, the feeling passes In a couple seconds, but every now and then some asshole tries to run you off the road to 'make a point'...

Absolutely, but the same idiots that text while driving and microwave grapes can also buy bikes, so the existence of idiots on bikes cannot be assumed to represent a philosophy for cyclists at large (in your area, anyway). Are these things you see many cyclists doing? Or just things you've seen a cyclist do?

I see the concerns you've listed, and I agree they're not safe. But I know why people choose several of them, even if I personally don't do them. I have headlights and a reflective vest, but if your hobby bike doesn't and you need to get home after dark, you deal. If there's no safe space on the road, or the visibility is too poor, you deal.

Some of the other things you name, I haven't seen and cannot fathom why somebody would do such things. We're probably not from the same country (let alone area) so our cycling infrastructure will be different.

One of them I have done: riding the footpath in the opposing direction. I'm going at low speed so I can brake, but the only risk is of a bad driver being impatient - the same risk a mobility scooter, mailbuggy, skateboarder etc would have. And I do this if a) the road only has one path, and the otherside i would be exposed on the shoulder, or b) when my destination is close on the same side because it makes no sense to cross the road twice within 100m. Both are decisions I make to reduce my exposure to cars.

Cyclists break laws to reduce exposure to cars and their drivers. Even walking on a footpath, you're more likely to be killed by a car mounting the curb, or launching from a driveway than anything else. Car drivers are the apex predator of cyclists and pedestrians.

The reason cyclists avoid stopping is that our vehicles are pedal powered. If we lose all momentum, we take far, FAR longer to execute maneuvers. It means we spend longer in intersections, which are the MOST dangerous place for cyclists to be. Because of the cars.

And if we stop and wait, we need a far bigger gap than cars do. We cant inject fuel into our legs for a burst of speed. So drivers get impatient waiting for us to go and try to cut in front of us, turn in front of us, take any gaps we could've taken.

So the recommended action is to 'take the lane' (be in the middle of the lane so cars can't pass us) and then drivers are angry we're in the way and slowing them down and behave recklessly out of spite. Or politeness, sometimes drivers 'help' by stopping in the middle of intersections to create space, which also causes accidents.

Or we could be on the footpath, which means we now have to go much slower for safety and oh wait the biggest risk IS STILL CARS because drivers forget the footpath exist and launch out driveways at full speed without even looking. Cyclists, mobility scooters, skateboards; all irrelevant to the impatient driver.

So yeah, all the things that make using a light vehicle safer tend to make heavy vehicle users pissed off. I can do everything right, but if an impatient driver overtakes me in an intersection and collides with me, I'm still the one who ends up in hospital.

So... yeah. Being a defensive cyclists means minimizing interactions with drivers wherever possible.

What the alternative for heating? If it is AC, consider that much of the electrical grid is powered by air pollution anyway (especially coal), so the issue is at best deferred.

In urban areas, I believe the biggest cause of air pollution is vehicles, not woodsmoke.

Good lord. So glad my country has strict animal welfare standards for livestock. Uncomfortable that we still import and slaughter pigs from countries without those standards. (And yes, we import-and-slaughter because we don't import pork itself. We do however, allow the import/export of live animals, so international trade buys our sheep for 'breeding', and sell us their pigs for 'NZ-made pork'. I suppose it at least enforces abattoir health standards..?)

We probably don't have enough user traffic to give people the specific help they need. Certainly not compared to something like StackOverflow, which is already what you're describing.

The issues with generalised user-to-user programming help (esp re: StackOverflow) is that an increasing number of communities are doing this in closed-off areas like Slack and Discord, where their support is not indexed or searchable. Users running into the same problems are struggling to find each others' answers. Creating yet another community that's separated from the internet at large exacerbates this problem.

Man, I used to really like browsing the stuff at ThinkGeek. Even bought a few things. Now that it's owned by... I wanna say GameStop?... it's ceased to be interesting to me. I liked things like the laundry basket that looked like a radioactive barrel, the shower gel that looks like a blood bag... that kind of light-hearted novelty stuff. But the new owner just gutted all the interesting content, and it's just all IP collectables now.

It's been long enough I forgot bout ThinkGeek. Damn. Wish something like it were still around.

• "progress on [1], fixed linting [2]"
• "[1] completed, setup for [2]"
• "[3] and [4] completed"
• "fixed formatting"
• "refactoring [1] and [2]"
• "fix variable typos"
• "update logic in [2]"
• "revert package.json and regenerate package-lock"

All my commits have comments. I generally commit after completing a 'block' objective, a describe what that was but in very simple terms mostly in regards to the file/section with the most significant logic changes. I don't always specify the file if I did tiny typos/linting/annotation across a bunch of them, because the logic is unaffected I know that the differences will be visible in the commit history.

My weakness is that I don't do it often enough. If I'm working on [2] for several hours, I'll only commit when I consider it minimally-viable (completed 2), or when moving between machines ([further] progress on 2). And I have a bad habit of not pushing every time I commit, just at the end of the day or when moving between machines (though a messy rebase hopefully made that lesson stick), or if somebody else on the team wants to review an issue I'm having.

I think that's a bad faith interpretation to imply that one eats animals exclusively because it being 'animals' is the point. Most people don't think about it, their priority is making their daily life as simple as possible. They just eat whatever tastes good and is easy to get. And the people pushing for eating insects are thinking about it; they just have different priorities; they're trying to make environmentally-sustainable food easier to get.

Insects are still a far better choice for protein. They don't take remotely the amount of land or water that soy crops do, and they can be grown in areas of the world that don't have as much freshwater. They can be fed off scraps and organic material that are waste to us. They also have a high return yield; they're not being lost to droughts/weather/pests at the rate crops (especially organic) are. I'd posit that an insect-inclusive diet is probably more environmentally-friendly than the modern vegan diet is.

Humans are evolved omnivores. It's both possible and noble to have an organic and herbivorous diet that meets your basic needs, but it's difficult, often inaccessible, expensive; and it takes up huge amounts of land to grow the kind of crops needed (especially if much of them are lost to pests). Soy demands a lot of water, and avocados have been priced out of reach of the impoverished Central Americans they used to cheaply feed. Whether plant or animal, we are only alive by consuming life. There is no diet without some harm to somebody somewhere. Most vegan diets are too expensive (or unavailable), and are part of the deforestation for soy plantations overseas.

Ultimately now that principles have become a part of how we consume (and not just necessity, availability, effort etc), any philosophy requires compromise. If one's primary concern is freshwater, the carbon cycle, deforestation for cropland, nutrition density, local food-chain, animal suffrage, animal consent, organic, local-grown, seasonal, etc... It's not possible to follow them all, and it's not reasonable to expect everybody choose a single specific one.

I have a preference towards attainable and environmentally-sustainable eating, which means that eating crickets (and mushrooms, yum) is less harmful ecologically than eating soy (deforestation, water), and far less harmful than cattle (magnitudes worse than any other livestock). I also avoid palm oil products (deforestation). I don't disagree with any vegetarians or vegans who chose other principles; it's excellent that humans are becoming increasingly mindful of what we choose to eat. We just have different priorities.

AI can code assist; it's quite helpful for that. Predictive text, learning a less familiar language, converting pseudo, etc.

But it couldn't possibly replace senior developers long-term. It just looks new and exciting, especially to people who don't truly understand how it works. We still need to have human developers capable of writing their own new code.

1. AI is entirely derivative, it's just copying the human devs of yester-year. If AI does the majority of coding then it becomes incapable of learning, thus necessitating human coders anyway. It also is only going to generate solutions to broad-strokes problems that it already has in its dataset, or convert pseudocode into functional code (which still requires a dev know enough to write pseudo).

2. It also currently has no way of validating what it writes. It's trying to replicate what our writing looks like contextually, it doesn't comprehend it. If it ever starts training on itself as it ages, it will stagnate and require human review, which means needing humans that understand code. And that's not including the poor practices it will already have because so many devs are inconsistent about things like writing comments, documentation, or unit testing. AI doesn't have its own bias but it inevitably learns to imitate ours.

3. And what about bug-testing? When the AI writes something that breaks, who do you ask for help? The AI doesn't comprehend the context of the code its reading if you paste it back, it doesn't remember writing it. You need people who understand how the code works to be able to recognise why it might be breaking.

AI devs are the fast food of coding. It will never be as good quality as something from an experienced professional. But if you're an awful cook, it still makes it fast and easy to get a sad, flat cheeseburger.

I've worked with devs who are the equivalent of line cooks and are also producing sad, flat cheeseburgers: code of poor quality that still sees production because the client doesn't know any better. IMO, those are the only devs that need to be concerned, because those are the ones that are easy to replace.

If AI coding causes any problems within the job market for devs, it will be that it replaces graduate/junior developers so well that fewer devs get the mentoring or experience to become seniors, and the demand for seniors will rack up significantly. It seems more likely that developers will split into two separate specialisations, not that our single track will be replaced.

Absolutely. I hear Witcher 3 is good, and I believe that it is... but after playing it for 5 hours and feeling like I got nowhere, the next day I just genuinely didn't feel like playing it as I'd felt very little character progress, and zero story progression.

Games are continuing to market towards younger people - especially kids - with spare time to burn. They consider their 120+ hour playtime to be a selling point, but at this point that's the reason I avoid them. If I'm going to play for an hour or so at the end of my day, I want that game to feel like it meant something.

I prefer my games to feel dense, deliberately crafted, minimal sawdust padding. I've enjoyed open-world in the past but the every-increasing demand for bigger and bigger maps means that most open-world games are very empty and mostly traversal. Linear worlds aren't bad - they can be crafted much more deliberately and with far more content because you can predict when the player will see them.

Open worlds that craft everything in it deliberately are very rare, and still rely on constraints to limit the player into somewhat-linear paths. Green Hell needs a grappling hook to leave the first basin, Fallout: New Vegas fills the map north of Tutorial Town with extreme enemies to funnel new players south-east.

And what really gets me is that with microtransactions, the number of games that make themselves so big and so slow that they're boring on purpose, so that they can charge you to skip them! Imagine making a game so fucking awful that anybody buying a game will then buy the ability to not play it because 80% of the game is sawdust: timers, resource farming, daily rotations, exp grinding. Fucking nightmare, honestly.

Maybe - certainly generations always assume anything that younger people do is somehow worse than what they did, and the digital landscape is a part of that. When writing slates became accessible, the old guard complained it was 'lazy' because they didn't have to remember it anymore. Any music popular among teenagers (especially teenage girls) is mocked as foolish, cringe, etc.

But I suspect like most hobbies, it's mostly the following that determine our assumptions:

• history of the media and its primary audience (digital mediums are mostly embraced by youth; video games initially marketed to young children)
• accessibility; scarcity associated with prestige (eg: vital labour jobs are not considered 'real jobs' if they don't require a degree)
• the kind of people we visibly see enjoying it (we mostly see children, teenagers, and directionless adults as gaming hobbyists)

You're right, reading is not somehow more or less moral than video games. Many modern games have powerful narrative structure that is more impactful for being an interactive medium. Spec Ops: The Line embraces the players actions as the fundamentals of its message. Gamers are hugely diverse; more than half the US population actually plays games at this point, and platforms are rapidly approaching an almost even gender split. (Women may choose to play less or different games, and hide their identity online, but they still own ~40% of consoles.)

Games as a medium is also extremely broad. I don't think you could compare games to 'watching anime' for example, so much as 'the concept of watching moving pictures', because they can range from puzzles on your phone, to narrative epics, to grand strategies, to interactive narratives.

So a better comparison for video games isn't 'reading books' so much as reading in general, and are you reading Reddit, the news, fiction, or classic lit? What does your choice of reading mean?

So for your suggested hobby of 'reading books', one might assume any (or all) of the following:

• they are intelligent and introspective (or pretentious),
• they are educated (or think they're better than you),
• they are patient and deliberate (or boring),
• they'd be interesting to discuss ideas with (or irrelevant blatherers).

Assuming everybody who reads is 'smart' is as much an assumption as assuming everybody who games is 'lazy', and the assumptions you make about the hobby are really assumptions you make about the typical person who chooses it. It may not be a guarantee, but its a common enough pattern.

TLDR: Ultimately? I think books have inflated status because it's seen as a hobby for thinkers; people picture you reading Agatha Christie (but you could be reading Chuck Tingle, or comic books). Games have deflated status because it's seen as a hobby for people who consume mindlessly - the people who know what games are capable of are the ones playing them, too.