WebRTC and decentralization. I mean actual decentralization and not crypto bullshit or web services.
643 karma · joined May 28, 2022
1) Have children early at risk of living life without wealth but at minimum risk of health for all parties.
2) Delay. This risks never having children for various biological reasons for the impractically increased chance of increased wealth.
As somebody who had children early, went through poverty, and now lives in a large house with a nice job I can't help but look at single people in their 30s or older. I always want to ask them why they cannot afford a Lamborghini or live in a giant mansion. They had no such restrictions on their time and/or finances to dedicate increased efforts in advancing their careers or founding new businesses.
https://en.m.wikipedia.org/wiki/Ali_Khamenei
https://en.m.wikipedia.org/wiki/Ayatollah
The most well known of the Ayatollahs is Ali Al Sistani who doesn’t even live in Iran and has no direct affiliation with the Iranian government.
* Don’t be clever. Clever is the attempt to short-circuit logic to arrive at a conclusion in seemingly fewer steps. This tends to backfire with either incorrect conclusions or logical fallacies that don’t make sense.
* Don’t self promote. If you want to be likable never talk about yourself except for moments of private self disclosure.
* Don’t interject into a conversation unless you have an exceptionally important reason for doing so.
* Have empathy, the non cognitive ability to anticipate the pains and pleasures of others. Don’t guess at this. Read people, read the room, and then qualify your assessments with pointed questions. You have to naturally and innately want to do this.
* Be direct. This means starting with a conclusion, but be prepared to progressively step through the logic only if asked.
* Be honest. You cannot achieve trust without honesty. Many people find directness and honesty challenging.
* Be available. This means an eagerness to exit your current focus and redirect yourself to the needs of someone else instantly without prior notice. When this is not possible respond with why and when you will be available.
* Be helpful, which means an eagerness to spend time and effort to solve a problem with someone else, a problem that do not own and will not be awarded for.
* If you wish to be humorous amplify logical directness with a play on words or through gross amplification, particularly when that directness comes at the expense of somebody else. If in practice this will require any kind of explanation then don’t do it.
Notice I never mentioned kindness or sympathy. That is intentional.
* The primary driver of motivation in animal brains (even in small worms) is a healthy dopamine cycle. In the brain there exists a dopamine baseline by which regular drive and motivation occur. There are also dopamine spikes when a pleasurable moment occurs. A dopamine spike is always followed by a dopamine crash and that dopamine crash will always occur in the same ratio below baseline that the spike occurred above baseline. Driven people are able to maintain a near constant high baseline and recognize their depressive spikes with healthy and positive responses.
Drug use, except for caffeine, almost always damages and/or destroys either the dopamine cycle or permanent dopamine production. A primary motivator behind the consumption of drugs, particularly combinations of drugs, is chasing a dopamine high that has already left the brain.
* Openness is one of the big 5 of personality indicators. Openness is the willingness to try new experiences and creativity falls under openness. Openness is not in any way correlated with extroversion.
These are not necessarily alpha personalities, as in their goal is probably not to compete but rather to be productive and industrious and probably original. This is an important distinction because alpha personalities qualify their performance in comparison to others while industrious and/or creative people quality their performance in response to their output even when there are not other people to compare against.
Those two qualities are what you need to look for: healthy living by people with a naturally higher than average dopamine baseline and people with a high personality index in openness. I recommend looking for people who have an abnormal need to build and/or produce things. The famous musician Hans Zimmer is really good at this. He has a traveling band composed of a mix of classically trained musicians and rock/metal musicians. When Hans Zimmer looks for new band members he has on several occasions found highly talented amateurs off of personal videos posted to YouTube. These are people who may completely lake the confidence of an alpha personality, but are still driven to create music and post it on YouTube at risk of complete embarrassment. The result is that Hans Zimmer hires emerging talent on the cheap and this emerging talent is immediately thrust into world-class training.
* Guthrie Govan discovered by Hans Zimmer via YoutTube - https://en.wikipedia.org/wiki/Guthrie_Govan#Hans_Zimmer
* Dopamine explained in a 2 hour video by a Stanford neurology professor - https://www.youtube.com/watch?v=QmOF0crdyRU
* Architecture - Most people writing code cannot plan, write, or envision an original solution to something wildly ambitious. This takes practice and with enough practice it gets comfortable and easy, but most people writing code will never get to that point. A mastery of architecture is possibly the only way to produce a superior product compared to the competition provided that business requirements remain unchanged.
* Performance - Astonishingly most people never measure anything unless they are forced to. Learning to measure things (everything) is a cognitive skill and the result is the difference between a 2 hour work day and an 8 hour work day. Measuring things is also the only way to write fast software, because everything else is guessing (and probably guessing wrong by several orders of magnitude). At the end of the day performance is not about how fast something this, but how much faster it is than something else.
* Writing, especially bridging the gap between technical writing and narrative writing for common people.
Web X.whatever is not about content. Its not even about technology. That is why term has failed to stick each and every time. Business people looking to drum up VC need something like this because a simple catch phrase is easier to sell than a concept they have no hope of understanding or explaining.
Do you remember what Web2.0 was? Yes, this was a real concept, and yes it did succeed and proliferate. In short, Web2.0 was use of asynchronous HTTP requests from pages. At that time the technology was just XMLHttpRequest (XHR), but it wasn't about the technology. It was about what you did with it. If you cannot remember back to writing code for the front end web back to 2005-2007 when this first became a thing I don't expect this to make any sense to you because you have no context.
Back then the web was a series of HTML forms and/or static pages. That's it. Content could not change and information could not be submitted without loading a new page. XHR radically changed the experience and how users interfaced with data and how data providers interfaced with users. That change to the business experience was Web2.0. Back then it was a massive improvement, but then you also didn't have the world's largest frameworks to make it so slow and unoriginal.
If people want the Web3.0 moniker to stick to something then apply to something that radically changes how the user perceives the web. Crypto is not and will never be that thing. If VCs lack so much empathy they are bound for losses by shams and cons.
One example of what a Web3.0 could be is a streaming experience where pages load in less than 0.5 seconds (with full state management) and transmit/receive updates in near real time such that you only need a delay spinner for the extreme edge cases.
The interesting moments were when somebody with less than 3 years professional experience were elevated to management because it’s a startup. They were so lost trying to interview somebody with 20 years experience and prior experience as a corporate director level. I completely stopped talking to start ups.
Eventually I got very lucky and found a company that is awesome with incredible leadership. They were actually looking for a senior to come in and fix some architectural things and in return they would teach me areas of programming I had never done before.
Here are the common danger patterns I observed over and over:
* Most importantly look for strong leadership in the employer first. If it just isn’t there stop talking to them. They are more than happy to waste your time in repeated interviews.
* Determine the level of honesty present in the work culture. Look for brutal honesty up front and don’t be shy about it. If they are timid about honesty in an interview you will spend your employment walking on egg shells and playing politics, the kind of place where shitty brown-nosing people get promoted over you.
* Next evaluate for the quality of work. Do this by asking about writing original code. If they are timid about original code or are horrified at the thought of stepping outside the yellow brick road to produce a superior product I don’t want to work there. There are many people thrilled to work at someplace average building a shitty product so they should hire one of those other people.
* Finally evaluate for retention. Does that employer work extra hard to retain people? If not you need to drill into this immediately.
Don’t be shy about asking tough questions. You will be devoting a block of your life to these people.
I have been thinking about how I could monetize performance. I have learned how to load data heavy pages with complex UIs in 0.3 seconds with full state restoration. I have also found a way to test automate that experience with ease and without a giant test automation framework.
Performance is great because the business implications are vast from improved human focus and less fatigue to fewer infrastructure costs and superior user retention.
Most of the software engineers I have worked with never put anything in writing because they lack confidence in their ability to express their thoughts in a written form. When that becomes common in a work culture you tend to have lots of meetings where people over communicate verbally as a compensation while everyone else is silently playing games or watching paint dry.
It’s not about the content. It’s about the experience. Web 2.0 were sites making use of XHR (asynchronous HTTP requests) to send/receive content without refreshing the page. Back in the 2000s this was a massive improvement because the experience was better over slow connections and there weren’t giant frameworks to dick it up. You actually had to know what you were doing and the experience was massively improved.
In that spirit “Web 3.0” will likely be a socket and event driven experience. Now the bottleneck isn’t the transmission but slow applications from poorly trained developers. When the application and the transmission are both fast a web application can perform faster than desktop applications doing everything in 50ms or less in response to user interactions. You aren’t going to achieve that with the overhead of HTTP round trips.
Here is the summary:
* You need a storage location
* You need a defined data structure to store your state data. I recommend storing everything in a single logical storage object, because 1 is simple and simple is good.
* You will need to update and save your storage object at the needs of your application. I do it on each user interaction, because this is cheap.
* On page load you will need to access your storage object and apply it to the user facing event handlers that create your state artifacts that otherwise normally execute in response to user interactions.
That’s it. Consider the problem from the goal and work backwards to the solution.
If you try to bring up that the days work could be solved in less than hour if only we didn’t make all the wrong decisions and fear the platform they will look at you like you’re retarded. I have heard this mentality expressed perfectly in the movie Edge of Tomorrow: Don’t tell anybody. Are we clear? Best case scenario you’re gonna end up in a psych ward. Worse case you’ll get dissected for study
In front end development people NEED the world's largest application frameworks (sometimes plural) because they cannot figure out state management. State management is stupid simple and a solved problem, but whatever. It will still, at the job, take you all day (maybe a week) to make that 30 second change.
Most of my functions though are void functions (returning null or undefined). It’s not essential to me that functions must return a value, in defiance to functional programming, so long as like instructions are grouped in a single container that may be called by reference.
I wish there was deep profound social, economic, or behavioral issues at play, but there aren’t. Some people want to build things and others just want to shout into a void or stare at those who do.
I apply that reasoning to all investments. Sure, I miss out on all the easy money hype trains, but the investment decisions are almost always safe and still better than market average.
You can see from that set of benchmarks (once you run them) that Chrome will top out at around 45 million ops/s in the fastest cases.
In Firefox the top cases are a stress test of memory access speed. My old desktop with DDR3 reports numbers like 850 million ops/s while my newer laptop (4 years old) with DDR4 memory, both otherwise slower, reports something around 1.2 billion ops/s. Years ago when I discovered those benchmarks I remembered other users reporting as high as 5 billion ops/s.
I would be curious what somebody reports now with fast DDR5 memory.
0. Don’t waste your time dicking around with tools. Save that immaturity for the children you will ultimately replace.
1. Make a new language in XML Schema. This will teach you about node relationships, DOM theory, lexical models, semantics and data description. The things you will learn from this will shape everything else.
2. Learn accessibility. This will expand your learnings from step 1 in a very practical way. Added benefits are better SEO and slimmer more precise HTML code. When I say learn accessibility I mean to take this seriously. It is a qualitative investment and not checking a box in a checklist.
3. Learn CSS. When you really learn CSS well you will gain the confidence to create any kind of visual presentation without ruining your accessible HTML.
4. Learn the DOM. Again, this reinforces everything learned in the prior steps. Walking the DOM in Firefox is as much as 250000x faster than querySelectorAll. The DOM is the backbone of everything in web frontend technology.
5. Now it’s time to learn JavaScript, but I recommend jumping straight to TypeScript. Type everything and keep your type definitions extremely primitive. In TypeScript clever code is very slow to compile.
To really really understand frontend JavaScript well all you really need is a thorough understanding of the lexical scope model, functions, and events. Functions are first class citizens, which means functions can be used anywhere primitive types can be used. If you can understand those three with great confidence you can do 98% of everything you will need in the language.
6. Finally, don’t listen to the ignorance. Most of the opinions I have seen in my 25 years of web development are about what people can’t do and how hard life is, great insecurity searching for validation. Toss all of this negativity and weakness aside. Instead, always focus on what you can do. Less is more. When you push yourself to exceed your potential after great effort you will do what the complainers can’t.
The only enticing quality of blockchain to finance is just elimination of transaction fees on a more open ledger.