Ability to reason is unexpected and hugely important skill to emerge out of large language models. Its effects on society and potential benefits are largely unexplored.
This is part two of a five-part guide on how to monetize open-source projects with a focus on economics of open source, which sets us up to creative a sustainable, monetize business from open-source.
Asking, "Will ChatGPT take my job" is like asking if we'll have an economic recession next year. That question is too vague, broad, and general to give a meaningful answer. The Jobs Impact Quotient will introduce an objective and systematic way to think about this problem.
This is the piece that complicates my thinking about CDBC and digital transfer systems. What UPI does is seamless and instant transfer of Indian Rupees between parties and it is widely adopted. So why would India need, or benefit from additional CDBC? I can see how CDBC's instant transfer scheme would benefit the US which does not have digital transfer systems that are both instant and close to zero-cost.
So why would India need, or benefit from additional CDBC?
What makes the UPI system work *is* effectively a CBDC. It's not possible to have instant transfer without *something* that functions like a CBDC --- though it may be named something else. The EU calls theirs a "credit transfer scheme" --- same difference.
The word that seems to be confusing people is the word *currency*.
A CBDC will be used by *banks* to benefit consumers but it is not something that consumers will consciously partake of. Consumers won't carry CBDC in their pocket or in a special digital wallet.
One way to look at it is that a CBDC would be used to add the functionality of digital wallet to everyone's existing bank account.
I have had the same problem and I worked on it with a workflow of reading something today, making a note of it in a notebook (handwritten works best for me) and revising it the day after. The hand writing part makes me bio-mechanically engage with the material and finally reviewing my notes the next day forces spaced repetition. A nice side-effect is that after a few months when I am just flipping through my notebook I remember something that I had forgotten.
I use this for technical webpages that I read, business concepts (e.g. I am reading about `Yule’s Law of Complementarity` or new technical concepts (e.g. NestJS).
This works for me and I stumbled upon this workflow for myself after trying out a lot of other things that did not work for me.
So the answer for me is, I am not sure. I have a Oculus 2 and often "log in" and check it out. I use it primarily for entertainment purposes (like visiting world cities etc.). But I haven not have not purchased anything in the meta verse. Is that considered hanging out in meta verse or is that just old-fashioned VR?
My point is it is not clear to me what is meta verse and if it is supposed to be different from VR. I would love to read what other write about their experiences.
This article touches on something that I have been recently thinking about - remote work vs. async work. Remote work is in vogue these days but a lot of these companies don't allow or encourage async work. They equate remote work with async work but then institute tools like slack which are antithetical to async work. Typing indicators are one such way where slack encourages synchronous work.
Typing indicators are an anti pattern imo but async work doesn't seem like a desirable thing. Very few people are doing jobs where they can just go offline for a day and come back with a result.
Most work, especially software development requires frequent communication. Being able to quickly bounce ideas off people and verify your plans before committing to them is so valuable. I can't count how many times I have been right in the middle of something, had to make a questionable choice, spoken to a coworker just to verify the idea, and they tell me something that completely changes the outcome. Being able to get this done within the hour vs getting it right at the end in review is so valuable.
What is worse than being interrupted is spending days in deep focus only to find out at the end that you made a foundational mistake that invalidates the rest of your work. Through no fault of your own you could have the wrong understanding of what the user wants or how it fits in with other parts of the system. Being able to quickly sync up with the end user for a change or validate your ideas with another developer is so valuable.
If you need to wait a day to get a response from anyone, you either have to drop the work and do something else while waiting (breaking your deep focus). Or assume you are right while waiting and risk throwing out a days work if you are wrong.
IME many large, non-tech companies are so bureaucratic they essentially have an async flow. Which perhaps is fine, there’s already a defined process for what needs to be done. But for a startup where even the next two weeks are foggy, async work can be detrimental.
That's a strawman. You're conflating async with no communication. There's perfectly fine asynchronous communication methods. You have to communicate differently on async, not stop communicating.
almost all FOSS work is async. any company that has teams across multiple timezones does async work.
for me, unless we are doing pair programming, i expect communication to be async, even if we are in the same office. you don't get to interrupt on demand, but you better wait until i am mot focused on something else, and respond to your message
I have found FOSS to really illustrate the problems of async work. It’s extremely difficult to break in as a new contributor. There is no help like in a corporate job, you can post on GitHub and hope someone gets back to you at some point, but no one is going to get on a call with you and walk through a problem or the context.
Which shows in the contributor stats where 1-3 people do all the real work and everyone else submits trivial patches.
I read through the whole deck, end to end. This `state of crypto` was a very professionally put together list of key words with very nicely designed graphics.
Disclaimer - I have started reading this but have not finished it completely. Having said that, it looks very exhaustive and well written and well worth my time to finish it. A bit of feedback to the OP about the page though - the left and right content areas introduce clutter, IMHO, and make it hard to remain focused. But thank you for putting together this resource.
Frankly, I was turned off after the first couple paragraphs because it looked like some sort of government presentation for boomer generals. Will check out further.
Any good resources to learn more about promises in-depth? Not your usual, cursory overview but in-depth with explanations for complicated usage (like promises returning promises etc.)?
The MDN Docs never disappoint[0]. Even more details can be gotten from the author of OP's link: Exploring JS[1]. And if you're wondering why the catch block isn't typed properly in Typescript, see this [2] thread.
It's meant for beginners, but I'm very partial to Eloquent JavaScript (I personally think it's one of the best programming books, period. And definitely one of the best JavaScript books)
