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

help-circle

  • That’s been my experience so far, that it’s largely useless for knowledge based stuff.

    In programming, you can have it take “pseducode” and have it output actionable code for more tedious languages, but you have to audit it. Ultimately I find traditional autocompletion just as useful.

    I definitely see how it helps cheat on homework, and extends “stock photography” to the point of really limiting the market for me photography or artists for bland business assets though.

    I see how people find it useful for their “professional” communications, but I hate it because people that used to be nice and to the point are staying to explode their communication into a big LLM mess.



  • So much the better, as far as those executives are concerned.

    Let’s say you want to cut costs and you know you have momentum and a long lag where your total incompetence won’t make a difference to business results in the short term, so cut costs by getting rid of the top talent.

    Now if they outright just fire every good person, well that looks obviously stupid, but if those good people just… up and quit… well they are hardly to blame, and don’t have to pay out those massive severances. You get your annual bonus which is big, and your big restricted stock payday might be delayed two years, but they know, realistically, they can probably coast a good 3 or 4 years before the game is up. Or if you have a supremely strong ‘business brand’, you might be able to coast indefinitely as the big shots will never believe that brand isn’t good anymore.


  • I have found my headset useful for work, when working from home and I don’t do camera on meetings anyway.

    At home it’s pretty nice, and since my ears are open I can actually talk, so my wife actually prefers it over me wearing headphones. But all things in moderation, I wouldn’t wear it constantly.

    Despite being a huge fan of the concept, I still couldn’t go for Apple’s headset, it’s heavy, it’s expensive, and lack of controllers are all deal breakers. The Quest 3 is lighter, has good controllers, and is more affordable. It may not have the displays as nice as Vision, but that doesn’t make up for the rest of the stuff.





  • Strong is not mutually exclusive with fat.

    I have a friend who made ability to lift heavy stuff basically his whole identity. Correlated with that was at any gathering he made a big show of eating just way more than everyone else because he’s a “big guy” and his muscles demand that much. So long as he could lift, obviously he must be fit, he works out after all. Basically his concept of masculinity is lift the heaviest stuff and eat the most stuff.

    Now he’s struggling with diabetes and liver problems, despite being crazy strong. Never did cardio, and ate way more than he needed.

    Yes, BMI can be misleading and being a bit muscular can have a higher BMI and be healthier than BMI says, but odds are if you are up in the obese territory, you probably are packing a lot of visceral fat screwing up your gut.











  • Any team that calls itself an Agile team that doesn’t actually follow the processes properly is doing it wrong and will fail.

    I mean, this statement is also weird, to imply that not following Agile implies failure. I’d say it’s quite possible for a team to “falsely” execute on Agile and still pull off success. However, if that story is prominent and successful, no one is going to make a peep about it not being “true Agile”, they’ll only do that when it’s a failure.

    But really this detail is beside the point, that people want to use ‘Agile’ as shorthand for good methodology, but it’s the way of the world that any shorthand that is popular will get co-opted and corrupted to the point of uselessness. You end up with various “interpretations” and so the meaning is diluted.

    Now at a glance, this may seem an innocuous scenario, ok, Agile doesn’t “mean” anything specific in practice because of people abusing it to their objectives, but it still carries the weight of “authority”. So if you have a criticism like “there’s way too many stupid pointless required fields in our Jira implementation, and there’s a super convoluted workflow involving too many stakeholders to walk a simple ticket to completion”, then you get chastised because “our workflow is anchored in Agile, and you can easily see online that Agile makes success, so you obviously don’t understand success”. You can try to declare “Individuals and interactions over processes and tools”, but then they’ll say “oh, but the stuff on the right is valuable, and it’s used to facilitate the interactions between people”. Thanks to Atlassian marketing, for a lot of the corporate world if you implement it in Jira, then it is, by definition, “Agile” and your peons can shut up because you are right.

    Basically, things get ruined by trying to abbreviate. You may be able to cite the Agile manifesto as something specific enough yet still short, though it’s still wishy washy enough to not be able to really “win” an argument with someone when deciding how you are going to move forward.


  • Yeah, Agile isn’t really at fault here. If done right

    This is what ticks me off about the “Agile” brand, it’s chock full of no true Scotsman fallacy (if a team failed while doing “Agile”, it means they weren’t being “Agile”).

    I can appreciate sympathizing with some tenets as Agile might be presented, but the popularity and consultancy around it has pretty much ruined Agile as a brand.

    Broadly speaking, any attempt to capture nuance of “best practices” into a brand word/phrase will be ruined the second it becomes “popular”.