Martin Stadler

Love building digital products and fun teams. Head of Engineering @ ex Engineering Lead @BCGDV. Also @OpenTechSchool/@OTS_BLN.

[Martin Stadler @xMartin]

🎉 Looking for my first engineering hire at VREY!

Full-Stack Software Engineer (Junior/Mid-Level)

+ Web application dev using RubyOnRails
+ Strong skills with relational dbs and data import/processing
+ Experience with cloud infra

Please share 💚

https://t.co/gwCO7XQp8e

[Martin Stadler @xMartin]

🎯

[Marko Kovic @marko_kovic]

13/ Es gibt keine "guten" Plattformen. Es gibt keine "schlechten" Plattformen. Tech-Unternehmen sind amoralisch. In den Worten Milton Friedmans: The Business of Business is Business. Moralisierung in egal welche Richtung ist PR, die je nach politischer Windlage anders ausfällt.

[Martin Stadler @xMartin]

Is web development going Back to the Future?

Here's my take on latest #NextJS/#React Server Components (#RSC) developments. Are we finally closing the loop from progressive enhancement to SPAs and back?

https://t.co/FnV2aWqc0B

What's your take?

[John Carmack @ID_AA_Carmack]

“Coding” was never the source of value, and people shouldn’t get overly attached to it. Problem solving is the core skill. The discipline and precision demanded by traditional programming will remain valuable transferable attributes, but they won’t be a barrier to entry.

Many times over the years I have thought about a great programmer I knew that loved assembly language to the point of not wanting to move to C. I have to fight some similar feelings of my own around using existing massive codebases and inefficient languages, but I push through.

I had somewhat resigned myself to the fact that I might be missing out on the “final abstraction”, where you realize that managing people is more powerful than any personal tool. I just don’t like it, and I can live with the limitations that puts on me.

I suspect that I will enjoy managing AIs more, even if they wind up being better programmers than I am.

[Dominik 🔮 @TkDodo]

PSA: Whenever you think of writing useEffect, the only sane thing is to NOT do it. Instead, go to the react docs and re-read the page about why you don't need an effect. You really don't.

But what if I ne.. - NO. read the page!
In my specia.. - NO. read the page!

READ THE PAGE

[Martin Stadler @xMartin]

Thank you so much for bringing this up, explaining, raising fair questions, sharing your perspective! The letter is very well phrased and I hope it will have an impact.

[Aisha Belamo @AishaXBello]

The python Africa community has sent an open letter to @ThePSF . We raise concerns over issues that have negatively affected our communities and many of us feel hurt. Please take a moment to understand where we are coming from: https://t.co/x0IY8X1jxp

[isaacs @izs]

But they're entirely fucking arbitrary, and out here in the real world of thoughtful and dedicated practitioners, we all know that what matters is trade-offs, priorities, and delivering a positive return on investment in pursuit of whatever unique goal we have.

[Martin Stadler @xMartin]

Interesting take and quite spot on for inexperienced or ignorant developers. If you're having a solid engineering approach, best practices can streamline your work. Doesn't work the other way round.

Reminds me of an agile mindset and Scrum as a set of rules.

[isaacs @izs]

It implicitly teaches newcomers to a craft that power in a craft comes from being the authority, and authority comes from knowing the rules better than anyone, and you can trust the rules because they came from an authority (who by definition knows the rules better than anyone).

[Martin Stadler @xMartin]

@Bumi The difference is that client-side rendering for interactivity is seamlessly integrated in terms of coding and performance optimizations and it's mostly common to connect to APIs instead of a database directly.

[Martin Stadler @xMartin]

Agree. Rendering HTML and other UI -specific concerns are frontend, both on server and client, including backend for frontend services.
Never heard otherwise but maybe because of client-only SPAs people get confused.

[Malte Ubl @cramforce]

I'm all for specialization in software engineering, but client/server isn't a good boundary. As a frontend engineer you need to control the entire user experience, and that requires being empowered to program the frontend server.

[Martin Stadler @xMartin]

@Bumi In the sense of frontend frameworks moving towards server-rendered first while not being opinionated on the model layer. Simple vanilla PHP applications would cover the same area in the past.

[Martin Stadler @xMartin]

I started doing paid mentorship and it's a lot of fun!
Feels good to use my 10+ years in software engineering (#frontend #react #fullstack) and leadership to help others to start or improve their career. 💫
If you're interested, get in touch! 🤝
https://t.co/lPHE3f2a2r

[Martin Stadler @xMartin]

Been there and yes, learning this can spare you much anger and frustration and help you staying productive. Still practicing...

[Cory House @housecor]

Related quote that helps me justify giving up when I can tell I’m not going to change their mind:

“Nothing in life is as important as you think it is, while you are thinking about it.”

[Martin Stadler @xMartin]

This. 💯

[Cory House @housecor]

A common mistake: "Let's abstract this in case we want to replace it later."

Examples:

🚫 "Let's abstract React in case we switch JS frameworks."

🚫 "Let's abstract Tailwind in case we switch CSS approaches."

🚫 "Let's abstract Mongo in case we switch Databases".

This is typically a waste of time, and often hinders current use too.

Why? Because to effectively abstract something, we need to know the API we're abstracting.

But we have no idea what a new technology's API will be. Thus, we have no idea whether our abstraction will work with the new technology.

In summary, abstraction can be useful. But avoid abstracting merely to support changing to some unknown future technology.

[SwiftOnSecurity @SwiftOnSecurity]

Working in InfoSec watching the rest of IT

[Mark Dalgleish @markdalgleish]

Adding GitHub comments to individual lines in your own PR is pro level.

And no, I don’t think they should be comments in the code. The point of PR comments is to talk about the *change*, not the code itself. This only makes sense with both old and new code visible side-by-side.

[Wizard Amig@s @wizardamigos]

We are lokking for vanilla js, node js and dat/hypercore related gigs for our learners.

If anyone has any leads, please let us know.

Learners have mentorship and help and they basically earn while they learn 🥰

[Martin Stadler @xMartin]

Zukunftsangst trifft es sehr gut. Angst davor dass sowas nochmal passiert, öfter passiert, normal wird.

Mir geht's in solchen Situationen genauso, friere auch erstmal ein. Vielleicht hätte ich den Impuls gehabt die alle an der nächsten Ecke rauszuschmeißen, hoffentlich.

[Diva auf‘m Divan @Snake_Kaa]

> Es ist Zukunftsangt.

Dieser Hass, diese blinde Wut. Und vor allem die vollkommene Hemmungslosigkeit, diese so lautstark und unverhohlen zu demonstrieren. Ohne Scham. Ohne Konsequenzen zu fürchten.

Das lässt mich mich in die Knochen erschaudern. >

[Jana Hensel @jana_hensel]

In Wahrheit agiert die FDP ja immer nach demselben Muster: sie macht aus einer Mücke einen Elefanten. Sie bläst ein Detail zu einer vermeintlich zentralen Frage auf. Wochenlang hat sie für die Verlängerung der Atomkraftwerke gekämpft, als ginge es um die Zukunft Deutschlands —