7,948 karma · joined December 17, 2019
Personally I think the bigger risk is software innovations making CPU training (and/or inference) sufficiently viable that it's cheaper to train models on a commodity CPU cluster than on some proportionally expensive GPU cluster. I don't know enough about the space to say whether that's likely, but it seems like a low risk, since pretty much any parallel algorithm will always be faster on GPU than CPU - it's just a question of the marginal benefits and cost (e.g. maybe it takes more CPU to train same model in same time, but cost of CPU is so much lower that it's worth buying more of them).
I'm perfectly willing to believe usage has flatlined, and that matches my personal experience where I've opened it maybe twice since installing it, only to see posts from mostly brands, celebrities, influencers and meme pages. There was an initial surge where I got a notification every time one of my Instagram followers also followed me on Threads, but that only lasted about a week and it's been quiet since then. I suspect a lot of people were behaving similarly to me, either signing up to claim their account or opening the app when they got a notification of a new follower.
But I'm skeptical of the utility of comparing the flatline to a baseline from the first week, and of using data from Sensor Tower and Similarweb, neither of which has much insight into usage data beyond what's publicly available through metrics like app installs, reviews and maybe DNS. It's not like Meta is using any analytics frameworks other than their own.
If you don't believe me just look at where members of your government went to school.
Also, is it actually public? Or just shared with everyone inside the firm? If it's public, anyone got a link to the leaderboard? And if it's not public, then it sounds less like a gimmick, and more like a transparent stack ranking incentive program.
There's basically zero upside to phone calls, and frankly nor is there much for SMS either. I would suggest that phone companies completely deprecate their telecom networks and go all-in on internet, but then the spam would migrate to the apps (it's already begun with whatsapp), so I don't want to give them any ideas.
And btw, I've been where the author is, so I recognize the signs. Let's check back in three years.
My advice: get a job. (I see the author is currently an intern in college. So I'll amend that advice to be: line up a job for after graduation.)
Can you expand on this (genuinely curious)? Did Facebook use ChatGPT during the fine-tuning process for llama, or are you referring to independent developers doing their own fine-tuning of the models?
But in regards to production code, I agree. When code is committed to a codebase, a human should review it. Assuming you trust your review process, it shouldn't matter whether the code submitted for review was written by a human or a language model. If it does make a difference, then your review process is already broken. It should catch bad code regardless of whether it was created by human or machine.
It's still worth knowing the source of commits, but only for context in understanding how it was generated. You know humans are likely to make certain classes of error, and you can learn to watch out for the blind spots of your teammates, just like you can learn the idiosyncrasies and weak points of GPT generated code.
Personally, I don't think we're quite at "ask GPT to commit directly to the repo," but we're getting close. The constant refrain of "try GPT-4" has become a trope, but the difference is immediately noticeable. Whereas GPT-3.5 will make a mistake or two in every 50 line file, GPT-4 is capable of producing fully correct code that you can immediately run successfully. At the moment it works best for isolated prompts like "create a component to do X," or "write a script to do Y," but if you can provide it with the interface to call an external function, then suddenly that isolated code is just another part of an existing system.
As tooling improves for working collaboratively with large language models and providing them with realtime contextual feedback of code correctness (especially for statically analyzeble or type-checked languages), they will become increasingly indispensable to the workflow of productive developers. If you haven't used co-pilot yet, I encourage you to try it for at least a month. You'll develop an intuition for what it's capable of and will eventually wonder how you ever coded without it. Also make sure to try prompting GPT-4 to create functions, components or scripts. The results are truly surprising and exciting.
To me it reads like a great example of where ChatGPT is most useful: as a force multiplier for time-constrained entrepreneurs who have a specific goal and need specialized knowledge for short periods of time (e.g. to write a script). It's now basically free and instant to produce what would previously require a multi-week process of sourcing, hiring and communicating with contractors to write a script that leads to the same end result.
The kneejerk reaction to call this "surprising" or irresponsible, while understandable, gives major "get off my lawn" energy. This is the future and as coders we should support the increased self-sufficiency of non-technical people. If you want to adapt to the change then maybe think about how to improve the process for entrepreneurs of asking ChatGPT to write a script.
I did notice the ad serving infrastructure seemed quite sophisticated. There were so many domains and proxies and redirects. Luckily uBlock Origin blocks almost all of them. And usually, I can avoid any of the "bonus" features by opening the video player iframe in its own tab (but sometimes this isn't possible, or the video player tab has some scripts to make it annoying to run in isolation).
One thing I like to do during the commercial breaks is paste the URL of the site into GitHub Code Search. This always leads to interesting results, including blocklists, people's personal media scrapers, or sometimes even the (re-)publishing infrastructure of the sites themselves. It's also a great way to find alternative URLs or other streaming sites.
FYI you can create a virtual WebAuthn device in Chrome DevTools and use that as a 2FA method (just don't lose it lol). I did this with Google where it was required to provide a phone number or hardware token in order to unlock the ability to switch to a simple TOTP method. I created the WebAuthn device, generated a TOTP, set TOTP as the default method, and then removed the WebAuthn device.
I'm not sure this applies to the GitHub situation (I am having trouble understanding the linked forum post), but it's a useful tip regardless.