James C. Davis (he/him)

( husband | father | engineer | scientist | artist ) Staff Software Engineer @Salsify, EmberJS + TypeScript, Node.js, Ruby on Rails.

[James C. Davis (he/him) @jamscdavis]

@chriskrycho @boulderthon Congratulations! That's awesome!!

[James C. Davis (he/him) @jamscdavis]

@bartocc @wycats FYI: The next major version of ember-css-modules (coming soon) will be a transform that behind the scenes turns local-class="foo" into what is described in this post.

[James C. Davis (he/him) @jamscdavis]

@chriskrycho Served as acting unit leader for my youngest kiddo's pack at cub scout camp! (writing this from my cot on the last night) Felt good! And I'll be back out here next week as an Assistant Scoutmaster with my daughter's Scouts BSA troop!

[James C. Davis (he/him) @jamscdavis]

@chriskrycho @jmduke If I were to start a software company, this is what I would want it to become.

[James C. Davis (he/him) @jamscdavis]

@chriskrycho Interesting take from Robert Greiner's article:

The two simple rules of ratcheting:
1. Your commit must not make the existing code base worse on aggregate
2. Your commit must improve the code base in one or more areas

[James C. Davis (he/him) @jamscdavis]

@chriskrycho Oldest usage I've found so far: https://t.co/bOXT7cHZ8G

[James C. Davis (he/him) @jamscdavis]

@chriskrycho I enjoyed this article that expands further on the ratchets concept, breaking them down into three categories:
- Fully automated tooling ratchets
- Semi-automated tooling ratchets
- Process-based ratchets
https://t.co/nFf48sTa3W

[James C. Davis (he/him) @jamscdavis]

@nullvoxpopuli Though wondering what /(m|c|g)(j|t)sx/ might be.

[James C. Davis (he/him) @jamscdavis]

@nullvoxpopuli That about covers it.

[James C. Davis (he/him) @jamscdavis]

@chriskrycho @typescript Also, excited to try out your programming language. Whatcha gonna call it? How about "Krust"? 😝

[James C. Davis (he/him) @jamscdavis]

@chriskrycho @typescript At @Salsify, we have a lint rule disallowing the shorthand. I am very happy that we made that decision early on in @typescript adoption.

[Chris Krycho @chriskrycho]

As of this PR, @emberjs can publish its @typescript types from its own TS source code: no more hand-maintained types! It took a *lot* of work and a lot of inventing new techniques, which made it fun, sometimes frustrating, and always interesting! https://t.co/cw0GpbAgOr

[James C. Davis (he/him) @jamscdavis]

@acemarke @chriskrycho @kentcdodds Or just use @babel/plugin-transform-typescript-prose

[James C. Davis (he/him) @jamscdavis]

@acemarke @chriskrycho @kentcdodds ChatGPT prompt: rewrite this without any reference to types.

[Chris Krycho @chriskrycho]

In which Chiang manages to not only make a great argument but provide exactly the right lay-level intuitions for how “diffusion”-type models actually work. Worth your time! https://t.co/CMO3QfbF5q

[Cory House @housecor]

A surprising irony about working in TypeScript:

The better I get at it, the fewer types I declare.

I declare types at the “edges” of my app:
✅Endpoint responses
✅Environment vars
✅Browser storage
✅Querystrings

These types “flow” throughout the app.

#typescript

[James C. Davis (he/him) @jamscdavis]

@housecor This is a good point! And with things like autogenerated GraphQL types, I find myself needing to declare almost _no_ types in the FE!