OutSystems Champion

OutSystems Champion

Good morning! And what a great morning it is today!

Keeping a secret is hard. Keeping a secret for weeks with a brain like mine? That’s not just a challenge; that’s an Olympic sport. 😅

My mind has been running at 200% capacity trying not to blurp this out, but today I can finally release the pressure valve:
I am incredibly excited and honored to announce that I’ve been named an OutSystems Champion!

Low-code has been my favorite playground for 8 years now, because it moves as fast as my thoughts do. To be recognized by the OutSystems community for doing what I love is something I’m truly grateful for.

Huge thanks to everyone who supported me on this hyper-focused journey. Now, if you’ll excuse me, I have about 42 other open tabs to attend to, but this time, I’m doing it as a Champion.

https://www.linkedin.com/posts/erijsewijk_oschampions-lowcode-milestone-activity-7422156518369792001-J-sR?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAAREY4BDtrrDS-i15-4nEOtIpIpIUuQ_0U

From Spaghetti Code to Low-Code: Refactoring My Internal Architecture

From Spaghetti Code to Low-Code: Refactoring My Internal Architecture

The Introduction: Critical Errors in Service Center

You’re a Senior Developer. You can map out a complex 4-Layer Architecture in your sleep. You’re the one they call when the production environment is showing “504 Gateway Timeouts” on a Friday afternoon, right when the client is trying to bulk-process ten thousand invoices.

And yet… my internal Service Studio keeps throwing Communication Exceptions on the most basic tasks. Entering working hours? Request Timeout. Finishing a grocery list? Aborted by User.

Does that sound familiar?

https://medium.com/@erwinvanrijsewijk/from-spaghetti-code-to-low-code-refactoring-my-internal-architecture-d0ef32a9032e