home.social

#tradeoffs — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #tradeoffs, aggregated by home.social.

  1. When tradeoffs aren't visible, ppl may choose a path without fully understanding what they’re giving up.

    Read the full article: Tech Leadership: Make Tradeoffs Visible
    lttr.ai/Aqcqs

    #TechLeadership #Tradeoffs #StaffPrincipalEngineer

  2. "Decision-makers who aren’t technically savvy may be attracted to the promise of new technologies without fully grasping the risks." lttr.ai/Aqcqr

    #TechLeadership #Tradeoffs #StaffPrincipalEngineer

  3. Ah yes, the groundbreaking revelation that programming languages have *tradeoffs* 🙄. Let's spend the next 1,000 words rehashing this ancient wisdom, with a sprinkle of personal anecdotes for flavor. Spoiler alert: no one emerges victorious in this epic battle of #Go vs. #Rust vs. #Zig 🏆🤡.
    sinclairtarget.com/blog/2025/0 #programminglanguages #tradeoffs #techhumor #epicbattle #HackerNews #ngated

  4. Ah yes, the groundbreaking revelation that programming languages have *tradeoffs* 🙄. Let's spend the next 1,000 words rehashing this ancient wisdom, with a sprinkle of personal anecdotes for flavor. Spoiler alert: no one emerges victorious in this epic battle of #Go vs. #Rust vs. #Zig 🏆🤡.
    sinclairtarget.com/blog/2025/0 #programminglanguages #tradeoffs #techhumor #epicbattle #HackerNews #ngated

  5. Ah yes, the groundbreaking revelation that programming languages have *tradeoffs* 🙄. Let's spend the next 1,000 words rehashing this ancient wisdom, with a sprinkle of personal anecdotes for flavor. Spoiler alert: no one emerges victorious in this epic battle of #Go vs. #Rust vs. #Zig 🏆🤡.
    sinclairtarget.com/blog/2025/0 #programminglanguages #tradeoffs #techhumor #epicbattle #HackerNews #ngated

  6. Ah yes, the groundbreaking revelation that programming languages have *tradeoffs* 🙄. Let's spend the next 1,000 words rehashing this ancient wisdom, with a sprinkle of personal anecdotes for flavor. Spoiler alert: no one emerges victorious in this epic battle of #Go vs. #Rust vs. #Zig 🏆🤡.
    sinclairtarget.com/blog/2025/0 #programminglanguages #tradeoffs #techhumor #epicbattle #HackerNews #ngated

  7. @innocence I’m not sure how all the apps and in your are . I’m by no means criticizing you. I do get that in the grand scheme of things there is always a level of

  8. "Breaking News: 🎉 Developers discover that coding is hard! 🚨 In a groundbreaking revelation, we learn that every decision is a tradeoff – who would've guessed? 🙄 Next up, find out why adding more code might be necessary... because apparently we needed an article to tell us that. 🤦‍♂️"
    programmersstone.blog/posts/wh #codinghard #tradeoffs #developernews #programminghumor #techrevelations #HackerNews #ngated

  9. "Breaking News: 🎉 Developers discover that coding is hard! 🚨 In a groundbreaking revelation, we learn that every decision is a tradeoff – who would've guessed? 🙄 Next up, find out why adding more code might be necessary... because apparently we needed an article to tell us that. 🤦‍♂️"
    programmersstone.blog/posts/wh #codinghard #tradeoffs #developernews #programminghumor #techrevelations #HackerNews #ngated

  10. "Breaking News: 🎉 Developers discover that coding is hard! 🚨 In a groundbreaking revelation, we learn that every decision is a tradeoff – who would've guessed? 🙄 Next up, find out why adding more code might be necessary... because apparently we needed an article to tell us that. 🤦‍♂️"
    programmersstone.blog/posts/wh #codinghard #tradeoffs #developernews #programminghumor #techrevelations #HackerNews #ngated

  11. "Breaking News: 🎉 Developers discover that coding is hard! 🚨 In a groundbreaking revelation, we learn that every decision is a tradeoff – who would've guessed? 🙄 Next up, find out why adding more code might be necessary... because apparently we needed an article to tell us that. 🤦‍♂️"
    programmersstone.blog/posts/wh #codinghard #tradeoffs #developernews #programminghumor #techrevelations #HackerNews #ngated

  12. > Moving from a physical data centre to the cloud also has some trade-offs; for instance, the cost will be approximately five times higher than running the system in the data centre; with initial data, it’s not unlikely the annual cost may be up to 2,000,000 USD.

    crossref.org/blog/weve-migrate

    Could be worse, right? cc @bert_hubert
    #TradeOffs #cloud

  13. What's this? An abstract syntax tree? A bytecode? What does that even mean anymore?

    Next Wednesday, Octave is going to explore those questions in his ICOOOLPS presentation.

    Our draft paper is online already: 2025.ecoop.org/details/ICOOOLP

    #interpreter #design #tradeoffs

  14. Explore the transformative potential of Generative AI and the role of GPUs in accelerating innovation. Learn about the tradeoffs involved and the importance of considering the broader impact. #GenerativeAI #GPUs #Innovation #DeepLearning #Efficiency #Tradeoffs #AI
    medium.com/@sanjay.mohindroo66

  15. CW: #LaTeX, #Emacs, and #pronouns

    It probably violates a lot of the usual conventions of #LaTeX #style but I can now \usepackage{catarcher} and have a quasi-nice interface to separating a character (or place, or organization) within a story from their function within it.

    Yes, you are allowed to think of a feline with a bow and arrow. There may be a #ttrpg motivating some of this. Er what, the focus group hates poncy elf men? We can fix that!

    \MakeNPC{protagonist}{Kragfeet}{Borhona}{f}{surname-first}
    \InductNPCIntoSpecies{protagonist}{dwarf}

    And later in the document...

    Upon \NPCpossessiveadjective{protagonist} person, \NPCfullname{protagonist} bears a letter written in the \NPCspeciesadjective{protagonist} language.

    There are shorter forms of the #macros that end up boiling down to unique eyesore macros that yield fixed strings after all the #recursive expansion is said and done. At the bottom of it all is some games with \expandafter\def and \csname ... \endcsname that build up a bunch of keyed lookup tables.

    The *roff equivalent (including #groff and #heirloom doctools) is more straightforward thanks to the .ds request. You could use macros in the body of the document but predefined strings fit the visual flow better.

    .MakeNPC protagonist Kragfeet Borhona f surname-first
    .InductNPCIntoSpecies protagonist dwarf

    Upon \*[paprotagonist] person, \*[fuprotagonist] bears a letter written in the \*[spadjprotagonist] language.

    In either case, you refer to the character by their function within the document. And when the focus group inevitably changes their mind again, you'll only need to go to one place to change just about every reference in the document. You still must proofread everything to ensure it makes sense after the changes. (Sorry.)

    Cue #bikeshedding about whose eyesore macros are less ugly.

    Can I write an entire document in it? Yes. Is it worth it? It yields attractive output. Does it do so with tolerably little tearing of hair and gnashing of teeth? I don't know yet. #Emacs and #orgmode help in some ways but hinder in others. Aren't #tradeoffs fun?

  16. @ctietze A lot of my target use case hinges around this: how can I change the attributes of a character (name, gender, species, etc.) in a document without doing a potentially-catastrophic search-and-replace across the entire document? Preserving the character’s function and role within the work despite changing almost anything else about them.

    In the #troff world you can do this pretty easily with the .ds macro to build a library of direct string substitutions.

    \*[fuHERO] overcomes \*[paHERO] foe!

    Perhaps there is a more native way to do it in #LaTeX than I have found; I haven’t researched it thoroughly. You can definitely set up data structures in #Emacs #lisp and pick out the attributes with #orgmode macros.

    {{{fu(hero)}}} overcomes {{{pa(hero)}}} foe!

    Here using `fu` for “full name” and `pa` for “gendered possessive adjective” (his/her/their/its).

    In favor of #troff is the lower-level stuff. You can use macros to define strings en masse and then override individual choices for particularly weird characters. The downside is that you end up building up a library of macros to supplement your chosen package so that the main body of your document looks more like semantic than physical markup. And you probably need a #Makefile to assemble anything beyond a trivial document.

    In favor of #LaTeX is mostly the higher-level stuff, and the short distance to semantic markup. #orgmode shortens this even further, and you can build your document in a single command (C-c C-e l p). But now the low-level stuff becomes annoying.

    Perhaps with more research I can find the appropriate packages, but that may obviate the benefits of #orgmode altogether. Hopefully a well-fitting puzzle piece is out there, somewhere…

    It’s all #tradeoffs but it’s not for paid work so I only have to worry about whether or not it works for me.

  17. @ctietze A lot of my target use case hinges around this: how can I change the attributes of a character (name, gender, species, etc.) in a document without doing a potentially-catastrophic search-and-replace across the entire document? Preserving the character’s function and role within the work despite changing almost anything else about them.

    In the #troff world you can do this pretty easily with the .ds macro to build a library of direct string substitutions.

    \*[fuHERO] overcomes \*[paHERO] foe!

    Perhaps there is a more native way to do it in #LaTeX than I have found; I haven’t researched it thoroughly. You can definitely set up data structures in #Emacs #lisp and pick out the attributes with #orgmode macros.

    {{{fu(hero)}}} overcomes {{{pa(hero)}}} foe!

    Here using `fu` for “full name” and `pa` for “gendered possessive adjective” (his/her/their/its).

    In favor of #troff is the lower-level stuff. You can use macros to define strings en masse and then override individual choices for particularly weird characters. The downside is that you end up building up a library of macros to supplement your chosen package so that the main body of your document looks more like semantic than physical markup. And you probably need a #Makefile to assemble anything beyond a trivial document.

    In favor of #LaTeX is mostly the higher-level stuff, and the short distance to semantic markup. #orgmode shortens this even further, and you can build your document in a single command (C-c C-e l p). But now the low-level stuff becomes annoying.

    Perhaps with more research I can find the appropriate packages, but that may obviate the benefits of #orgmode altogether. Hopefully a well-fitting puzzle piece is out there, somewhere…

    It’s all #tradeoffs but it’s not for paid work so I only have to worry about whether or not it works for me.

  18. There’s nothing like a #disasterrecovery #test to point out the glaring holes in your tech stack, and when they collide with #licensing constraints, it’s a real #hootenanny of #tradeoffs.

    You consider bizarre things like using #deprecated #container images of the open-source unlicensed community version. And, succeed or fail, documenting what you did so you can flog the developers with the #technicaldebt they’ve been ignoring for too long.

    You can have your DR exercise, but it’ll cost you…

  19. No, I do not want to stack more #kludges on top of 20+ years of #technicaldebt to get this working. All over the file system, all different users and groups. Things were less standard then. Things are more standard now. I’m tempted to suggest that we thoroughly #refactor but the application is supposedly on its way out. We need a discussion about #tradeoffs.

    All this to avoid some cryptic error about shared memory permissions. I shall #nope out of #debugging it in its current form.

  20. Emerging from a few days of hyper-focus is hard. There is the attention crash (NOTHING is interesting anymore!), physical exhaustion (sleep debt is REAL), and piles of neglected admin work that has to be dealt with NOW (annual report X was due a month ago).

    But github.com/ktoddbrown/SoilDRaH now has a wiki in the works and the data harmonization is drafted! Oh and some clever paired treatment analysis is VERY satisfying. #tradeoffs #AcademicLife

  21. @georgetakei

    This is the fastest way to lesrn how bad the bruise is.

    Though, you just added another day for it to heal.

    #TradeOffs

  22. Now available Ahead of Print! "Population Dynamic Consequences of Context-Dependent Trade-Offs across Life Histories" by Louis Bliard, Maria Paniw, Dylan Z. Childs, and Arpat Ozgul: journals.uchicago.edu/doi/10.1

    #populationDynamics #lifehistory #heterogeneity #covariation #tradeoffs

  23. more clothes, worse quality, washing less frequently < less clothes, better quality, washing more often
    #tradeoffs

  24. "A compromising mindset? How citizens evaluate the trade-offs in coalition politics"

    ejpr.onlinelibrary.wiley.com/d

    "we show that European citizens understand that compromise is essential for democratic governance and that they, holding everything else constant, prefer political parties that express a willingness to compromise"

    (Green-pedersen & Hjermitslev, 2023)

    #democracy #tradeoffs

  25. Ever dreamed of a flexible solution?

    A solution where everything can be implemented quickly? Best configured? A solution that is ready for whatever the future may bring?

    Dream on.

    Not that we misunderstand each other: You can get flexibility. But it comes at a price: effort and complexity. As so often in life, it's all in the dose.

    Too much flexibility can freeze a project in its tracks.

    🧵 #softwarearchitecture #flexibility #tradeoffs #nodreaming

  26. cbs19news.com/story/49854253/l Welcome to the world you little #cville hotel. This was a tough call on the PC to allow hotel use in a historic hotel being used as crumbling low cost housing near jobs and services. I still believe we need low cost housing near jobs and services, but I also see some benefit to allowing hotels to be hotels. #tradeoffs #housing

  27. "There is a price tag for anything you want to achieve in life. Every single thing you want is an output that requires certain inputs to buy or earn. There's a 'list price' (actual, direct price to pay for the thing you want) and a 'real price' (List Price, plus the hidden, indirect price in the form of the tradeoffs and opportunity cost of the pursuit)." — Sahil Bloom — — — #SahilBloom #quote #quotes # #listprice #tradeoffs #realprice #achievement #accomplish

  28. @CarlG1VIF #JT65 was responsible for my best distance/power ratio to date. Despite being such close cousins, and knowing the approximate #tradeoffs between the two modes, I somehow find #FT8 to be less compelling. Technically impressive, nonetheless. It’s never fun to discover the #bandwagon (#pun at your discretion) has moved out from under you.