1. Sometimes
2. Sometimes
3. Both

I have for a bit, decided to stick to MD because of its accessibility to my non-tech collaborators, it is easier for them to install Obsidian, and MD is very well-known.

Aside from that, I am planning to use Pandoc to process my sources into other deliverables: web pages, PDFs etc. I am myself still learning this ecosystem, and markdown (in my experience) just enjoys more visibility.

Truth be told, I did not have any exposure to Org Mode prior to looking it up for knowledge management, so all of the above might be my “little duck” brain speaking.

Bevy, specifically because it is an ecosystem of libraries. I tried UE3/4, Unity and Godot, and I’ve always found the complexity of tooling and amounts of options available completely overwhelming. Not to mention, that most of these tools and options funnel the developer into very specific and opinionated ways of doing things.

By contrast, Bevy is just a Rust crate, and it is modular - I can connect only those plugins and functions I really need. If I am ever confused by some function, or a type, I just press “gd” and my nvim will show the definition of this function or type - it feels refreshingly simple and seamless in comparison with the enormity and complexity of Unreal or Unity. At any point in time I am staring at my code, I only see things that are relevant to the problem, and nothing else.

I can bring my own tooling (editors, analysis tools, asset pipelines etc.), projects are easy to build and automate, - it is pure bliss.

The absence of an editor allows me to hook up whatever I want: LDTK, Trenchbroom, even Unity could be used as a scene editor. There is virtually no vendor lock-in with dependencies either. Don’t like Rapier as your physics engine - easy-peasy, you can use Avian, or something else, or something custom, or nothing at all. Don’t like Bevy UI - no worries, there is Egui, multiple integrations with other UI frameworks, you can even use Typst layouts for your menus if you so desire.

Right now I am working on a literate game with a friend: our sources are markdown files with bits of code in them. Our automation compiles markdown to Rust sources and then builds the game, potentially along with the devlogs and some other auxiliary artifacts.

My non-technical partner contributes to the repo freely, treating it as an Obsidian vault, - in our team there is no distinction between technical writing and development, our game design document and source code are literally the same thing. This approach has removed loads of roadblocks and allows us to safely and controllably accumulate knowledge, before distilling it into a working game.

It wasn’t trivial to set up, but it wasn’t overly complicated either - good luck replicating this set up with Unity or Unreal though.

Indeed it is! That is why we are blessed to have its power obscured by an incomprehensible CLI, aside from a few most common use cases. Still very worth it though.

If you work a lot with plain-text files (markdowns, office documents CSV etc.) try learning Git. It is a version control tool - it keeps timestamped versions of your documents, so if you edit something wrong, or delete a wrong file you can bring it back by “checking out” a previous version.

It’s a software development tool originally, so learning it might be daunting for a lot of folks - fear not, download a graphical Git client app and look up some tutorials.

I promise once you get the hang of it, it will be hard to imagine doing anything without it.

One of those tools I wish were more popular among people who are not into software/engineering.

Uncharted, especially the final installment. On normal and higher difficulty dealing with the enemies becomes a bit of a chore: they force you to hide a lot, as well as waste entire clips of ammo on a single guy. On easy the game becomes forgiving enough food you too start pulling off cool stunts: swinging on ropes, shooting during a climb/jump, etc.

It’s just more fun on easy.

Thanks, but it wasn’t so bad. I have learned exactly two things from that conversation: 1 - one can brake a dick 2 - some injuries have fascinating stories attached to them

Overall, I wouldl rate this experience 8.5/10 - very enlightening and only mildly inappropriate.

Sausage was fine.

I grew up in a family of medical doctors, it came with its own set of similar challenges. Every problem discussion always revolved exclusively around solutions or practical harm reduction. I suspect God forbade the doctors from talking just for emotional support.

Every problem I ever had (completely normal ones included) was medicalized and pathologized, neatly classified and wrapped in a set of actionable instructions: “this is how you get better, this is how you allow it to get worse”.

I still remember coming home from school and sitting down at the dining table, eating my sausages with buckweed, while my dad, mom and older sister discuss methods and techniques to install a urethral catheter in a person with a broken phallus.

It wasn’t good or bad, it was just weird I guess. Hey, at least I am not scared of blood/trauma/desease, and in a some cases I believe it allowed me to stomach helping people in need, when other people would turn away out of disgust or disturbance.

Outer Wilds, if you haven’t played already. Obligatory warning to avoid spoilers like your life depends on it, go in completely blind if possible.

Stangenzirkel!

Cactus - Cacti Sarcophagus - Sarcophagi Octopus - Octopi Campus - Campi Mouse - Mice House - Hice

I am not a professional educator, but in general I think it is worth to start with basic computer literacy: identifying parts of a PC, being able to explain their overall functions, difference between hardware and software, and what kinds of software a computer can run (firmwares, operating systems, user utilities etc.). This would also be a perfect time to develop practical skills, e.g. (assuming you are a normatively-abled person) learning to touch-type and perform basic electronics maintenance, like opening your machine up to clean it and replace old thermal compounds.

After that taking something like “Operating systems fundamentals” on Coursera would be a great way to go on.

It really depends on your goals, resources and personal traits, as well as how much time and energy you can spare, and how do you like to learn. You can sacrifice and old machine, boot Ubuntu and break it a bunch of times. You can learn how to use virtualization and try a new thing every evening. You can get into ricing and redesign your entire OS GUI to your liking. You can get a single-board computer like RaspberryPi and try out home automation.

I might have phrased my thought too bluntly: I never intended to frame the problem as any sort of moral failure on the end users’ part. I view this as a failure of our educational institutions.

In my mind, preferring to spend time on (e.g.) MS Office in class, instead of teaching proper computer literacy, is like trying to teach meal-prep with Philips air fryers instead of teaching how to cook.

I hear you, and I too feel like it might be just my aspi-nerdiness speaking, but the same argument could be said about any subject that is considered fundamental to highschool ed. We don’t skip on philosophy, sciences, languages and arts just because they seem less applicable than math or econ, or because “it’s impossible to learn everything”.

Our civ made progress, having invented a fundamentally new tech that is accessible to everyone and now underpins everything. Allowing people to acquire the basic literacy needed to interface with this tech sustainably is the bare minimum we should be doing. I am not talking about turning kids into cyber wizards - just getting their computing up to a level that allows them to make relevant informed choices.

We learn and teach inferior personal computing practice, and most people don’t realize how much they are missing.

The vast majority of people outside of enthusiast circles have absolutely no idea what a personal computer is, how it works, what is an operating system, what it does, and how it is supposed to be used. Instead of teaching about shells, sessions, environments, file systems, protocols, standards and Unix philosophy (things that actually make our digital world spin) we teach narrow systems of proprietary walled gardens.

This makes powerful personal computing seem mysterious and intimidating to regular people, so they keep opting out of open infrastructures, preferring everything to come pre-made and pre-configured for them by an exploitative corporation. This lack of education is precisely what makes us so vulnerable to tech hype cycles, software and hardware obsolescence, or just plain shitty products that would have no right to exist in a better world.

This blindness and apathy makes our computing more inaccessible and less sustainable, and it makes us crave things that don’t actually deserve our collective attention.

And the most frustrating thing is: proper personal computing is actually not that hard, and it has never been more easy to get into, but no one cares, because getting milked for data is just too convenient for most adults.

I find the lack of proghead representation quite disturbing. There are dosens of us!

Y’all just have no idea how complicated the process is. In 2004 it was OK to just “ship a working game”, - in 2023 you have to include all of the software stacks you have partnering contracts with, deploy an entire cloud infrastructure to deliver updates and short purchases, design and launch automated targeted ads campaigns, pay union-busting lawyers, accommodate for all the “fun” senile execs want to put in the game, pay handsome compensation to these senile execs, pay more lawyers to bury workplace toxicity-related incidents. At the end of the day, you have to sustain the company somehow when 95% of your workforce goes on a sick leave after a 3-month-long crunch period. All of that takes money, time and effort. And y’all don’t get a lot of time in-between autumn release windows.

Hey, we’ve been at it for 20 years, and we have just managed two months of 16-hour workdays without anyone dying, it looks like it might be one of those projects we actually manage to ship - what an important internal milestone!

PS: I don’t actually work at Ubisoft, I love my life too much - this entire comment is a satire

Number is a simple abstraction: an exercise in conceptualizing a particular part of human experience, - the amounting of stuff and the relations of various amounts.

Its utility shines the most in the practice of measurement: determining, manipulating and comparing the amounts of stuff.

Numbers also useful as a stepping stone in a learning journey, allowing an individual mathematician to transition to using other, more powerful abstractions (like variables, polynomials, sets, functions, vectors, fields, etc.).

Numbers are magick!

Humor can be read in various ways, the author’s public statements and policy paints a cringey picture, unfortunately. I am not a trans person myself, so the tastefulness of this humor is hard for me to judge. Still, this particular episode has left a bad taste, even if the show as a whole cracks me up. Doesn’t help that I am growing into a huge Matt Berry fan

I used to love this show until that one transphobic episode. After watching that I looked up the main show writer and learned that he is huge piece. Such disappointment.

As I guy, I relate strongly. I think that’s because of all the ridicule I used to receive for things I liked as a kid. If I share my music playlist with you, that means a lot as well - music is very intimate.