
•software engineering and economics •I hike sometimes 🏔️ • @1337FIL Alumni 🇲🇦
Joined August 2011
- Tweets4.7K
- Following930
- Followers1.9K
- Likes10.6K
Mouad_Sidqi.ts retweeted
PDFs in React Native often mean a WebView or a bundled PDFium. react-native-better-pdf skips both: Nitro Views on the New Architecture, PDFKit on iOS, PdfRenderer on Android, virtualized pages. Already at 10k weekly npm downloads, nice one @jkasprzyk17 :)
github.com/gmi-software/reac…
Mouad_Sidqi.ts retweeted
most developers would do much better just using one AI chat a time and actually think about what they are doing
too many of y'all larp
Mouad_Sidqi.ts retweeted
My advice to men is to just bury your feelings.
Nobody cares. Nobody has or will ever care. It'll bother them that you do. Doesn't matter.
Lock in and just do the thing.
Somebody needs to do the thing. That's you.
Mouad_Sidqi.ts retweeted
Replying to @overflowyouknow
Sprite Stacking. They used to do this in old SNES JRPG games for bosses that needed to look 3 dimensional
Mouad_Sidqi.ts retweeted
One of the reasons Shopify rewrote their mobile apps from React Native into native was to improve performance metrics like startu p time. Here's the new, optimized, native Shopify Shop app compared to the same thing in Exact. The Exact version is talking to the same GraphQL API and fetching the same data. (Yes, I'm sure Shopify could make their Swift app as fast to startup with some time and tokens.)
Mouad_Sidqi.ts retweeted
I want to share a preview of something I've been working on called Exact. It's a new Agent Native app framework written in Rust. It's extremely fast and tries to let you build exactly the experience you want with no compromises.
Mouad_Sidqi.ts retweeted
Software engineers have been adapting to technology changes and paradigm shifts for decades (compare your SWE stack today with what it was 20 years ago). In this regard, we were much more prepared for AI to dramatically change how we build software (i.e., we almost write no code manually anymore).
AI can produce very high-quality code, especially if you know how to guide it well. However, I'm worried about one thing: The people getting most value out of LLMs and AI coding agents today are the experienced software engineers who cut their teeth writing code manually for decades and have good intuitions on how to build good software.
I wonder what will happen to the next generation of SWEs who never wrote code and their entire experience was prompting AI agents to build stuff, add features, and fix bugs.
it's shocking that software engineering has transitioned to 100% AI written in such a short time.
it's more shocking that somehow we, the SWEs, are all just continuing on as if nothing happened. It writes C++ better than I ever could, but the problem of making sure it works didn't magically disappear. we are just shipping enormously more volume at higher quality.
Mouad_Sidqi.ts retweeted
Just wanted to defend the term "Software Factory" for a second.
First, the caveats:
It's bullshit. It sounds fancier than it really is.
It's a bandwagon. People are using it to get you and their VC's hyped.
But it's also referring to a real change.
Earlier this year, most SOTA teams were using agents to work on the product. Shipping features, fixing bugs.
But now, they're building automations to help agents work on the product for them. They've moved up a layer.
What do we call the thing they're building? Loops? Workflows? Some other generic label?
"Software Factory" is as good a term as any other.
- "We're not working on the product, we're working on the factory that builds the product."
- "We're not product engineers, we're factory engineers."
I like it. I'll continue using it.
Mouad_Sidqi.ts retweeted
Anyone who says a social network wants bots is deeply mistaken. Human interaction is already scarce on social networks, since most people are passive consumers.
Bots displace this scarce resource:
Each bot reply means one human reply is not seen or engaged with by another human.
It’s nearly a 1-to-1 drop in product & business value—and likely has much bigger compounding losses when you account for people churning out of frustration.
Mouad_Sidqi.ts retweeted
"Most hardware engineering is actually software engineering in disguise."
12 years ago I founded Boom, as a software engineer doing hardware for the first time. I’m probably the least handy founder in hard tech. My 12 y/o son does my soldering and 3D printing for home projects, and I’ve struggled with imposter syndrome the whole way through. What business does a software guy have building supersonic jets and turbines?
More than a decade in, the most insane realization is that software is the key to reaccelerating hardware engineering. But in a way that I don’t think is widely understood or implemented, even in the burgeoning hard tech community.
Most hardware engineering is actually software engineering in disguise. It’s spreadsheet “code,” engineering calculations done as one-offs. Eg wing structural loads in, spar sizing design out. Thermal loads in, air conditioning system sizing out.
Everything is a calculation, and calculation is software. But these calculations are done essentially by hand, as if we are doing arithmetic but have not yet discovered algebra.
Hardware engineers have baby software, built in spreadsheets, the kind of crappy software I wrote as a kid before I understood architecture, unit tests, APIs, version control, and everything else that makes modern software good.
Our airplanes and engines are built with the software sophistication of a script kiddie.
So what we tell our engineers: don’t design the hardware, design the *algorithm* for designing the hardware. And take the algorithm seriously—as an algorithm and as a first-class engineered software system.
Never design a piece of hardware, such that you couldn’t redesign it tomorrow with a different set of assumptions.
This all sounds obvious, yet our experience at Boom is that it changes everything.
Ten years ago we couldn’t afford to build much software. We had a small team—and there were few software engineers with the curiosity, brilliance, and vision required to learn hardware engineering.
But now AI changes the equation. Now everyone can code. The software engineers define the architecture. The hardware people bring the physics and engineering know-how.
We have a turbomachinery design tool that lets one engineer do in realtime what previously took 100 engineers six months. Another tool auto-generates 65% of entire aircraft structure. I’m sure we’ll figure out the other 35% too. Eventually these should not be multiple tools, but one integrated physics model of a complete vehicle, airframe and powertrain.
The results speak for themselves. A boomless supersonic airplane built by 50. A full scale supersonic turbine made by 150. And with this approach, I don’t think we’ll need that many more people to build and certify a supersonic airliner.
You don’t need a big team to build big things—not when everyone on the team is a software engineer.
Mouad_Sidqi.ts retweeted
Devs a year ago: "Code is a liability. PR's that delete 100 lines of code >> PR's that add 1,000 lines"
Devs now: "This ai slop canon can produce 50,000 lines of unreviewed code a day and you'll destroy this company's future if you delay it from merging"
It’s actually crazy how X makes you believe the entire world is falling apart every single day.
Another war, another crisis, another headline about how we’re all fucked.
Then you go outside and realize everyone is just living their normal lives, going to work, eating at restaurants and enjoying themselves.
Sometimes you just need to close X, stop consuming all this fear and go enjoy your life. The algorithm makes you believe that everything is negative and bad.
Mouad_Sidqi.ts retweeted
‼️ Apps built with the AI app-maker Lovable left passport numbers, payment information and 200,000 chat messages open to anyone, no login needed.
German security firm Crissy Field scanned 159,041 Lovable projects and found databases with email addresses readable on 7,403 sites.
Lovable promises no coding skills are needed. Its terms make customers responsible for their apps and data.
Lovable told German business daily Handelsblatt the problem is industry-wide.
Mouad_Sidqi.ts retweeted
Apple can't keep up with app review right now, and you can see it in their own numbers
Their website says about 500 people review 130K apps a week
In April they said it was 200K a week. Last month, 378,000
That's almost 3x the volume still listed on their website. Developers report new apps sitting in Waiting for Review for weeks, some over a month, while Apple says minor updates average 14 hours
Apple's response is that the average is still 1.5 days. Sure, but averages hide the queue. If you're a first-time dev with a brand new app, you are the queue
What I'd do if I were submitting my first app this month: add a demo login, write real notes, and link a screen recording the first time. Apple says it themselves, incomplete submissions get rejected. And a rejection right now can cost you weeks



























