Yeah, same, auDHD er , most of the ADHD people I know, and especially the auDHD people I know, including myself, can’t form habits our brain just isn’t wired for it. I stopped trying and focus on other coping mechanisms…
I see plenty of such people who don't seem to have such a problem, at least not uniformly (some habits stick, some don't), so unfortunately I don't think such a simple excuse works. I think examining Big 5 personality traits, and the sub-facets within, would produce more reliable results, but I'll admit that's just a guess. Whatever the reasons, there's nevertheless broad variation on whether habits stick or not. I read Stephen Guise's Mini Habits a couple years ago on suggestion from some other HN thread, as expected it hasn't exactly "worked" for me in that I have no new habits since reading it that I've been able to maintain consistently on a periodic basis (daily/weekly/monthly, and I even failed a yearly goal streak of 3 years last year and am on track to fail again this year). Streaks get broken, and gaps last longer than streaks. I still think it was useful to read though for two reasons.
First, it's one of the few sources that recognizes the huge variability:
How Long Does It Take To Form A New Habit?
It depends. Anyone who tells you differently is repeating what they've heard
(which is wrong).
It is NOT 21 or 30 days. ... The 21-day habit myth was possibly started by Dr.
Maxwell Maltz, a plastic surgeon. Dr. Maltz reportedly found that amputees took
about 21 days to get used to the loss of a limb. So he argued that 21 days is how
long it takes for people to adjust to any life changes. ...
The most-cited viable study on habit formation duration was published in 2009
in the European Journal Of Social Psychology. Each participant chose an
“eating, drinking or activity behavior to carry out daily in the same context (for
example ‘after breakfast’) for 12 weeks.” And what did they find?
The average time for a behavior to become habit was 66 days. But the range
was wild, from 18 to 254 days, showing that there is huge variation in people's
time to reach habit automaticity, and that it can end up taking a very long time in
some cases. 21 and 30 day challenges are popular, but they're highly unlikely to
form many types of habits. ...
In my experience, the first sign of habit formation is decreased resistance, which
makes perfect sense.
Second, it uses a fun trick to motivate some things later. The trick is this: touch your nose, right now.
I still like to think about that trick (and sometimes even do it) and what it could suggest. For me it makes me more suspect of concepts like "willpower" and "executive dysfunction". This trick is never a challenge to do, even to do multiple times. Yet, if I tried to turn it into a habit -- touch my nose every day between 1pm and 2pm -- I'm certain that would fail to take hold. But that's fine, action is what's important, not whether it's a habit.
A flavor is a slightly different syntax, a renderer is the software that outputs format x from markdown. So flavor A can only be rendered by renderer A, but vanilla markdown can be rendered by all renderers. Different renderers can produce different output based on the options you give them, though
Sure, and Markdeep handles vanilla Markdown just fine. It also offers some extensions, which can't be standard by definition. I don't see a problem with that, and I definitely don't understand the distinction the grandparent was trying to make.
I run my home automation and infrastructure on kubernetes, and for me that is one of the smoothest ways of doing it. I find it quite easy to deal with, and much prefer it to the “classic” way of doing it.
what dark magic are you using? Not joking. I've tried learning kubernetes several times and gave up. Maybe I'm not the smartest. Can you point to guides that helped you get up and running smoothly? This is probably something I should put some more effort into in the coming months.
I think this is really hard, it's a bit like how we talk about learning Rails in the Ruby community. "Don't do it"
Not because it's bad or especially hard, but because there's so much to unpack, and it's so tempting to unpack it all at once, and there's so much foundational stuff (Ruby language) which you really ought to learn before you try to analyze in detail exactly how the system is built up.
I learned Kubernetes around v1.5 just before RBAC was enabled by default, and I resisted upgrading past 1.6 for a good long while (until about v1.12) because it was a feature I didn't need, and all the features after it appeared to be something else which I didn't need.
I used Deis Workflow as my on-ramp to Kubernetes, and now I am a maintainer of the follow-on fork, which is a platform that made great sense to me, as I was a Deis v1 PaaS user before it was rewritten on top of Kubernetes.
Since Deis left Workflow behind after they were acquired by Microsoft, I've been on Team Hephy, which is a group of volunteers that maintains the fork of Deis Workflow.
This was my on-ramp, and it looks very much like it did in 2017, but now we are adding support for Kubernetes v1.16+ which has stabilized many of the main APIs.
If you have a way to start a Kubernetes 1.15 or less cluster, I can recommend this as something to try[1]. The biggest hurdle of "how do I get my app online" is basically taken care of you. Then once you have an app running in a cluster, you can start to learn about the cluster, and practice understanding the different failure modes as well as how to proceed with development in your new life as a cluster admin.
If you'd rather not take on the heavyweight burden of maintaining a Workflow cluster and all of its components right out of the gate (and who could blame you) I would recommend you try Draft[2], the lightweight successor created by Deis/Azure to try to fill the void left behind.
Both solutions are based on a concept of buildpacks, though Hephy uses a combination of Dockerfile or Heroku Buildpacks and by comparison, Draft has its own notion of a "Draftpack" which is basically a minimalistic Dockerfile tailored for whatever language or framework you are developing with.
I'm interested to hear if there are other responses, these are not really guides so much as "on-ramps" or training wheels, but I consider myself at least marginally competent, and this is how I got started myself.
I share the frustration. I can get office365, with 1T of onedrive, mail, office apps etc for 15 / month, a subscription of even 5 a month is just nuts. Especially since the subscriptions seem to be just stacking up.
I’m glad you guys are making a living, but I can’t justify yet another subscription.
Yes, thinking back to the days of e.g. F-Secure, or all in ones like Coda that included terminals, $10/year or $0.99/month would be a more appropriate revenue stream for the feature work on an ssh client sized app.
Uptime is bad, mmkay. I don’t tolerate uptimes longer than 90 days. Always have planned reboots as part of your scheduled maintenance. One day, one of those high uptime machines will go down, and won’t come back up.
That so far has not been proven. OTOH, Cisco devices [0] have been proven to contain backdoors in the past.
I am cautious of any government tampering in devices, but as it stands such tampering has not been found in huawei devices, but HAS been found in devices coming from US manufacturers... Yet no one is asking a ban on those?
The article references intelligence agencies hacking routers, shocking routers have bugs and vulnerabilities just like all other computers and software, or intercepting them in shipment to implant devices. No where is there any implication that Cisco purposely created a means for US or any other intelligence agencies to access their routers or otherwise cooperated in intelligence gathering which is Huawei is being accused of.
Meanwhile, it has been shown [1] that the NSA DOES in fact compromise cisco equipment. Huawei hardware has yet to be found to contain backdoors, but we should ban Huawei, but not Cisco?
While compromised hardware from _ANY_ player worries me, I worry more about American hardware than I worry about Chinese hardware at this point in time...
