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

help-circle







  • Yup, I would definitely agree more with what you’re saying here than what I understood from above.
    It definitely takes willpower to lose weight, and you definitely need to learn to identify why you’re eating and break those habits you don’t want, which also takes willpower.
    I would characterize boredom/stress/comfort eating differently than hunger, since there’s the distinction between “want to eat” and “feel hungry”.

    Whatever your reason is for wanting to eat, you need to handle it. If it’s boredom, you can use willpower to push through chips being more interesting than the show you’re watching, ideally by doing something else.
    If you want to eat because you’re hungry, there isn’t a way to handle that beyond eating. So the smart move is to make choices about what and how you eat so that feeling stays away longer, which goes a long way towards helping to break the habit of feeling like you’re “supposed” to eat more often than you need to.

    I think you’re initial comment came across much stronger than I see it is now, and we’re actually very close in terms opinion. :)




  • Precisely. And to be entirely clear: it will always take willpower and motivation to lose weight. Your body is thought to have a sort of target weight that it wants you to be at all else being equal. If it were effortless to maintain a healthy weight, it would be because that’s where your body was pushing you to be.

    The key is not to be stronger than your body, but to work with it. Use your finite supply of willpower on things like “making a healthy shopping list and not deviating from it”.
    Instead of insisting you need to “not be lazy” and always cook a healthy meal at home, be realistic and accept that sometimes you’ll be tired and have a lazy dinner option that’s a better choice than pizza.
    Buy apples instead of Oreos, so that when you feel hungry between meals it isn’t a choice between feeling hungry and eating a sleeve of Oreos, but just eating an apple. You’ll feel more full after the apple than after 20 times more calories in Oreos. If you choose to be hungry, you’ll be aware of being hungry and food in general until you eat, which will likely either make you fail hard, or eat more at the next meal because food is more appealing when you’re hungry.
    It can also take a lot of motivation to work through which desires to eat are hunger, which are boredom and which are, of all things, thirst. Eating is a source of dopamine, and so if you’re bored “food” is an easy source of entertainment (your body is so dumb that just chewing is often enough for it, hence “gum” is pleasant). Sometimes your body asks for sugar when what it needs is water.

    “You” don’t control what “you” want, you just get to figure out how to get it. A deeper, vastly stupider, part just shouts vague demands you get to act on. “WATER. FOOD. <GENDER> SEX. SLEEP. SCARED. BORED.” it doesn’t stop shouting if you ignore it. So use your willpower to give it what it wants in the healthier but more difficult way, and to make doing so a habit that it won’t veto.

    And that’s before you get to things that need a medical intervention in addition to behavioral.
    If your pancreas or hypothalamus have decided to be shits, there’s absolutely no amount of willpower that can regulate things.



  • That’s a more complicated topic. Not everyone’s endocrine system is wired the same way, and you can’t always just willpower your way through it.

    Insistence that willpower is sufficient for weight regulation is a big cause of people going on diet after diet that just doesn’t work. They’re fighting against the system that has a disproportionate influence on what you want in the first place, and if you push it too far you find yourself not giving a shit about your diet, and then being filled with a slew of complex feelings coming from your “lack of self control”.

    It’s better to direct that energy towards getting your diet compositionally right than trying to be okay just being hungry.

    You can’t get your body to stop insisting it needs food, but you can get it to insist less often. You can teach it that it doesn’t need “SUGAR”, it needs water and maybe an apple or banana. You can give it a little solid protein between meals to keep it from asking for a continuous stream of carbs.
    You can learn to identify the difference between eating because you’re bored or want a little dopamine, and eating because you’re hungry. The first one is your brain and you can willpower through it to eventually unlearn the habit.

    You can choose to make good choices at the store instead of failing to make them in the kitchen.

    Willpower is critical, but it’s important to know what you can or cannot actually solve with it and work within that framework.
    You’re in control of your body, but that doesn’t mean that you need to pick the harder path.

    And, for some people, their endocrine system is a lot more forgiving. Those usually aren’t the people who have a lot of trouble loosing or keeping off weight because they try to just “eat less” and it works.



  • In the sense that they have a manager? Sure. In the sense that there’s one individual dictating the design of the software? I’ve never even been on a team with that dynamic, to say nothing of the entire codebase.

    Modern software teams tend to eschew design by decree.

    What’s the dynamic that you’re thinking is typically what teams use?


  • I’m not sure I’d construe a manual you can find, or a variety of guides, as a negative. :) most days my usage of git consists of “pull, commit, push, merge” in different orders. You might be overestimating how much effort goes in to managing the tool.

    Most of my professional experience has been working on projects that consist of multiple teams of between 4-6 developers, and between 5 and 40 teams. I’m not entirely sure what you mean about git not mirroring the development patterns of most “real life” projects.
    “Real” projects are frequently developed by groups of people working on the same goal adjacent to other groups working on related but distinct goals.


  • We very clearly work in different professional environments. :)

    In no particular order: Administrating a git server is similarly trivial. A repository is a folder (easy to backup, easy to repair, easy to host), and setting up a new server usually a matter of ssh key management. Don’t even need to install sqlite or anything beyond the git package. Or, because the tool has wide support, you can install a wide selection of tools that manage it for you, or use a free hosting service, or a paid one.

    I’m startled that you would say you can’t think of anyone who would care. My entire professional experience has been developer stories about bad jobs often include details about using old or esoteric VCS systems, usually met with “ew” or “wtf” comments. Sets the flavor of the story.
    Personally, in a business environment, I would take using anything except git for the org as a red flag. It’s a sign that someone in leadership at the company values doing things unrelated to the core mission “their way” above doing it the easy or “paved path” way.

    The standard tool is indeed not constant. Before git existed, using CVS would have been the better choice, as well as for years afterwards until it had clearly been usurped. Most projects aren’t Linux when it made the switch to git.

    You joke that no one really “knows” git, but… This is literally the first time I’ve ever seen a fossil command. I just searched for “fossil manual” and I get analog watches. It’s not even available in any of my systems package managers.
    Developer familiarity is a big advantage that I think you’re downplaying in comparison to “there are metadata files in .git”, which I don’t know has ever been relevant to me in any significant way.
    (Also, I thought the different systems all work basically the same? 😛)

    I’d handily agree people should be using the best tool for the job. Familiarity and ease of use are significant factors in what makes a tool better.
    Ability to integrate with other tools is also a major factor. Setting up continuous integration or code review tools with git is trivial with any number of different systems.

    What are any of the tools you’re using doing better than git? The biggest selling point you’ve shared for fossil is that it’s functionally similar to git, and that it has better merging. I can’t find anything related to merge conflicts outside of years old forum posts, and barely anything relating to merges at all, so I’m not entirely certain what makes it “better”.

    If it’s biggest advantage is that it’s similar enough to git that you can pick it up fast, why wouldn’t I just use git?


  • Like I said, there are always factors.

    For a company starting from scratch though, the usage base factor becomes vastly more significant.
    Using a tool that radically limits your integration capabilities is a poor choice, to say nothing of most likely needing to onboard every new employee to an entirely new VCS.

    I don’t know that I’ve encountered anyone using svn that wasn’t interested in moving in recent memory, so “developer experience” would be a reason to move.