I would be very interested to see if the same effect holds in those athletes who maintain a low carbohydrate diet.
Maybe if the body is adapted to use fat as the primary energy source from the get-go, it would not go looking for energy in such a seemingly strange place.
I think the point here is that animals raised for meat should not be conflated with burning fossil fuels. Cattle, chickens etc. are part of the carbon cycle.
Modern high-intensity farming practices such as feedlots and cage chickens - where the majority of the feed is grain and harvested hay - are probably where the conflation enters. There is just as much a need to raise healthy, minimally carbon intensive animals as there is to reduce eating meat. There are farming methods to do this, but change is slow.
Not sure why you're talking about 'conflating with burning fossil fuels'. I didn't do that and neither did the paper. It seems like you're not read up on the topic.
Staggering amounts of methane and nitrous oxide. Massive deforestation and other habitat loss (read: reduction of carbon sinks).
Hey mate, as a fellow obese (soon to only be overweight) person, I found something that makes a lot of sense to me: the carbohydrate-insulin model of obesity.
The thermodynamic model of calories-in-calories-out doesn't work because we are not a thermodynamic system; it doesn't take into account the hormonal and metabolic changes that occur when calories are chronically restricted.
I feel like being pedantic for a moment. Our suburban posties don't get off the bike to deliver the letters, they ride up alongside the letterbox and deliver the letters right from the vehicle, as can be seen in the link in the GGP comment. They also deliver small parcels that will fit in a standard letterbox.
You are quite right though, as soon as the rain starts, they're in full wet gear. Bright yellow, you can't miss them.
Suburban parcel delivery is specifically taken care of by Startrack, an Auspost subsidiary, usually in a trusty Toyota Hiace van.
Yep, this is why I chose truck driving as a job. I am looking to change out of it now after 12 years, but there's no short list of 'one thing at a time'jobs, and the ADHD has prevented me from learning programming so far.
Regarding OP's question, when the tab counter on Firefox turns to infinity, I check the last ten tabs for anything really important, then take a deep breath and 'Close All Tabs'
May I interest you the most potent dopamine kick for us with adhd?
Build it, run it.
For iOS development, that means rubbing the ink off of Cmd+R, Python in PyCharm is Ctrl+R, bash is uparrow+enter…
The feeling of extreme frustration when things don’t compile and run, met quickly behind a rush of “hell yeah!” dopamine when things work - is an adhd brain’s white powder.
However, keep in mind that over time, business success will mean not finding the next thing to battle with or to learn - it will be implementing what you know quickly towards a customer aim. There’s a pit of despair if one doesn’t keep an eye out for that.
I was the typical “well-functioning, kinda smart” ADHD-kid, who got trash grades, to many of my peers surprise.
I was too busy tinkering with electronic music production, which I guess has a similar profile to coding, in regards to instant feedback dopamine hits.
Then I got into javascript at some point.
Last year I actively chose to go back to school to study web development. Top grades now and I am super excited to go to school every day.
I don't have an ADHD diagnosis, but I have some suspicions.
I find I want to be doing things. Those things must be immediately (or very quickly at least) and consistently rewarding, or I'll stop. That much is, as far as I've found in the last few decades, an unchangeable fact.
That pretty much rules out studying.
You can learn by doing things too, obviously, but the early stages of learning programming are either sensible small steps (hello world, what's a function, etc etc) or gigantic unrealistic moon-of-an-exoplanet-shot projects (I'm going to build the next World of Warcraft by myself by next weekend).
The sensible small steps are exciting and give the doing things successfully rush at first, but that goes away fast and you need more.
You do hello world (wow I made the computer do something!). Learn how to use some conditions (wow I made the computer decide something!). Learn about libraries (wow so I can just stitch a bunch of these together and build the next Big App!). Start working on your big idea, quickly realise you're not going to be getting the success hits fast enough. Do something else "for a bit" and never touch your project again.
I'm fairly sure the only reason I managed to learn to code was that my first job in tech support was both easy and boring, and automating parts of that job was more fun than actually doing the job. Productive things become much easier when they're procrastination from something less fun.
It's taken me ten years, but I'm finally at the point now where I've built up a big enough skillset that I can take on projects that I'm interested in, and make progress fast enough that I get my fix and can stick with them.
There is also the part where the machine I sit down at to attempt to learn programming also happens to be the same machine where I do banking, budgeting, YouTube, Reddit, HN, porn, gaming, socialising, falling down Wikipedia rabbit holes etc. etc.
There are lots of distractions for the distractable mind.
>Productive things become much easier when they're procrastination from something less fun.
I feel there are 2 main types: ADHD and the other type that we need to respect and be kind to. I suppose there is a gamut of sub-types in-between. Come and enter the "realm" of developers!
