Florian Benz

Software Crafter, VP of Engineering @ScalableCapital he/him
@[email protected]

[Florian Benz @flbenz]

#BuildToGive

[Thomas Much @thmuch]

Was ist "State of the Art" bei der agilen bzw. kontinuierlichen #Softwareentwicklung im Jahre 2024?

Heute Vormittag habe ich dazu beim @inside_agile-Konferenztag einen Vortrag gehalten – danke fürs Zuhören 😊

Die Folien gibt’s hier: https://t.co/ZGa3xhQokk

[Oliver Drotbohm 🥁 & 👨‍💻 @odrotbohm]

From the fine folks at @INNOQ – https://t.co/JMyLfqMhEg

[Florian Benz @flbenz]

Pull Request numbers that made me smile. Pure coincidence but a very nice one. Both the number and actually getting rid of code feels good.

[deararchitects @deararchitects]

Issue 154: https://t.co/AlylUshRKt

This week:
1. How to bridge silos inside your organization
2. #devops best practices
3. How @stripe is designed for #BlackFriday traffic
4. New #serverless book from @sheenbrisals and @level_out
5. @OReillyMedia #architectures #books #bundle

[Florian Benz @flbenz]

One of our machine learning success stories at Scalable made it to the AWS Machine Learning blog: Classifying emails.
I'm proud of our Data Science team and it was a great internal collaboration.
https://t.co/QypTlIJftB

[Go @golang]

🧐 “Fixing For Loops in Go 1.22” by @_rsc and @dr2chase #golang
https://t.co/Gqa5NWcDWt

[Werner Vogels @Werner]

Building and operating a pretty big storage system called S3 – A unique perspective by #AWS Distinguished Engineer @andywarfield on what it means to scale systems, yourself and others. #allthingsdistributed #S3 https://t.co/C3CE2iOJ0o

[Abhay Bhargav @abhaybhargav]

Great security feedback loops you can create w/ @github actions (screenshots below)
1. commit to "feature" branch runs @semgrep SAST
2. commit/merge to main branch runs SAST and gen SBOM w/ @CycloneDX_Spec, pushes to @DependencyTrack
3. Run everything on tag push (pre-deploy)

[Florian Benz @flbenz]

I talked about Domain-Driven Design at Scalable Capital in a podcast (German).

[Working Draft @workingdraft]

Revision 556: Domain-Driven Design mit @flbenz

https://t.co/zfHIFz83kT

Dieses Mal wird die Folge von @demodern gesponsort! Vielen Dank für die Unterstützung dieser Revision.

[Simon Vergauwen @vergauwen_simon]

I had a great time talking at @fosdemkotlin! Thanks for the great questions, and organisation 🥰

My slide deck is available here, https://t.co/hcjlTabbJ9 and the recording will soon be available.

#kotlin #functionalprogramming

[Martin Fowler @martinfowler]

A convincing argument from @ghohpe

One of those situations where I don't think I've ever said it, but as soon as I read it, I reacted with: "obviously true".

[Daniel Bryant @danielbryantuk]

People often ask how I keep on top of news, tech, and trends 🤔 Here's one of my secrets: subscribing to (and reading!) essential newsletters 📰

Here are my top tech newsletters for 2022!

(and bear in mind my interests are quite ecletic, from tech to devrel to business)

🧵 👇

[Martin Fowler @martinfowler]

I've noticed a number of people asking about how to find people to follow on Mastodon, so here's what I do.

https://t.co/TFwWoPiKVj

[Martin Fowler @martinfowler]

Twitter is becoming increasingly hostile to writers. I'm still currently posting here, but strongly recommend that readers follow me on Mastodon or my site's RSS feed if you want to know when I post something new. Do the same for other authors you find useful.

[Andy Wilkinson @ankinson]

The next generation of Spring Boot is here! Massive thank you to everyone who's helped with this release.

https://t.co/uQRKw7FhpO

[Maciej Walkowiak 🍃 @maciejwalkowiak]

There are so much happening now in 🍃 @springboot ecosystem that it's easy to get lost.

Subjectively, the most interesting Spring projects releases in November 2022:

[Florian Benz @flbenz]

I'm also on Mastodon now.
https://t.co/jBQoft3M1G

[Stefan Tilkov @stilkov]

This is a fantastic resource: https://t.co/vMVV4KV0FY

[Florian Benz @flbenz]

3. Read documentation. I jumped right into coding way too often and could have benefited greatly by reading the documentation first.

[Florian Benz @flbenz]

I was asked today for tips on how to become a better software engineer. Here are the first three things which came to my mind:

[Florian Benz @flbenz]

2. Don’t be scared to understand something in depth if it’s crucial for your work. Going into the code and following the development of a library or even a framework can not only improve your interaction with the library/framework but shows how others code and work.