Lukas Gjetting

• 25 y/o from Copenhagen, Denmark
• Coding since 2011, making internet money since 2012
• 110-120 WPM (profile)
• Have worked professionally with...
  • React and React Native since 2016
    yup, back in the pre-autolinking days
  • Next.js since 2018
    though less in the recent years
  • TypeScript since 2021
    and haven't looked back since

GitHubLinkedIn

Experience

BravoShop (2022-now)

I am currently occupied by my own project called - a no-code app builder for Shopify merchants. The platform is built in TypeScript, with Node, tRPC, React and React Native (and the landing page is built in Next.js).

What a match!

Because of React Native's cross-platform capabilities (h/t react-native-web), I'm able to render the actual app as part of the builder. Instead of just having a mock-up like many similar tools. All this without making compromises on the native feel of the resulting app.

While launching a thing from scratch is hard, there is nothing that beats the joy of building cool projects

P.S. Let me know if you want to walk through some of the BravoShop codebase. I'd be happy to show you around!

Freelance (2021-now)

Since BravoShop is still in its early stages, I have been doing some consulting work on the side. Mostly app development (React Native), but also a bit of web dev.

ClearVoyage (2020-2022)

I was the first employee, hired to help the CTO (and co-founder) build out their MVP in Node and React.

In late 2021, our engineering team had grown to 5, and we were experiencing major problems with the way we developed software. Especially our PR reviews, often filled with tons of code-style nitpicks, were hurting morale. Often, we would have reviews with dozens of comments, of which only a few were actually meaningful.

I lead the effort, and eventually the team, to combat this tendency. My initiatives included writing a ton of custom ESLint rules via no-restricted-syntax, publishing a few small open-source ESLint plugins (such as eslint-plugin-parentheses-single-line-jsx) and setting up a handful of new GitHub Actions checks, that would run against PRs.

These new automations allowed us to focus our PR reviews on what mattered: Providing detailed, in-depth feedback.

Table Butler (2018-2020)

My first try at building a company (with a friend). A table booking platform for bars and night clubs, which they could embed into their Facebook page.

I was responsible for building the platform (Node, Express, React, Next.js).

We spent about a year and a half before shutting down, as we were unable to find any sort of product-market fit.

Restaurant 2 Night (2016-2019)

At Restaurant 2 Night, I got introduced to both React and React Native. I was hired as a high school student to help rewrite their previous native apps in React Native.

My main responsibility was to implement the design for their components.

To acknowledge my enthusiasm, fast learning and focus on quality, I was given the responsibility of all new app development.

How did I get here?

As mentioned, I started writing code back in 2011 when I learned that it was possible to make arrows in Minecraft explode on impact (how cool is that?!). Soon after, I got into web development.

At 15 years old, I had completed a series of freelance gigs. Most of them were very small, often less than $100, but some around $1000. What a rush! Making money. From home. Doing a task I enjoyed! It was almost unbelievable.

Since then (just realized it was 10 years ago...) I have gotten deep in to React, React Native and later TypeScript.

Every since learning to code, I have had an insatiable need to build cool stuff. When I'm not spending the weekends with my wonderful fiancée, you can probably find me building a new app or tool.

When I first started exploring React Native, I was blown away. Amazed by the React Native team, who had the audacity to think that React could (and should) power native apps. But also amazed by the tech that allowed React to render actual, real, just-as-intended native views.

What I had previously thought of as the core of React (mapping the component tree to actual DOM elements) was actually not done by React itself. Rather, it was done by react-dom. And interestingly, react-native was "simply" another "mapping engine" (or rather, reconciler).

Why Wander?

For the past few years, I have been wandering (hah). Feeling like a mercenary. Lacking direction.

For the past few months, I have been looking for a new path forward. A path where I can learn and grow. Where I can apply my skills. Where I can be in it for the long run.

And when I saw John's Twitter post, and his description of the things you value, it struck a chord. I miss working in a team. Sharing the highs, and the lows. I miss working towards a shared vision of a better future.

And I think I can be a valuable part of your team. Both on the technical side, and the personal.

Looking forward to hearing from you!