Christopher Hlubek

Well, let's see how that #Mastodon thing works out. Find me at @christopher" target="_blank" rel="nofollow noopener">networkteam.social/@christopher (@christopher@networkteam.social) on our own brand new instance.

@dan_abramov Simple is better. Multi-column layout is much harder to scan - one could easily overlook „useReducer“. But the examples would be nice to add. For me too much design is rather distracting for docs.

A few weeks later and we are doing the last finishing touches for a first customer project using this setup. Take a peek at the NPM and Composer packages, they are all public now: github.com/networkteam/ze… . Next step: a demo project to start with a working setup and more docs.

@watch_union @elonmusk 🖕

Der neue #Twitter-Eigentümer @ElonMusk behauptet, ein Großteil unserer Follower sind Bots. Lasst ihn uns eines besseren belehren. Wenn du kein Bot bist, antworte auf diesen Tweet mit 🖕. /PM

@zoink @figma @Adobe 😭

THREAD: This morning we’re announcing that @Figma has entered into an agreement to be acquired by @Adobe ! More information here: figma.com/blog/a-new-col… (1/9)

@Markus306 @brgmn @nextjs @neoscms @networkteam @nuxtjs @sbruggm4nn 😀 We basically skip Fusion completely and generate the frontend preview via Next.js preview route in React with all editing metadata of a „normal“ frontend rendering emulated. Neos UI seems to be happy so far. We‘ll open-source it when we figured out how to package it for reuse.

Upcoming: @nextjs with @neoscms in headless mode and full editing experience in Neos UI - driven by frontend rendering in Next.js and content API in Neos. We had a really productive internal barcamp @networkteam for 2 days trying out this crazy idea - results look promising! 🤩

After Lens (a really nice #Kubernetes GUI) now finally enforces having a Lens account it was time to look for an alternative. I can highly recommend K9s: k9scli.io, a CLI based tool to inspect and work with a cluster. I think for me it might be even more effective.

Develop it, Test it, Ship it, Measure it - Building an end-to-end CI
 solution for #NeosCMS projects speakerdeck.com/hlubek/develop… #NeosCon

Super stoked to be on stage again in a great community. at #NeosCon. Here's the repo for our CI end-to-end setup with #NeosCMS & #Kubernetes (slides are coming soon) github.com/networkteam/ne…

@dimaip --autostash ?

why can't git just do `git stash && git pull && git stash apply` automatically?

I'm grateful we tried. Man, oh, man, did we try.

“Rethinking Visual Programming with Go” divan.dev/posts/visual_p…

Wir müssen handeln. JETZT! Mit dieser Forderung sind wir nicht allein. Immer mehr unterstützen unseren Aufruf an die Bundesregierung nach einem sofortigen Importstopp für russisches Öl & Gas. Vielen Dank! #Ukraine #Embargo

I really enjoy using unit tests when developing #Helm charts (using github.com/quintush/helm-…). Writing templates for YAML is hard. This makes it somewhat more enjoyable and enables a fast feedback loop -which is always important. Also: refactoring and safeguard from regressions.

Wie verwenden wir #Golang bei networkteam? Und für welche Projekte eignet es sich am Besten? Neu bei uns im Journal: networkteam.com/journal/2022/g…

@jensneuse_de Ha! I‘m guilty of doing all of this… (Doing K8s bare-metal is a bit painful though.) But the amount of knowledge you gain is tremendous. Think twice before you want to support a full production setup, though.

It's like running and operating your own kubernetes clusters or databases. Unless you're a could vendor, you should almost never touch these layers but depend on someone trustful with the right amount of experience.

You can argue that an #api needs to be designed, and you're right. But what if developers are inexperienced and finding experienced Devs is expensive and time consuming. A database-driven generated #GraphQL API, like we offer with @wundergraphcom, can fill a gap.

4. Architectural design is mostly about trade-offs and choosing what you're optimizing for. So if you need to support something for a longer time it's just a very different perspective from optimizing for a short time to market.

3. After all I tend towards more explicit software that is easier to read, is not optimized for the least amount of code and reduces friction as far as possible (e.g. due to framework, tooling, language and dependency updates). But I'm also not optimizing for just being fast 🤷

For software architectures I see much benefit in striving for a constant/gradual amount of complexity. What does that mean?