HackerTrans
TopNewTrendsCommentsPastAskShowJobs

msaspence

no profile record

Submissions

Leadership: Navigating Conflict

medium.com
1 points·by msaspence·w zeszłym roku·1 comments

Leadership: Force Multiplication

medium.com
3 points·by msaspence·4 lata temu·1 comments

You Don't Need Microservices

medium.com
113 points·by msaspence·4 lata temu·165 comments

comments

msaspence
·6 miesięcy temu·discuss


    Location: San Diego, CA
    Remote: Yes
    Willing to relocate: Possible within CA
    Résumé: https://msaspence.com
    Email: [email protected]
    Technologies: Node.js, Typescript, JavaScript, react, Python, Rails, Ruby, Postgres
Are you a small growing team looking for a hands-on leader who can comfortably operate tactically and strategically simultaneously?

I love to straddle IC and management roles. If you need someone who can lead your product software team and still churn out feature after feature with clean, maintainable code I'm your man.
msaspence
·w zeszłym roku·discuss
What makes you think that AI is going to produce leaner codebases? They are trained on human codebases. They are going to end up emulating that human code. It's not hard to imagine some improvement here, but my gut is there just isn't enough good code out there to train a significant shift on this.
msaspence
·4 lata temu·discuss
Or more simply, the one key question all leaders should judge themselves by.
msaspence
·4 lata temu·discuss
> "move stuff around and complexity will magically go away" fallacy

This is a great description of microservices
msaspence
·4 lata temu·discuss
I love the idea of "managing junior level programmers who don't know how to make loosely coupling architecture" as describing engineering leadership, regardless of how cynical it is.

I do question how microservices manage that, though? Tightly coupled microservices ie "the distributed monolith", are a still real danger for teams that don't have enough engineers that know "know how to make loosely coupling architecture"
msaspence
·4 lata temu·discuss
Why the monolith should remain the default choice for new, small, and medium-sized engineering teams. Considering how we can leverage the monolith to realize the benefits that microservices claim for themselves.