I know it isn't the point you are trying to make, but I can't think of a better way to re-enforce OP's point of "mediocrity will be even more available" than a mid-00s style, pop country song about eating hamburgers. "Toby Keith but with less to say" might be the gold standard of mediocrity.
Typescript/Javascript, C#, HTML/CSS, Vue, SQL, noSQL, Bootstrap, Azure Devops/Github Actions, Kubernetes, Docker, Node.js, functional programming, CQRS, unit and automated testing
Résumé/CV: upon request via email
Email: michael[dot]goeke[plus]yc[at]gmail[dot]com
Laser focused Principal Software Engineer adept at delivering best in class solutions on time, on budget, while building a kick ass team in stride. Fearless and empathetic communication - break down walls, find and create alignment, empower those around me. Technical genius. Polymath and autodidact. Clear and concise communicator.
I've appreciated a lot of parts of this book and was wondering if I could share it with others in some way.
I like to see the actual content of a book before I buy it to know if it resonates with me.
I found the book's table of content with links to the content is available, so I linked that here. Hopefully you get something out of it, and buy either the digital or paper copy if it speaks to you.
I have a very different set of problems/concerns in my current project and when I walk through the website most of it isn't mapping into my current problem+solution space.
The problem this is solving may be obvious from your perspective, but it isn't from mine, and maybe others.
I don't know I need your solution unless I see I have a problem.
Perhaps there are a few simple, general problem cases this solves.
If so you could characterize those in context+problem+solution brief narratives.
That could help others get on the same page as your solution.
And this is true for reasons I didn't understand when I was soley technical and younger.
At the end of the day people - _teams_ - want people they can trust in. That doesn't mean you handle things flawlessly, or that your boss can necessarily "set it and forget it" with you.
Being trustworthy and responsible means acting out of good intent. Take a breath, keep your head on straight, look at the slightly bigger picture, and make reasonable choices. Communicate.
Act as if the world isn't on your shoulders - because it isn't.
Take a step back, realize that we're all people, trying to make good decisions, and we're responsible to work with the outcomes and address problems as they arise.
I've found I grow by leaps and bounds when I embrace this.
>> Being trustworthy and responsible means acting out of good intent.
This is a great comment. It reveals the truth about how we grow into roles of higher and higher responsibility. I believe I was on the lucky side, though, that most of my bosses understood this about me. Part of it actually is the fact that they know you will take the world on your shoulders in their absence if the situation demands it. It's a test. If it goes off the rails, they're basically saying they can afford it and they don't care, but they want to know who stayed up all night trying to fix it. It sounds paradoxical and maybe jaded, but it's actually better for OP if the upgrade breaks shit all over the place and he's sleeping under a table 36 hours later responsible for managing the failure state. If everything goes off without a hitch, the boss won't even notice. That said, hope for the best, plan for the worst and go in with the best of intentions - but just like if you're an honorable person, you'd never take credit for something you didn't do, you should never take blame for something you warned people about.
People who see ahead and are capable to intervene and mitigate other people's disasters are literally priceless, and OP will go far just by having the attitude of foreseeing and managing crises created by other people's lack of engagement or imagination. This is also the origin story of every superhero and mob boss.
I'm actively developing this, here's my list of next things:
* make the tool author new page-object-model files
* workflow to append to page-object-model files
* support nested page-object-models better (scope selector)
* make playwright selectors work both ways (only work one-way right now, generating, not executing)
* page-object-model patterns flexibility - embellish recorder rules with method parameters
* add an animated gif to the top of the readme showing usage
* clean up ui
* margins/alignment
* add toggle to show/hide
Yes exactly!
Our behemoth of a web app was taking 25s initial load time (much faster when cached so it just wasn’t a priority to fix performance). Average test run time for a workflow test is 2 minutes.
That means when authoring them and I’m trying to get selectors and crap right it takes me 5 tries for the next line of the test, waiting for 60-90s between each try.
The result is it takes 3-4 hours to author a single medium complexity test. And my brain is mush for the rest of the day.
I hated that and would subconsciously avoid writing tests.
What I’ve developed allows me immediate feedback every step of the way. It makes it _fun_ again so I can keep my head in the game and finish a test in 15-20 minutes and feel accomplished instead of burnt out.
I’ve also taken an approach where the tooling (especially the recorder, and soon the page object model support) brings you 80-90% off the way there, but _always_ plays well with user created code - it has some loose basic expectations of the interface, but it doesn’t need to own the generated code - that’s just a starting point for you to improve it.
Super excited. My company already has a precedent for open sourcing projects so I’m hoping this won’t take more than a week or two to get it there.
I’m on vacation for a week but plan to finish the page object model story when I get back.
https://youtu.be/easvMCCBFkQ?t=114