@scathach@thgs in my last days of c++ i had started replacing the self-insert keys to completely eliminate holding shift (because it was a source of RSI.) so things like typing ;; would become :: and - would become an underscore if next to an identifier character kind of stuff
@bobmagicii I gave up on psr18 and whatnot for the http clients I am using. I did some small interfaces for what I needed exactly.
I see what you mean though. If X is based on Y, then X is bounded in some ways to Y. But that is only true when Y is opinionated. The closer it gets to being as objective as possible then it becomes less of a boundary. It’s pretty hard to make something as objective as possible though
@thgs Our of which diagrams? The diagram would need to be in a parsable format, like Mermaid or something like that. If you have that, it could certainly be done though I don't know of a tool that does so.
@Crell Yes, I'm wondering if there is a tool already. I've tried with phpstorm in the past for the reverse operation of generating a diagram from code but it was not that nice.
@Girgias thanks so much for uploading the talk. I wanted to join but had to follow with the others that I was with.
Went through the video and the slides and as kept having an issue with my properties being not initialized, took a couple of hours to figure out the arginfo was not correct as I was missing the constructor definition from the stub. Had a laugh when I figured it out.
Thanks so much for the talk though, that was great!
@thgs depends on the package/repo. I think we have a bunch at 1, a couple are 2-3, there’s an 8 (or maybe 7 now?) and one where I don’t think we bother because even at the highest you can go there’s just too much output to be useful.
@Dave_von_S still reading the first one myself (oop software engineering), the essence model (i saw it you mentioned somewhere in another post) is probably coming next.
I recently came across the #RICE prioritization model that product managers can use to set goals and prioritize whats important.
I felt that this could be interesting to map over on how the #softwareengineering teams set goals and prioritize what is important as we build software, but within that context.
1/*
@thgs
Two concepts I pay attention to are 1) What is the "low hanging fruit", so we can see results early? 2) What is actually making life harder than it should be, so we don't have GIGO?
Start with visiting these questions regularly and recording progress, but: #1 can fail because of poor decision making, analysis-paralysis and unwillingness to experiment; #2 can fail because of lack of self-monitoring, self-analysis and thinking independently of what the management is feeding you.
@thgs if your worry is about doing it at scale, you're thinking about platform engineering: you need to invest in internal tooling for your team, and improve the developer experience.
@thgs nah, I don't think so. There are a few things Go did differently, therefore deviating from C. E.g. stacks grow and consequently are copied to a new area in memory. That makes some things work fundamentally different.