295 karma · joined October 4, 2019
But it's not just about the popup - it 's more that when your work is fundamentally about using reusing someone else's character, it feels pretty hypocritical to be so focused on making sure you get credit.
Which is not to say he wasn't "willing to dedicate [himself] entirely to solving the problem", but I think it agrees with your take about finding market opportunities rather than following a passion.
Maybe a long load time just wasn't that important for the success of GTA.
But AFAICT, it just doesn’t scale whatsoever. That SQLite db is both the dataset index and the dataset content combined, right? So you're limited by how big that SQLite db can realistically be. The docs say "share data of any shape or any size", but AFAICT it can't handle large datasets containing large unstructured data like images and video and multi-billion data point datasets are hard to store in a single machine/file.
Not really a criticism, but more wondering if there are scale optimizations in Datasette I'm not aware of since the docs do say any shape or size.
Everything else is just window dressing.
More concretely:
- Identify why you need an "escape valve". Understand that having an escape valve that dominates your life negatively is the problem, not the shape that valve takes
- Identify the triggers that push you to the escape valve. Both the long-term triggers (for example, it could be being stressed or unhappy) and the immediate habit triggers (for example, it could be seeing paraphernalia or being extremely hungry). Try to reduce the long-term triggers. Try to develop new habits around the immediate triggers (trigger still exists, but habit response is something you want to do). Being aware of your habit loop is IMO important for improving how you react to triggers (therapy can be really helpful here)
> We have performed an internal review of a sample of accounts and estimate that the average of false or spam accounts during the first quarter of 2022 represented fewer than 5% of our mDAU during the quarter. The false or spam accounts for a period represents the average of false or spam accounts in the samples during each monthly analysis period during the quarter.
> In making this determination, we applied significant judgment, so our estimation of false or spam accounts may not accurately represent the actual number of such accounts, and the actual number of false or spam accounts could be higher than we have estimated
What I know of your experience shows a low number of years of experience, a lack of papers, and a lack of true hands-on experience at the small number of companies in the world that have the resources to truly investigate large models. How can you know so much about LLMs without ever having the resource to train one?
I'm obviously not going to dox you, so you can easily just dismiss what I'm saying. But even just reading through your HN comments shows arrogance in your own knowledge (across multiple domains).
A specifically memorable quote is:
> I frequently create unique on the internet [words]
This is very true. Your erudition is apparently only matched by the uniqueness of the words you use when on the internet.
No, you don't. Looking at your experience, there is simply no way that you are the foremost expert in DL on HN.
Javascript and webdev is also a decent option since you can build such interesting and shareable web apps quickly, but the frameworks and scaffolding can be intimidating and painful.
I would work backwards from a project/interest and pick a high-level language where it's easy to get a good enough solution and create something that feels like an accomplishment. I would want to teach both programming as well as the joy of programming.
IMO this is exactly when you should not be using AWS. AWS is a premium offering and you can find cheaper alternatives for the commoditized offerings like EC2, RDS (the older, non-AWS-specific features) and (maybe) S3.
It's the high-level services where the real value is in AWS - the cutting edge technologies that only exist in a specific cloud (or multiple clouds but where it's difficult to port across clouds due to subtle differences). This is where the extremely high development cost is able to be amortized over many customers, allowing you to get scalable, easy-to-use, and easy-to-operate services at a much lower cost than would be possible outside of that cloud. A great example of that for AWS is Serverless Aurora.