In honor of the launch day we have today at @directus, here are some historical facts about the word "LAUNCH" 🚀 The Middle English launchen (around 1300s) meant things like “to rush,” “leap,” or “set suddenly in motion.” It came from Old French lancher/lancier, meaning “to fling, hurl, or throw.” And that leads to a lance. The French word ultimately comes from Late Latin lanceare, “to wield a lance,” derived from lancea, a light spear. So launch and lance are relatives. Around the 1400s, “launching” a ship meant putting it into the water. Then it became metaphorical. By around 1600, launch was being generalized to mean starting or setting something in motion (business, career, product). Rockets are surprisingly recent. The use of launch for the liftoff of missiles and spacecraft dates only to around 1935, while launch pad appears around 1960. There’s a linguistic curveball: a launch, meaning a type of boat, appears to have a different origin from the verb to launch. That noun entered English in the late 1600s through Portuguese lancha. The spelling seems to have been influenced by the already-existing English verb launch.

Working from home is great… until you realize you haven’t seen your colleagues in person for too long. 😄 So I turned a regular workday into a little adventure and flew over to France for the day. 🇫🇷

Today I tried a new AI workflow - "Rolling Wave Engineering" by @rijkvanzanten 🙌 Most of the AI workflows base on the idea that you develop a plan with your AI from start to finish. So you know exactly everything that is coming out the end. And then let AI write the whole thing. For people like me, who like to be more in the code rather than just writing a plan document for 3 days that doesn't work. What Rijk is proposing is a system that uses AI to help you do a workflow very closely as you would do in the pre-AI era. Instead of planning everything out beforehand, you build our feature step by step. Or "slide by slice" to use the framework nomenclature. You prepare a slice, implement it, test it, review it. There are nice guards to make sure each of the parts you build is solid (from start to finish). You also don't need know which pieces exactly you need to move/implement for your feature to work. You start with a general idea and in each slice explore and concreticize together with AI what you exactly need. You can also just skip the implementation of a step and do it yourself. And let AI do everything around it. I feel like this keeps me way more in the driver seat as other methods. I'll let you know the coming days or weeks how this experiment continues. If you want to give it a whirl, here's the repo 👇 github.com/rijkvanzanten/rol…

There are so many exciting things going on at @directus, it’s mental! Very soon we will be able to show you what we’ve been working on besides the incredible Directus v12. It feels unreal being a part if all this 🥹

As I have mentioned a few times already, we still need GREAT ENGINEERS. At @directus we are looking for Senior Rust engineers 🦀 Check out this opportunity to work with a phenomenal team 👇 directus.io/careers/senior-b…