You just described 90% of coding
202 karma · joined May 20, 2017
You just described 90% of coding
Even if you aren't an expert it is trivial these days to copy/paste it into chatGPT and ask it to optimize or suggest improvements to the dockerfile, it will then explain it to you.
From the article "Muscles grow by lifting weights" yet we do that now as a hobby and not as a critical job. I'm not sure I want to live in a world where thinking is a gym like activity, however if you go back 200 years it would probably be difficult to explain the situation today to someone living in a world where most people are doing physical labor or using animals to do it.
Only when you know for sure the problem can't be coming through from that component can you stop thinking about it and reduce the cognitive load.
For Seattle area in particular most weather apps will show the entire week as cloudy and rainy, but there is a lot more to it and merrysky is able to surface that.
Once you realize that you can actually achieve anything you set your mind to just by making a routine you will find yourself wanting to shift the time and effort going into games into real world success.
* Find new hobbies and things you enjoy, even if it is just being better at video games because you aren't drinking when you play. You can't 'stop' something without replacing it with something else.
* Understand that quitting isn't going fix all your problems, your life might seem worse/more boring afterwards. Accept it and see #1
* The decision to drink or not is the most stressful part. Things like dry Jan and sober Oct really helped me avoid making the decision and especially the long term decision at first. Deciding in the store if you're going to drink or not doesn't work, you have to make that decision one time and rely on the fact that you already decided for that month and it isn't a big deal.
* Exercise. People who quit drinking get healthy, it is such a stereotype but you will love it. Get jacked with your new extra time.
* CBD + todo lists, taking care of the little things in your life will keep your anxiety down and eliminate the need for the forced break from your life that drinking provides.
It will be 2 years next month for me.
The article mentions that FF hit %34 in 2010 and acts like that was due to the features, I don't think it was.
For the average browser user we're talking about here talking about bloat and features are irrelevant. FF's market share is just a number bouncing around in the waves between two giant forces, Microsoft which owned the OS for much of this timeline and Google which owns the pages everyone is going to where it is suggesting they install Chrome.
I see a strong need for a microblogging framework where users have control of their data. Mastadon is great, but I think Zooko goes farther in the right direction.
As a developer I both expect tools and libraries to be free and have been burned by this as someone working on developer tools and as an open source maintainer on my personal projects.
The frustrating part to me is that this doesn't apply to apps, saas apps, services, or a lot of AI/ML related things. Most developers expect to make money off those things while at the same time demanding everything they used to build it be free because it's just code and they love open source. It feels unfair, and in that way I agree, open source is broken, or at least unsustainable for small projects long term.
I doubt this will go well since if it keeps happening unproductive people will become the best at gaming the system.
But at the same time, there has to be a better way than being observed by a boss in a physical office. I don't want to commute just because people on my team who were unproductive in the office are now just as unproductive at home and not seeing their face daily makes it hard to tell if they took another job and just haven't told anyone.
In the end I felt like Clojure was too clever for its own good. By relying on Java (which was a great choice) it took a lot of the oxygen out of the ecosystem for other devs to build tooling and libraries, and without that there aren't as many people participating or becoming a well known community member from their work there. Again, can't say this was the wrong choice, but in my opinion ecosystem is the #1 thing for a language and the way Clojure was done had an impact on how the ecosystem could grow.