
Building Shopify apps @PunchyApps
w.w.w.
Joined April 2022
- Tweets400
- Following434
- Followers297
- Likes1.3K
maxico ✨ retweeted

DHH@dhh2 Dec 2025
🇩🇰
DenmarkConnected via United States App StoreAccount-level information, not a live location or per-post device.
Fizzy is live! Our modern, beautiful spin on kanban for tracking just about anything. Nothing revolutionary, but just right, just nice. And we're launching our freemium SaaS version alongside an O'Saasy-licensed codebase for you to run it yourself too! fizzy.do
maxico ✨ retweeted
🚀 New feature alert! We’ve added a Customer Account Extension that lets shoppers see all their active gift cards & balances right from their account. 🎁✨
👉 apps.shopify.com/checky-gift…
#shopify #giftcard #ecommerce
maxico ✨ retweeted
Hey DTC folks! 👋 If you want an easy way to keep customers coming back, try our free Creditback app. Customers earn store credit and claim it daily - it’s kinda fun 😎 Give it a shot: apps.shopify.com/rebo-credit…
#Shopify #ecommerce #dtc
maxico ✨ retweeted
Python has crazy forecasting libraries.
Let me introduce you to Kats, by Meta (Facebook)
maxico ✨ retweeted
I'm so excited to announce that the new version of Ratatui is released today! 🐁🎉 (@ratatui_rs)
🦀 A Rust library that's all about cooking up terminal user interfaces.
✨ Release highlights: ratatui.rs/highlights/v026/
⭐ GitHub: github.com/ratatui-org/ratat…
#rustlang #tui #library #terminal
maxico ✨ retweeted
Eight Years running 🏃🏻, #Rust has been voted the most desired software language by software engineers.
This is a metric worth noting.
We can look at solana, deno, polkadot, tauri, and any other major rust open source projects - dive into any of their codebases - and immediately see the quality of code which is being delivered.
You’ll notice a minimal amount of code ase regressions, high quality engineering talent attracted by rust, & rarely really bad code or low quaility devs due to rust being harder to learn/use acting as a gatekeeper that keeps engineers that aren’t “at least better than average devs” away.
Why do I say healthy barrier of entry?
Don’t we want all of our engineers to be able to easily dive in and just start coding away?
Heck no, we absolutely don’t want that!
Now, in all fairness - this is a very debatable topic - so feel free to kickstart a debate in the comment section below👇
With that said, I believe a healthy difficulty level for the barrier of entry to being able to contribute code to a repo slows engineers down & eliminates instinctually lazy practices that all catch us now and then when we’re tired and others all to frequently by lack of willingness to try.
Rusts healthy barrier of entry sets it up so bad stuff doesn’t get into our code base.
Rust’s difficulty level when learning the language curves away low quality talent during the interview process and even if a bad apple sneaks thru, the compiler doesnt let them break anything in exponentially bad ways that we’ll only truly catch two to three years from now
Nope, rust as a language makes it easy to spot good & bad engineers when hiring or recruiting & the compiler keeps a large amount of bad code from ever reaching runtime.
This is, at times, frustrating - the difficulty that comes with learning and building rust that is; but once a dev does get rust code to build and it’s able to run — then at that point the business can be pretty dang confident that the code is built well enough to scale; be secure; have minimal runtime bugs; be performant; and be secure with safe memory management implemented.
Ultimately, thru rust’s difficult barrier of entry and strict compiler we’ve eliminated an exponential amount of regressions that would each act as a red light or stop sign for us during our journey to building the technology we’re building.
With rust, we catch those regression causing bugs now, as we the devs build it. Time spent finding bugs during regressions is saved.
The love for rust attracts good talent while the difficult entry into rust attracts simplifies recruiting by organically demotivating potentially lazy devs who are unwilling to dive a bit deeper to understand systems programming and lower level memory management the other way - understanding a systems language like rust covers a similar concern as data structure & algorithms rounds as well, it shows a dev can dive into the tedious details for months on end.
#rust #rustlang #coding
maxico ✨ retweeted

DHH@dhh29 Jan 2024
🇩🇰
DenmarkConnected via United States App StoreAccount-level information, not a live location or per-post device.
We’ve tested Raspberry Pi 5 with ONCE/Campfire. Running on an SD Card for disk, we were still able to easily see 250 concurrent users (and outside of a longer reconnect delay, easily above 1,000 too). Love it. Will explore some fun physical ONCE products from this.
maxico ✨ retweeted
📣 Announcing @yaakapp – a minimal REST and GraphQL client built with @TauriApps
maxico ✨ retweeted
I've written multiple blog posts over the past few years. From someone trying to destroy our company, to nearly moving our application to DynamoDB, to leaving MySQL behind, to re-writing our entire application, to asking does Laravel scale? Check them out.
xitter.cf/JackEllis/highlights
maxico ✨ retweeted

Taylor Otwell@taylorotwell20 Jun 2023
🇺🇸
United StatesConnected via United States App StoreAccount-level information, not a live location or per-post device.
This month marks 12 years of Laravel. Let’s push for another 12. ❤️
It’s been a joy to build Laravel with all of you.
maxico ✨ retweeted

Taylor Otwell@taylorotwell24 May 2023
🇺🇸
United StatesConnected via United States App StoreAccount-level information, not a live location or per-post device.
We've just launched a new page giving you all the details on why we believe Laravel makes for a radically productive full-stack framework that pairs perfectly with the front-end you already love. ❤️
laravel.com/frontend
maxico ✨ retweeted
Final Product Hunt Update!!
🔼 570 Upvotes 🥹
💰 $574 Revenue
💭 133 Comments
⏳ 9 Lifetime Deals for $14 left!
Gonna take a break from the internet today to let this sink in and to recover from the absolute BLAST that was yesterday.
Love you all ❤️
maxico ✨ retweeted

DHH@dhh4 May 2023
🇩🇰
DenmarkConnected via United States App StoreAccount-level information, not a live location or per-post device.
"Now the real-world results of all this theory are finally in, and it's clear that in practice, microservices pose perhaps the biggest siren song for needlessly complicating your system." world.hey.com/dhh/even-amazo…
maxico ✨ retweeted
I've recently 🚀 launched: laravel-package-ocean.com
Still working on it. I hope the @laravelphp community finds it useful 😊🌸👍
Let me know your thoughts on it!
maxico ✨ retweeted
🧩 One of the ways we keep maintenance burden of @spatie_be packages low is by making our packages customizable.
🧠 Here are a couple of strategies we use for that!
freek.dev/2442-strategies-fo…
#php #laravel
maxico ✨ retweeted
All your questions about Editions, answered! Join @tobi live now on Twitter Spaces.
xitter.cf/i/spaces/1zqJVPbdNmVKB
maxico ✨ retweeted

Matt Pocock@mattpocockuk17 Feb 2023
🇬🇧
United KingdomConnected via United Kingdom Android AppAccount-level information, not a live location or per-post device.
Just made three pull requests to @calcom to improve their types in small, subtle ways.
Take a look! You might learn something.
maxico ✨ retweeted
How to identify a senior developer reddit.com/r/programmerhumor…





















