mjgoeke

With all the talk about "does the software support fractional bpm" wouldn't you just create it at say 124bpm and then scale down to 123.45 (or whatever) by taking the total length and scaling it by that percentage (e.g. 0.99561926612903225806451612903226). You don't even need to scale it trying to keep the pitch correct. You just speed it up < half a percent, the pitch rises slightly, and you have your perfect bpm.

That's not a "watermark", keep it to 5% opacity. This is around 13% and very distracting.

Mobile? afaik node.js doesn't run on mobile. If that's the case the 'copy' doesn't do a good job of highlighting the big value prop.

Location: Oregon

Remote: yes

Willing to relocate: no

Technologies:

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.

My first thought is, are they differentiating between people who buy vinyls for themselves vs someone who has a record player?

Seems like they may be jumping to conclusions here.

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.

This.

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.

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