Tim Marois

Tim Marois

@marois.dev

Building web apps since 2006 marois.dev

226 followers125 following268 posts

Tim Marois reposted

Replying to @flo-bit.dev

i tried a 3d version, looks cool but doesnt really make it less chaotic ๐Ÿ˜…

Charlotteโ€™s skyline never disappointsโ€”such a beautiful city. For all my US friends, I hope youโ€™re planning something fun for Thanksgiving this week! ๐Ÿฆƒ Recharge and relax.

Accidentally closed a tab? Use Ctrl + Shift + T (or Cmd + Shift + T on Mac) to reopen your last closed browser tab. #SavedYourLife

Tim Marois reposted

The decentralized identifier (DID) is a core component in the ATMosphere. ATProtocol supports both did-web and did-plc methods, but most accounts here use the did-plc method. It comes with some powerful security features that are good to know about.

Thanks to the #ATprotocol weโ€™ve reached the internet endgameโ€”no more starting over, and best of all for content creators to actually own their data. Looking forward to the explosion of new apps all connected and sharing one global community.

All online services with public profiles should use the same domain verification process as @bsky.app for customized user names. This will prevent people from scalping names and give authenticity and official brand ownership. I see you @github.com.

As a fun side project, Iโ€™m rethinking the browser start page. After all, the browser is the new desktopโ€”so why not give you full control over the widgets, layout, and functionality. @vuejs.org and @vite.dev are the perfect tools for this mini-product.

Tim Marois reposted

Brands should use their actual domains on Bluesky instead of .social, it kind of defeats the purpose of understanding who is official. Just a thought after seeing multiple brands create a new domain.

Debugging isnโ€™t just fixing errors; itโ€™s understanding the why behind them. Master your tools, log intelligently, and embrace the hunt.

In my role, every decision shapes the team, the product, and the vision. People rely on me to lead, guide, and deliverโ€”but success is always a team effort. ๐Ÿ’ช #Leadership

Tim Marois reposted

Dev pro tip: Donโ€™t optimize prematurely. Write clean, functional code first, then refactor for performance once you have a working solution.

Some interesting new features coming to PHP 8.4 ๐Ÿ”ฅ

Laravel News@laravelnews.com

๐Ÿš€ PHP 8.4 is almost here! Get ready for Asymmetric Property Visibility, a cool feature that changes how properties can be accessed and modified. It lets you choose different levels of access for reading and writing data. Keep an eye out for more updates! https://laravel-news.com/asymmetric-properโ€ฆ

Building an entire platform/CRM in record time with Inertia.js has been incredible. ๐Ÿ”ฅ It simplifies complex requirements and continues to impress while reducing the dev effort. (Invelo 2.0 relaunch Feb 2025)

Throwback: Welcome to the command center. Where code meets data, and we keep the ship sailing smoothly. ๐ŸŒŒ ๐Ÿ’ป #CommandCenter

Tim Marois reposted

Released in 2.2.0-beta.2 and it's even smoother now! Here's comparison of latest Vitest on left vs beta on right. Flickering is gone and now you can scroll up to see results without scroll jumping. And of course there's the status summary of active test run on the bottom. github.com/vitest-dev/v...

AriPerkkio@ariperkkio.dev

Hello ๐Ÿฆ‹! Here's sneak peek into Vitest reporter improvements I've been working on for a while now. This reduces terminal flickering, fixes scroll issues and adds status summary. It's still WIP but looking really good so far!

Donโ€™t aim for perfection in your first product release. Focus on delivering a working MVP, gather feedback, and iterate. Progress > Perfection. #StartupTips #ProductDev

Sunday evenings are for reflection and setting intentions. - What went well last week? - What will you improve this week? Plan it. Own it. Crush it. ๐Ÿš€ #sundayretro #weeklygoals

Throwback: before chatGPT reading every php book I could get my hands on. Seems like everyone is posting books, hereโ€™s mine

Dev pro tip: Donโ€™t optimize prematurely. Write clean, functional code first, then refactor for performance once you have a working solution.