I write Python, PHP, Lua, bash, javascript, Dart, Go. Created https://xitter.cf/t.co/3Sbx5id8IY, https://xitter.cf/t.co/0J94lnvHKN, odoid. A father and husband.
Joined December 2023
- Tweets1K
- Following219
- Followers24
- Likes205
Well... sometimes i love the mission of Islam on red people's land. You mess up a continent and every day, you find new things to use and spat on their face. Like the destruction you brought to them wasnt enough. These Africans you re mocking are way smarter than your dumb kids I watch get interviewed on daily.
What makes these looser think if I learnt their language while still keeping mine, I can't learn anything? And is there something they can do that I can't?
Evidence of africans excelling across the globe abounds. But yea, brain size!
Hey @grok do Africans on average have smaller brains and lower neuron densities? If so, how is that expressed in day-to-day life
Having worked with argon 4, here is my findings.
For coding, it is not there yet. Though it writes clean code.
Right now it excells at visual works.
But I can't replace 3.8 flash with it.
So I will keep using 3.8 till I need to do visual works
Looser statement. This is why billionaires will keep getting richer in America. Everybody claims to know the theory. Just few has the mind to put it to work.
Few weeks ago people were like "Goodle is going down, Person A left last week and now this person XY, google is so cooked"
And Google has released 3 good coding models since then. 2 days ago was Argon 4.
People still dont get it.
Your analogy doesnt fit what you want to say.
When you read book, you learn. In fact, schools encourage reading of books.
When you read, you re practically putting effort. And then you move to apply what you read, that too requires a ton of effort and skill.
LLM ships the books, the research and works of skilled people and ship it to people who dont require skill to get output. And they feel empowered🤣. I mean, i didn't feel empowered when I transitioned to using LLM for coding after 18 years as a programmer. Becais3 it is just another new tool. For the unskilled, it is an empowerment.
And I think I now understand where the Dario is coming from.
LLM is typically shipping labor and skills to everyone. Including people who shouldn't have it.
Yea LLM coding is the greatest skill export at the moment. Where the unskilled feel empowered. Yea I agree.
But here is the thing...
This is my 18 years as a programmer. Coupled with the fact I was in 3D/Video industry for years before I jumped into coding.
A prompter can't do what I do.
7 years ago I wrote Aiwa that did over $2m. All by hand using notepad++ . I have not seen a prompter that has the skill to reolicate that even with AI aid.
During this AI coding era I have gotten more jobs that before AI coding. Nobody is going to trust their idea with a prompter.
I use Gemini now and have been using it for the past 2 years. What I have built with it, no prompter can dream of doing it using Fable.
And nobody out there is going to use a prompted project. Maybe you all take a work outside and feel the world outside of the twitter echo chamber.
People are hiring skilled programmers and giving them AI because of speed. People are still paying for SaaS products. My Jvzoo friends are still doing 200k to 450k just like before.
And I love that I am using LLM to code now. It means faster iteration and I dont have to type a shit.
And if anything happens and LLM is banned, I and those like me will return to what we ve always done, with more experience. The prompter will return to nothing, because they ve learnt nothing.
People pay for the kind of thing this guy does. Fear mongering. People has build something more complex that "inbox". And none of those long list you dropped there is a standalone requirement.
Yes, you can now build an inbox in an afternoon.
Congratulations, you are now responsible for:
- Deliverability.
- Bounce management.
- SPF, DKIM, DMARC.
- A domain that slowly drifts into spam.
- Finding out it why the hell it's drifting into spam?!
- Parsing emails from a mail server last updated in 2007
- HTML, plain text, and emails somehow containing neither.
- Outlook’s interpretation of HTML.
- Outlook’s other interpretation of HTML.
- Threading that breaks when someone changes the subject.
- Someone starting a new conversation by replying to an email from 2022.
- Forwards inside forwards inside forwards.
- CC, BCC, reply-all, and someone who really shouldn’t have clicked reply-all.
- Attachments.
- Attachments with malware..
- Inline images that become attachments.
- Attachments that were supposed to be inline images.
- A company logo attached to every reply, forever.
- Quoted replies.
- Distinguishing a quoted reply from the actual reply.
- Someone answering your five questions inside the quoted reply.
- Signatures longer than the conversation.
- The out-of-office that answers your out-of-office.
- Two autoresponders having a productive weekend together.
- Notifications that fire twice.
- Notifications that never fire.
- A reply sent from the notification itself.
- A reply to a notification about an internal note.
- Making absolutely sure that notes stays internal.
- Permissions.
- Two teammates writing the same reply.
- Drafts that sync across devices.
- Drafts that overwrite other drafts across devices.
- A confidently displayed “Saved” that was optimistic.
- Snoozed conversations.
- Time zones (!)
- Daylight saving time (!!)
- A conversation snoozed until a time that technically doesn’t exist.
- One customer showing up as three people across email, chat, and Slack.
- Three different people sharing one email address.
- Merging them.
- Undoing the merge.
- Search.
- Search that finds the thing you can literally see on screen.
- Webhooks arriving twice.
- Webhooks arriving out of order.
- Webhooks not arriving.
- Retrying a failed send without sending the customer six apologies.
- Rate limits you discover during your first traffic spike.
- Training your AI on your product.
- Scraping your website.
- Scraping the pages that need JavaScript.
- Not scraping your entire website footer into every answer.
- PDFs.
- PDFs that are actually pictures of PDFs.
- Keeping the content fresh.
- Knowing when content changed.
- Knowing when content disappeared.
- Making the AI forget the pricing page from last year.
- Conflicting answers across your docs, website, and past replies.
- Deciding which one wins.
- Chunking.
- Embeddings.
- Reindexing everything when you change embedding models.
- Retrieval that finds the answer, not just something with similar words.
- Web search tooling.
- Knowing when to search.
- Prompt injection hiding in a page you just scraped.
- An agent confidently promising a feature you don’t have.
- An agent confidently issuing a refund it shouldn’t.
- Tool permissions.
- Tool timeouts.
- Tool retries that issue the refund twice.
- Knowing when to hand off to a human.
- Actually handing off to a human.
- Not continuing to argue after handing off to a human.
- Evaluating whether any of this works.
- Evaluating it again after a model update.
- Token budgets.
- Context windows.
- A customer pasting an entire novel into the chat.
- WebSockets.
- WebSocket authentication.
- Reconnecting WebSockets.
- Reconnecting 10,000 WebSockets at once after a restart.
- A connection that looks alive but isn’t.
- A phone switching from Wi-Fi to mobile data mid-message.
- Messages that arrive once.
- Messages that arrive in order.
- Messages that arrive.
- Syncing read states.
- Unread badges.
- Typing indicators that stop typing eventually.
- A customer opening your widget in six tabs.
- Anonymous users becoming logged-in users.
- Logged-in users logging out on a shared computer.
- The iPhone keyboard covering the message composer.
- Safari.
- Keyboard navigation.
- A widget that must not slow down the actual product.
- Explaining that “sent” and “delivered” are different things.
- A help center.
- An editor.
- An editor that survives pasting from Google Docs.
- Images.
- Image resizing.
- Broken images.
- Article drafts.
- Autosave.
- Version history.
- Restoring the version before someone deleted half the article.
- Reordering nested categories without losing an afternoon.
- Slugs.
- 301 Redirects when slugs change.
- Internal links that now point nowhere.
- Working out which translations need updating after an edit.
- Search that understands what customers mean.
- Custom domains.
- DNS verification.
- SSL certificates.
- Renewing SSL certificates.
- Someone putting Cloudflare in front of your Cloudflare.
- Mobile layouts.
- Dark mode.
- Code blocks.
- Tables on small screens.
- Sitemaps.
- Canonical URLs.
- Accidentally indexing draft content.
- Accidentally deindexing published content.
- Cache invalidation.
- “I published it. Why does it still show the old version?”
- Making sure your AI sees the new version too.
- Spam.
- Phishing.
- Someone uploading malware as “a screenshot of the issue.”
- Someone pasting their CC details into chat.
- Someone asking you to delete every trace of that CC.
- Logs that also contain the CC.
- Backups that also contain the CC.
- Backups.
- Restoring backups.
- Discovering those are two separate features.
- An expired token.
- A background job that quietly stopped on Thursday.
- “Disk is full.” Sunday. 3 a.m.
- Monitoring all of this.
- Monitoring the monitoring.
Now you have two jobs 🤷♂️
To make an IOS/Android app is so easy.
Any Startup, firm that focuses on IOS alone shouldn't have your money. It simply means they dont respect their customers enough.
Any @antigravity team, pls fix this issue in the IDE where if pc shuts down for any reason at all, starting the IDE again the last conversation is nowhere to be found.
And what makes this issue more frustrating is the conversation file is store in the antigravity bran directory. So why is this issue still unresolved after many months?
Conversation should be persisted permanently on init. And lingering conversations should be recovered cleanly.
This shouldn't be a big deal guys
Gemini will lither your codebase with fallbacks. Those kind that hides real issues and degrades experience.
Be watchful! The enemy comes to steal and .... destroy 😒
Because they re folks who lacks the ability to create stuff by themselves. And when others do, they be like
" I dont like the color choice so I made made mine"
"I detest this icon pack so I made mine using that icon pack"
"The performance is so bad, I made mine and it is 10000000000x faster"
Dudes can't make things even if there lives depends on it.
I dont think you have the moral standing to say that. You re an animation guy not a developer. If you re a developer you would spent time building proper codebase.
It's time to stop using slow programming languages.
I don't think you understand the magnitude of this situation.
Let me explain.
Readers added context they thought people might want to know
The video uses final benchmark numbers from a Rust implementation refined over hundreds of commits with extensive performance work versus Elixir/Go ports with only a few commits and minimal optimization.
github.com/basecamp/once-…
github.com/basecamp/once-…
github.com/basecamp/once-…
github.com/basecamp/once-…
github.com/basecamp/once-…
x.com/josevalim/stat…
Beware of their guardrails that even flags AI generated image. Unless you re using text to video then it's fine.
I would think this is a ragebait if I haven't been seeing your bad takes. You think people with 17 followers dont know a bad take because they have 17 followers? 🤣
