Suggestions
Falko Burghausen
Ex-CTO striving for a more active life beyond meeting rooms and desks. Outdoor and Sports Photographer when the sun sets. Trail Running Guide for alpine running tours. Software Engineer when things get tricky.
Falko Burghausen is a seasoned professional with over 10 years of experience in software engineering and leadership across various technologies.
He is a staunch advocate of lean and agile principles, possesses a deep understanding of DevOps practices, cloud-first strategies, and infrastructure as code.
His expertise spans Java, Python, JavaScript, PHP, C++, databases, Terraform, Camunda and BPM, and *nix systems.
Falko is committed to writing clean code, implementing extreme programming, practicing test-driven development, and setting up continuous integration and continuous delivery pipelines.
Outside of the tech realm, he is a skilled professional photographer specializing in nature photography and outdoor/sports storytelling.
Driven by a blend of passion, fairness, and pragmatism, Falko enjoys mountaineering, skiing, cycling, kayaking, trail running, and creating electronic music.
He holds a Bachelor of Applied Science (BASc) degree in Informatik / Software Engineering from HTWG Hochschule Konstanz – Technik, Wirtschaft und Gestaltung.
Falko has held leadership positions including CTO at OnlineDoctor, Co-Founder & Professional Photographer at alpün media, Engineering Lead and Team Lead at CREALOGIX Group, Engineering Manager and Tech Lead at siroop, Business Analyst at siroop, Senior Developer & Technical Lead at Interactive Data, Software Engineer at coliquio, and various web development roles early in his career.
Highlights
It never ceases to amaze me how rigorously so-called and self-appointed thought leaders press certain technological concepts or statements into a black-and-white mindset and create a huge drama out of banal reports, while regularly ignoring relevant background information from the original source.
Latest topic on LinkedIn: "Not even Amazon sees sense in microservice architectures". This statement is, if I may say so, simply bullshit and was not made by Amazon (the original blog post from Amazon on this topic can be found with a link at the end of this post). Actually, the point was simply that "[...] we realized that distributed approach wasn't bringing a lot of benefits in our specific use case, so we packed all of the components into a single process. [...]" The blog post also explains quite clearly and transparently the background for this decision and it sounds plausible from what one can tell as a completely uninvolved person. I also honestly doubt that all those who are now loudly ranting against microservices have ever worked in this team at Amazon in their lives and thus really had a profound insight into the topic.
So are microservices good or bad? The unprofessional answer would be one of the two. The professional answer is the unpopular one: it depends. On the individual use case, the knowledge of the team, existing technologies, and much more.
The moral of the story: as a Software Engineer or Tech Lead, do your own thinking about such decisions as software systems architecture and consistently question supposedly simple statements. You know the individual use case best, and even if you didn't catch the most ideal setup from the start, you did the most important thing of all, which is to move the actual business forward for the users of the software. Because let's not forget one thing: 99.9% of the users don't give a shit whether the software has been developed on the basis of microservices or as a monolith, they don't even know these terms.
In this sense: happy coding! 🚀🙂
Original blog post: https://lnkd.in/eDU_eUtM
#tech #architecture #coding
Improving your personal communication skills as a Software Engineer can have a big impact on your future career. Read more about what this has to do with icebergs. 🧊 https://lnkd.in/etbnHmgJ
#career #softwareengineer #communication
