• 0 Posts
  • 63 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle
  • 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.




  • 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.



  • My first encounter with Linux was in 2007, I installed Kubuntu Gutsy Gibbon on my dad’s computer out of curiosity - I was intrigued by a notion of free OS you can deeply customize.

    I have spent countless hours fiddling with the system, mostly ricing (Compiz Fusion totally blew my mind) and checking out FOSS games.

    Decades later I switched to Linux full-time. After 12 years of daily driving OS X and working as a developer, I wanted a customizable and lean OS that is easy to maintain and control. Chose Arch, then Nix, havent looked back ever since.





  • I’ve been using Git professionally as a software developer for 15 years, and I think it sucks quite hard. There is always a dosen ways to do the same thing, it occupies tons of hardware space, it’s log is unstructured data that has to be parsed. Git CLI is an incomprehensible mess of bloat and misnomers, so no matter what team/project you are working on, there is always going to be 1-5 Git commands they’ll tell “you are NEVER supposed to use”.

    I’ve completed my courses on Git, I’ve worked with CI/CD, onboarded younger developers, read “Git Koans”, and I haven’t seen even a theoretically convenient VCS until someone showed me Pijul.

    Git is mess, it sucks that we are stuck with it, and every time someone says it’s the best VCS we have, it saddens me.





  • The future’s wasteland will be covered by bodies of web stalkers who were naive enough to get tricked by mid-2010s shitposts.

    “Turns out they never used this to make their metal cutlery darker - who would have thought the ancients were so casually cruel?”

    “After months of research we have concluded, that despite all their technical achievements, the ancients never figured out, what does the fox say”

    “Today prof. Drobyshevsky is going to tell us about their newest work in XXI cent. anthropology - what is ‘streamer dent’ and why do we have such long heads 2300 years later?”

    “Ass, coochie and the rich - dietary practices of homo sapiens in the age of over-production”




  • Hundun@beehaw.orgtoScience Memes@mander.xyzLPT Do it.
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    4 months ago

    Why on Earth would you curse yourself with MS Office anyway, especially if writing docs is your professional responsibility?

    Why not use Git+Markdown+Pandoc, have your copy, data and layout separate?

    I understand that a lot of istitutions/companies impose stylistic/technical requirements for docs and publications, - still doesn’t mean you gotta stay married to the worst tooling.