Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it.
When I opened the box of my Roomba back in 2016 there was a sticker saying:
This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so.
A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time).
While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself.
Although it may sound a little over-engineered here’s my current project:
Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker.
At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all? +
Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it.
When I opened the box of my Roomba back in 2016 there was a sticker saying:
This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so.
A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time).
While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself.
Although it may sound a little over-engineered here’s my current project:
Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker.
At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all? We grow by learning on new impulses, not by locking ourselves into our comfort zone.
There are few technologies that change as often as web frontend tools, libraries and technologies in the recent years.
With a focus on web development at AOE we have been on the bleeding edge ever since, evaluating and understanding what technologies bring us forward.
Sharing knowledge and experience is what we love, but it took us a long time to establish a format where interested people come together on a regular basis, talking about the newest tech, all cross-team and cross-project.
Keycloak is our go-to tool when it comes to identity management, federating identities over multiple sources and organizing and managing roles for all kinds of applications. Naturally, there is no “one-tool-fits-all”, so Keycloak too sometimes needs to be customized beyond what the configuration offers, and we need to implement providers to add additional configuration.
Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it.
When I opened the box of my Roomba back in 2016 there was a sticker saying:
This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so.
A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time).
While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself.
Although it may sound a little over-engineered here’s my current project:
Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker.
At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all? +
Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it.
When I opened the box of my Roomba back in 2016 there was a sticker saying:
This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so.
A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time).
While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself.
Although it may sound a little over-engineered here’s my current project:
Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker.
At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all? We grow by learning on new impulses, not by locking ourselves into our comfort zone.
There are few technologies that change as often as web frontend tools, libraries and technologies in the recent years.
With a focus on web development at AOE we have been on the bleeding edge ever since, evaluating and understanding what technologies bring us forward.
Sharing knowledge and experience is what we love, but it took us a long time to establish a format where interested people come together on a regular basis, talking about the newest tech, all cross-team and cross-project.
Keycloak is our go-to tool when it comes to identity management, federating identities over multiple sources and organizing and managing roles for all kinds of applications. Naturally, there is no “one-tool-fits-all”, so Keycloak too sometimes needs to be customized beyond what the configuration offers, and we need to implement providers to add additional configuration.
When I opened the box of my Roomba back in 2016 there was a sticker saying:
This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so.
A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time).
While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself.
Although it may sound a little over-engineered here’s my current project:
Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker.
Using an ESP32 microcontroller I was able to “bridge” the serial interface to MQTT and an HTTP api. Instead of implementing everything from scratch I used the Tasmota firmware. Tasmota is a great open-source firmware for ESP8266 and ESP32 microcontrollers that helped me doing getting started without any custom code on the microcontroller.
I used an ESP32-cam board (later more on the “cam” part). This board is cheaply available. Make sure you also get the dev-board since the ESP32-cam board itself doesn’t come with a USB connector and you’d end up fiddling around with additional components. The ESP32 runs on 3.3V (and most boards have a built-in voltage regulator for 5V, which is the USB voltage). But the Roomba connector only includes an unregulated output that can range from 15 to 17V. So we need to drop that voltage safely. While some people suggest using a cheap USB car carger this didn’t work for me so I ordered some MP1584EN buck converters. +
When I opened the box of my Roomba back in 2016 there was a sticker saying:
This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so.
A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time).
While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself.
Although it may sound a little over-engineered here’s my current project:
Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker.
Using an ESP32 microcontroller I was able to “bridge” the serial interface to MQTT and an HTTP api. Instead of implementing everything from scratch I used the Tasmota firmware. Tasmota is a great open-source firmware for ESP8266 and ESP32 microcontrollers that helped me doing getting started without any custom code on the microcontroller.
I used an ESP32-cam board (later more on the “cam” part). This board is cheaply available. Make sure you also get the dev-board since the ESP32-cam board itself doesn’t come with a USB connector and you’d end up fiddling around with additional components. The ESP32 runs on 3.3V (and most boards have a built-in voltage regulator for 5V, which is the USB voltage). But the Roomba connector only includes an unregulated output that can range from 15 to 17V. So we need to drop that voltage safely. While some people suggest using a cheap USB car carger this didn’t work for me so I ordered some MP1584EN buck converters. Roomba’s RX pin works fine the the ESP32 3.3V output, but the data returned from Roomba’s TX been needed an extra PNP transistor (I used an 2N3906) so that the signal was readable reliably. Since I also wanted to capture a video feed I replaced the OV2640 cam with a different fisheye lens with a longer cable. This is what my prototype board looks like:
Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
+ Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
We grow by learning on new impulses, not by locking ourselves into our comfort zone. There are few technologies that change as often as web frontend tools, libraries and technologies in the recent years. With a focus on web development at AOE we have been on the bleeding edge ever since, evaluating and understanding what technologies bring us forward. Sharing knowledge and experience is what we love, but it took us a long time to establish a format where interested people come together on a regular basis, talking about the newest tech, all cross-team and cross-project. Keycloak is our go-to tool when it comes to identity management, federating identities over multiple sources and organizing and managing roles for all kinds of applications.
Naturally, there is no “one-tool-fits-all”, so Keycloak too sometimes needs to be customized beyond what the configuration offers, and we need to implement providers to add additional configuration. Keycloak is our go-to tool when it comes to identity management, federating identities over multiple sources and organizing and managing roles for all kinds of applications.
+ Keycloak is our go-to tool when it comes to identity management, federating identities over multiple sources and organizing and managing roles for all kinds of applications.
Naturally, there is no “one-tool-fits-all”, so Keycloak too sometimes needs to be customized beyond what the configuration offers, and we need to implement providers to add additional configuration. Being a complex project, Keycloak can be intimidating at first glance, but once we learn how the general architecture and workflows look like we can precisely implement providers to fine-tune Keycloak’s behaviour. Let us take a look into what Keycloak does is when a user is authenticated, and see how we can implement such a provider: We can see multiple points marked with “SPI” (service provider interface). These are all the points where we can provide additional or alternative implementations, and alter the way Keycloak works.
Please note, some API’s are private, which means they can change in any way during Keycloak updates. So one has to be careful where and when functionality is added. In our example we want to implement a new token mapper, to have some claims mapped in a specific way.
To do this, we setup a small Java project in our favorite Editor, throw in some gradle build scripts (maven works too, of course!) and define our entry point and a marker for Keycloak to load our provider: At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
+ At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
We grow by learning on new impulses, not by locking ourselves into our comfort zone. That’s why we believe in Open Source as a chance to steadily keep learning from each other, beyond our companies boundaries. Over the past 20 years AOE’s people were always heavily involved in all kinds of Open Source projects, as users, contributors, maintainers. Beyond code we keep organizing community meetups, share experiences on conferences and strive towards an open exchange about new topics, technologies and tools. Take a look on our AOE Technology Radar if you are interested on technologies we find promising or have adopted in the recent years, and learn more why and how we decide on our tech stack. Of course, you find the source code on Github as well, check it out and build your own radar if you like. 5 years ago we set started the adoption of the Go programming language at AOE. 3 years ago we open sourced Flamingo, our web framework, created to enable us to build fast and scalable applications.
+ 5 years ago we set started the adoption of the Go programming language at AOE. 3 years ago we open sourced Flamingo, our web framework, created to enable us to build fast and scalable applications.
Now, looking back, it was quite a ride raising a flock of small Flamingo’s to form a stable basis for our daily work. But first, why even open source work we have spent hundreds and hundreds of hours on, for free? At AOE, we do not believe in gatekeeping, sharing our code enables us to join an open dialogue with everyone interested in building, growing and learning on a mutual code base. What is our learning in all these years? First of all, things change. Back in the days, we set for server side rendering using a custom PUG implementation in Go, to make sure we can always deliver the fastest and most optimized page, no matter what Browser people run. Nowadays, after many iterations, our default setup uses generated GraphQL code on the serverside, where Flamingo is the edge to all connected services and microservices, while the Frontend is a standalone React application, requesting precisely the required data necessary to render what we want to show. Remix now allows us to bring back the serverside rendering in a way that we can even support browsers with disabled JavaScript. This evolution was nothing we could predict, but we are grateful for all the learnings, all the contributions from the outside and the chance to let our Flamingo grow wings. Now we set out to fly even higher, focusing on making Flamingo accessible and lowering all entry barriers, so you can start right away with a free choice of your tech stack, be it gRPC, GraphQL, Rest, and include and connect any framework you’ve learned to love in the past. After all, this is about Open Source, and we love Open Source. Gitlab became our main tool for sourcecode and automation over the past 5 years.
+ Gitlab became our main tool for sourcecode and automation over the past 5 years.
Naturally, all of our build processes, continuous integration and delivery as well as platform management is completely automated, and Gitlab CI has proven to be a valuable tool. So how do we organize our pipelines at AOE? Initially, we have a repo which provides templates and starting points for all of our pipelines, so we can benefit from scaling to any number of microservices without having to think of management overhead. Each pipeline is a well-defined and small piece that declares it basic steps, such as “test”, “build” and “deploy”.
More complex pipelines are organized as sub-pipelines, e.g. deployments to multiple regions: Using these abstractions we can quickly roll out our applications to new clusters or changed infrastructure topology, while keeping fast build processes so our developers get a quick feedback on merge requests and commits. So, why do we not use something else than Gitlab CI? Having one tool helps a lot with keeping vital things close together, such as sourcecode, helm deployment definitions and necessary pipelines. Also, the feedback loop is short and allows for more effective work. After all, nobody likes waiting for pipelines reports. Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. A major part of the application can be configured via environment variables located in the .env file. If setting environment variable is not an option, like in shared web hosting, then create a .env.prod file and configure them there. Install application dependencies Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. A major part of the application can be configured via environment variables located in the .env file. If setting environment variable is not an option, like in shared web hosting, then create a .env.prod file and configure them there. Install application dependencies Create database schema Generate static assets A pre-built cloud installation image of meals can be found in docker hub. It is automatically updated whenever new features, security or bug fixes are introduced. The application configuration is same as in the hosted environment. However, no setup is required here. Not a problem. You can download the source code from Github on your local machine. The development environment is configured using In software development we tend to continuously update to the latest version. It keeps you up to date with the current state of development, it can provide you with new features or better performance. But it can also lead to frustration when the process is not as smooth as expected and brings completely new challenges which you did not have before. As we experience this in our daily work with moving from monoliths to microservices, from server to server-less, from SPAs to SSG, an update is currently also happening within the web itself. There is now a new “major version” called Web3. At this point it is getting complicated. What can we expect from this update? New features, bug fixes, breaking changes? As there is no such thing as a CHANGELOG.md for the Web itself, a short summary reads like this: Web3 promises to give users the full ownership over their content, data and all other assets they possibly could own… by utilizing blockchain technology. What we need to understand here first is that this “update” is not primarily technology-driven. It is more about people starting to avoid trusting big companies, banks or even countries. They aim for a system which is decentralized, transparent and trustless. And blockchain as the technology can provide this. It is even proving its concept since 2009 as the key technology behind Bitcoin. So does Ethereum, which even powers applications (dApps) running worldwide on a decentralized network. So does this mean we should migrate all our customers applications to some blockchain and we are done? Of course not. Before even suggesting this, we need to clarify the WHY first. Jumping on the hype train is easy, making something valuable out of it is not. And finally, we have to look into the HOW and start learning what it means to develop for a decentralized web. The Web3 is not just a new version you simply upgrade to. It is a new paradigm where people and machines can interact with data or property without the need of a third party in the middle. The discussions about Web3 and blockchain in general will remain controversial until we see more reasonable use cases. In the meantime we should keep our minds open for the things to come. In software development we tend to continuously update to the latest version. It keeps you up to date with the current state of development, it can provide you with new features or better performance. But it can also lead to frustration when the process is not as smooth as expected and brings completely new challenges which you did not have before. As we experience this in our daily work with moving from monoliths to microservices, from server to server-less, from SPAs to SSG, an update is currently also happening within the web itself. There is now a new “major version” called Web3. At this point it is getting complicated. What can we expect from this update? New features, bug fixes, breaking changes? As there is no such thing as a CHANGELOG.md for the Web itself, a short summary reads like this: Web3 promises to give users the full ownership over their content, data and all other assets they possibly could own… by utilizing blockchain technology. What we need to understand here first is that this “update” is not primarily technology-driven. It is more about people starting to avoid trusting big companies, banks or even countries. They aim for a system which is decentralized, transparent and trustless. And blockchain as the technology can provide this. It is even proving its concept since 2009 as the key technology behind Bitcoin. So does Ethereum, which even powers applications (dApps) running worldwide on a decentralized network. So does this mean we should migrate all our customers applications to some blockchain and we are done? Of course not. Before even suggesting this, we need to clarify the WHY first. Jumping on the hype train is easy, making something valuable out of it is not. And finally, we have to look into the HOW and start learning what it means to develop for a decentralized web. The Web3 is not just a new version you simply upgrade to. It is a new paradigm where people and machines can interact with data or property without the need of a third party in the middle. The discussions about Web3 and blockchain in general will remain controversial until we see more reasonable use cases. In the meantime we should keep our minds open for the things to come. There are few technologies that change as often as web frontend tools, libraries and technologies in the recent years. With a focus on web development at AOE we have been on the bleeding edge ever since, evaluating and understanding what technologies bring us forward. These days, Tailwind CSS is really pushing us forward, by making things easy and accessible for everyone. How does Tailwind CSS differ from classic CSS frameworks, or just plain reset.css and custom classes? Tailwind shines with to aspects: First, we get to focus on what CSS is designed to do. There are no buttons, no popups, only raw classes with minimal and well-defined features. Want to define a padding? Set Second, Tailwind only compiles required classes, not everything. By statically analysing your code Tailwind ensures no useless classes are bundled, making sure that you always bring the bare minimum. Being so simple with such a clear API, Tailwind even allows people with very little experience in frontend development to implement and adjust necessary components without breaking the whole design. Did you notice? This website is built using Tailwind too! Feeling adventurous? Try Tailwind together with React, and render everything on the server side using Remix. Now you’ll feel the whole speed of what’s possible on the web! There are few technologies that change as often as web frontend tools, libraries and technologies in the recent years. With a focus on web development at AOE we have been on the bleeding edge ever since, evaluating and understanding what technologies bring us forward. These days, Tailwind CSS is really pushing us forward, by making things easy and accessible for everyone. How does Tailwind CSS differ from classic CSS frameworks, or just plain reset.css and custom classes? Tailwind shines with to aspects: First, we get to focus on what CSS is designed to do. There are no buttons, no popups, only raw classes with minimal and well-defined features. Want to define a padding? Set Second, Tailwind only compiles required classes, not everything. By statically analysing your code Tailwind ensures no useless classes are bundled, making sure that you always bring the bare minimum. Being so simple with such a clear API, Tailwind even allows people with very little experience in frontend development to implement and adjust necessary components without breaking the whole design. Did you notice? This website is built using Tailwind too! Feeling adventurous? Try Tailwind together with React, and render everything on the server side using Remix. Now you’ll feel the whole speed of what’s possible on the web! Sharing knowledge and experience is what we love, but it took us a long time to establish a format where interested people come together on a regular basis, talking about the newest tech, all cross-team and cross-project. We failed multiple times, COIs/COPs are always centered around a common topic of interest, meetings during lunch were interrupted by delicious barbeque (shout outs to our chefs!), and finding even more timeslots in full-packed weeks led to distraction, less interest and never really took of. But there is one constant in AOE’s work-week, which is “the weekly”, where every Monday the whole company comes together (online, nowadays), to get the most recent updates about business development, teams, and so on. This is where we introduced the Dev-Weekly, just following our weekly, we quickly introduce the topic that has been prepared this week, and everyone interested can just stay. By today the Dev-Weekly sparks new ideas every week, and topics ranging from CSS frameworks to monorepo tooling to analysing iOS exploits make sure everyone finds something they are interested in. How does a recipe for a successful Dev-Weekly look like? First, find people interested in presenting, this is by far the most challenging part. I do simply ask people if I notice them being interested (or even experts) in certain areas. We track them all in Gitlab, that’s where work happens anyway, so we don’t spread over multiple tools. A gentle reminder to be ready by next week helps everyone to have their topic prepared. Second, make sure to not have a boring Dev-Weekly: focus on that one topic, use the regular weekly as a teaser, and you’ll find half of the company joining and listening. Eventually, make sure to record the presentation (if okay for the presenter), as people will sometimes miss it, and this gives everyone a chance to follow up. Sharing knowledge and experience is what we love, but it took us a long time to establish a format where interested people come together on a regular basis, talking about the newest tech, all cross-team and cross-project. We failed multiple times, COIs/COPs are always centered around a common topic of interest, meetings during lunch were interrupted by delicious barbeque (shout outs to our chefs!), and finding even more timeslots in full-packed weeks led to distraction, less interest and never really took of. But there is one constant in AOE’s work-week, which is “the weekly”, where every Monday the whole company comes together (online, nowadays), to get the most recent updates about business development, teams, and so on. This is where we introduced the Dev-Weekly, just following our weekly, we quickly introduce the topic that has been prepared this week, and everyone interested can just stay. By today the Dev-Weekly sparks new ideas every week, and topics ranging from CSS frameworks to monorepo tooling to analysing iOS exploits make sure everyone finds something they are interested in. How does a recipe for a successful Dev-Weekly look like? First, find people interested in presenting, this is by far the most challenging part. I do simply ask people if I notice them being interested (or even experts) in certain areas. We track them all in Gitlab, that’s where work happens anyway, so we don’t spread over multiple tools. A gentle reminder to be ready by next week helps everyone to have their topic prepared. Second, make sure to not have a boring Dev-Weekly: focus on that one topic, use the regular weekly as a teaser, and you’ll find half of the company joining and listening. Eventually, make sure to record the presentation (if okay for the presenter), as people will sometimes miss it, and this gives everyone a chance to follow up. Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
+ Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
We grow by learning on new impulses, not by locking ourselves into our comfort zone. There are few technologies that change as often as web frontend tools, libraries and technologies in the recent years. With a focus on web development at AOE we have been on the bleeding edge ever since, evaluating and understanding what technologies bring us forward. Sharing knowledge and experience is what we love, but it took us a long time to establish a format where interested people come together on a regular basis, talking about the newest tech, all cross-team and cross-project. Keycloak is our go-to tool when it comes to identity management, federating identities over multiple sources and organizing and managing roles for all kinds of applications.
Naturally, there is no “one-tool-fits-all”, so Keycloak too sometimes needs to be customized beyond what the configuration offers, and we need to implement providers to add additional configuration. Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
+ Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
We grow by learning on new impulses, not by locking ourselves into our comfort zone. There are few technologies that change as often as web frontend tools, libraries and technologies in the recent years. With a focus on web development at AOE we have been on the bleeding edge ever since, evaluating and understanding what technologies bring us forward. Sharing knowledge and experience is what we love, but it took us a long time to establish a format where interested people come together on a regular basis, talking about the newest tech, all cross-team and cross-project. Keycloak is our go-to tool when it comes to identity management, federating identities over multiple sources and organizing and managing roles for all kinds of applications.
Naturally, there is no “one-tool-fits-all”, so Keycloak too sometimes needs to be customized beyond what the configuration offers, and we need to implement providers to add additional configuration. Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
+ Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
We grow by learning on new impulses, not by locking ourselves into our comfort zone. There are few technologies that change as often as web frontend tools, libraries and technologies in the recent years. With a focus on web development at AOE we have been on the bleeding edge ever since, evaluating and understanding what technologies bring us forward. Sharing knowledge and experience is what we love, but it took us a long time to establish a format where interested people come together on a regular basis, talking about the newest tech, all cross-team and cross-project. Keycloak is our go-to tool when it comes to identity management, federating identities over multiple sources and organizing and managing roles for all kinds of applications.
Naturally, there is no “one-tool-fits-all”, so Keycloak too sometimes needs to be customized beyond what the configuration offers, and we need to implement providers to add additional configuration. Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
+ Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
We grow by learning on new impulses, not by locking ourselves into our comfort zone. There are few technologies that change as often as web frontend tools, libraries and technologies in the recent years. With a focus on web development at AOE we have been on the bleeding edge ever since, evaluating and understanding what technologies bring us forward. Sharing knowledge and experience is what we love, but it took us a long time to establish a format where interested people come together on a regular basis, talking about the newest tech, all cross-team and cross-project. Keycloak is our go-to tool when it comes to identity management, federating identities over multiple sources and organizing and managing roles for all kinds of applications.
Naturally, there is no “one-tool-fits-all”, so Keycloak too sometimes needs to be customized beyond what the configuration offers, and we need to implement providers to add additional configuration. Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
+ Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
We grow by learning on new impulses, not by locking ourselves into our comfort zone. There are few technologies that change as often as web frontend tools, libraries and technologies in the recent years. With a focus on web development at AOE we have been on the bleeding edge ever since, evaluating and understanding what technologies bring us forward. Sharing knowledge and experience is what we love, but it took us a long time to establish a format where interested people come together on a regular basis, talking about the newest tech, all cross-team and cross-project. Keycloak is our go-to tool when it comes to identity management, federating identities over multiple sources and organizing and managing roles for all kinds of applications.
Naturally, there is no “one-tool-fits-all”, so Keycloak too sometimes needs to be customized beyond what the configuration offers, and we need to implement providers to add additional configuration. Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
+ Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
We grow by learning on new impulses, not by locking ourselves into our comfort zone. There are few technologies that change as often as web frontend tools, libraries and technologies in the recent years. With a focus on web development at AOE we have been on the bleeding edge ever since, evaluating and understanding what technologies bring us forward. Sharing knowledge and experience is what we love, but it took us a long time to establish a format where interested people come together on a regular basis, talking about the newest tech, all cross-team and cross-project. Keycloak is our go-to tool when it comes to identity management, federating identities over multiple sources and organizing and managing roles for all kinds of applications.
Naturally, there is no “one-tool-fits-all”, so Keycloak too sometimes needs to be customized beyond what the configuration offers, and we need to implement providers to add additional configuration. Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
+ Meals, as the name suggests, is an application to manage meals. It was developed at AOE to manage employee lunch meals. What initially started as a small tool has now grown in to a mature and enterprise ready application, and it’s still growing. It’s been open source ever since, and we love to share it. When I opened the box of my Roomba back in 2016 there was a sticker saying: This robot contains an electronic and software interface that allows you to control or modify, and remotely monitor its sensors. For software programmers interested in giving your iRobot new functionality we encourage you to do so. A little later I first started playing with microcontrollers sending infrared commands to the IR sensor in order to start cleaning via my home network (or specifically by pressing one of the Amazon Dash buttons that came out at that time). While newer generations of the Roomba product line already come with wifi and cameras I always wanted to be able to add that myself. Although it may sound a little over-engineered here’s my current project: Under the top cover of the Roomba there’s a serial interface connector hidden. Using a documented serial interface you can easily send either higher-level commands like start cleaning, stopping, and seeking the dock, or low-level commands like reading individual sensor values, controlling the motors or even playing notes on the internal speaker. At AOE our most valuable asset is our experience with building complex enterprise applications to shape companies digital transformation, so why do we care about Open Source at all?
We grow by learning on new impulses, not by locking ourselves into our comfort zone. There are few technologies that change as often as web frontend tools, libraries and technologies in the recent years. With a focus on web development at AOE we have been on the bleeding edge ever since, evaluating and understanding what technologies bring us forward. Sharing knowledge and experience is what we love, but it took us a long time to establish a format where interested people come together on a regular basis, talking about the newest tech, all cross-team and cross-project. Keycloak is our go-to tool when it comes to identity management, federating identities over multiple sources and organizing and managing roles for all kinds of applications.
Naturally, there is no “one-tool-fits-all”, so Keycloak too sometimes needs to be customized beyond what the configuration offers, and we need to implement providers to add additional configuration.
diff --git a/renovate/tailwindcss-3.x/posts/index.html b/renovate/tailwindcss-3.x/posts/index.html
index 7c434b3..f0f58bf 100644
--- a/renovate/tailwindcss-3.x/posts/index.html
+++ b/renovate/tailwindcss-3.x/posts/index.html
@@ -1,5 +1,5 @@
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Tailwind pushing us forward
The weekly Dev-Weekly
The Key to Keycloak
Running (faster) with Gitlab CI
The Key to Keycloak
The Key to Keycloak
package mapper;
diff --git a/renovate/tailwindcss-3.x/posts/loving-open-source/index.html b/renovate/tailwindcss-3.x/posts/loving-open-source/index.html
index 9633e15..5c108e7 100644
--- a/renovate/tailwindcss-3.x/posts/loving-open-source/index.html
+++ b/renovate/tailwindcss-3.x/posts/loving-open-source/index.html
@@ -1,5 +1,5 @@
Loving Open Source
Loving Open Source
Raising Flamingo(s)
Raising Flamingo(s)
Running (faster) with Gitlab CI
Running (faster) with Gitlab CI
🍽 Savory Meals
So, what can it do?
Installation
Hosted Environment
Prerequisites:
Configuration:
Setup:
composer install
+🍽 Savory Meals
So, what can it do?
Installation
Hosted Environment
Prerequisites:
Configuration:
Setup:
composer install
bin/console doctrine:migrations:migrate -n
cd src\Resources && yarn build
Cloud
Sounds delicious, but I like extra topping.
docker and ddev, so these must be pre-installed. After this, just one commandmake run-devbox
diff --git a/renovate/tailwindcss-3.x/posts/should-you-upgrade-to-web3/index.html b/renovate/tailwindcss-3.x/posts/should-you-upgrade-to-web3/index.html
index 406b24c..664fcc0 100644
--- a/renovate/tailwindcss-3.x/posts/should-you-upgrade-to-web3/index.html
+++ b/renovate/tailwindcss-3.x/posts/should-you-upgrade-to-web3/index.html
@@ -1,5 +1,5 @@
Web3: A new major version. Should you upgrade?
Being state of the art
Should we upgrade?
$ update web@v3
Conclusion
Web3: A new major version. Should you upgrade?
Being state of the art
Should we upgrade?
$ update web@v3
Conclusion
Tailwind pushing us forward
class="p-8". Want to decrease that? Change to class="p-4". Easy, right?Tailwind pushing us forward
class="p-8". Want to decrease that? Change to class="p-4". Easy, right?The weekly Dev-Weekly
The weekly Dev-Weekly
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Tailwind pushing us forward
The weekly Dev-Weekly
The Key to Keycloak
Running (faster) with Gitlab CI
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Tailwind pushing us forward
The weekly Dev-Weekly
The Key to Keycloak
Running (faster) with Gitlab CI
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Tailwind pushing us forward
The weekly Dev-Weekly
The Key to Keycloak
Running (faster) with Gitlab CI
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Tailwind pushing us forward
The weekly Dev-Weekly
The Key to Keycloak
Running (faster) with Gitlab CI
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Tailwind pushing us forward
The weekly Dev-Weekly
The Key to Keycloak
Running (faster) with Gitlab CI
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Tailwind pushing us forward
The weekly Dev-Weekly
The Key to Keycloak
Running (faster) with Gitlab CI
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Read the AOE Articles
🍽 Savory Meals
Hacking Roombas
Web3: A new major version. Should you upgrade?
Loving Open Source
Tailwind pushing us forward
The weekly Dev-Weekly
The Key to Keycloak
Running (faster) with Gitlab CI
Read the AOE Articles