Because anyone worth their salt knows that the superficial hello world example covers the tip of the iceberg. So to say you learned it in two days means you either don't get that you barely scratched the surface or you dont get what other developers really need when they hire someone with knowledge in a specific framework.
Honestly i thought the concept of Uber would work. I'm commuting and you are too so you give me a few bucks to go my way. It was supposed to be "Cash, grass, or ass" minus the grass and ass.
But then people started driving purely to get people to pay them and suddenly its a taxi service.
Well for scaling. If you wanted on prem you bought cheap. And when you needed more power you were screwed. So if you were worried about that you bought too much system in the hopes you don't overload.
But even those motivations only get you surface deep. I'm glad technology has gotten better but what streamer today has bought a new camera only to find the drivers haven't been updated and had to go into the system registry to add a new vendor id? Not that this individual task is important but it's the mentality of being about to fix and manipulate their system when things don't work...computers aren't walled gardens. That's totally lost on this generation.
But that kinda makes sense. They never had that period where tech sucked and you had to struggle through it. Even as a developer I'm noticing the junior developers amazed at the stuff i know how to do and they ask how i soaked it all up. It's cuz i had to just to get basic shit to function.
State cases will definitely put him in jail. They don't care about any of the political nonsense and honestly I'm not seeing the DoJ backing down either.
Honestly if they dont put him away i think it will only embolden his group to make them feel they all are untouchable.
The problem was that my boss was a title hopper and needed to fill his old position and he did it with yes men who wouldn't stand up for anything. Meant that these yes men were also not the greatest at doing the rest of the job either.
They were expecting me to just do Hero Engineering by not objecting, put in more time and fill on the gap when theu couldn't do their job. Was the first time in 20 years i ever was reprimanded, been praised at everything else I've done. So i knew at that point this was just a toxic place to work.
The last place i worked at they started pushing the same type of cringe. What made it worse was the PM/BA wasnt actually writing stories. One sprint I had 4 stories with just titles and "TBD" on the description. His boss was mad that my productivity was low when i couldnt do the work they couldn't describe.
There are a lot of channels that are missing from what i did back in Reddit. Many i have no interest in modding so they most likely wont show up for a long time.
Much of it was obvious, a few new ideas. But it was good to just reinforce the whole process. It's all about you building your own strategy so whatever works for you.
Being a vim user for 30 years I'm often tempted to learn emacs purely for org mode. But then i remember emacs is evil and go back to todo.txt and vimwiki and I'm content.
C: tasks that need to be done but aren't high priority
D: tasks I delete if not done by the end of the month
I make sure all my tasks have a +ProjectName and if i have to deal with a @SpecificService or @EmployeeName i note that. I will also add in things like jira:StoryNumber or other data.
Due dates are rare, only when there is a hard stop. End of a sprint is not a hard stop. If i need to remind someone I'll use due date and @Reminder
100% of the time all tasks go in my list. Nothing is left for me to remember. It goes into my list before it ends up in a Jira ticket or Conflience page. Remind me first, everyone else second.
First thing in the morning i process my list. Move tasks to A. End of the week at the end of the month I delete all the D tasks.
As for notes, i use vimwiki with automation to compile into html when files are written. I've also setup coworkers with an automated process using pandoc to go from markdown to html. Then i have a little a bookmark on my browser to pull it all up nice and pretty. I'll post the scripts later, not at my computer.
Daily diary entry made every morning when i do my todo list prep, entry for each meeting. Add notes during meetings and links or other details when looking for solutions to problems.
Inter-country commerce is often done in US currency if ones own currency is extremely volatile. Nothing worse than trading in something else and before you convert to your local currency the value drops out.
The big difference here is there is already this "learning curve" about the whole fediverse that people were struggling with that many of us wrote blog posts and had toot chains we'd forward explaining how this universe works. Adding in links and screen shots and templates for how to submit a bug...
...I hate saying this but the vast majority of people are just lazy. It's not a culture issue or not something too difficult. People like to complain and not put in effort to things. People expect others to do things for them and don't get that free comes with a cost.
FOSS isn't really that small, it's just that most people don't do any type of investigation into what they use for technology. Much of what you use may have a for-profit company in front of it but huge parts of their products are open source andnyou can directly influence the products by actually engaging the projects themselves.
Because anyone worth their salt knows that the superficial hello world example covers the tip of the iceberg. So to say you learned it in two days means you either don't get that you barely scratched the surface or you dont get what other developers really need when they hire someone with knowledge in a specific framework.