Dave Sibiski

CTO & Co-Founder of AutoElevate ( Member of @reactnative core team.

[Dave Sibiski @dsibiski]

@peterpme @draftbit Yeah man, I'd love to hear what kinds of ideas you've come up with...especially implementing with ReasonML! I'd love to show you where I'm at as well with all that stuff.

[Dave Sibiski @dsibiski]

@peterpme hey man, @draftbit looks amazing! Congrats! It looks like you're having a great time building the product and the company, super happy for you bro. 😀

[Dave Sibiski @dsibiski]

@gabegreenberg @reactnative @Eli_White @reactiflux I need to make some time and do a call with you guys or something and catch up. I've been basically disconnected from everything for a while now...need to hop in and see whats up. 😀

[Dave Sibiski @dsibiski]

@gabegreenberg @reactnative @Eli_White @reactiflux So far so good! Super challenging, but definitely rewarding. The product has evolved and turned in so many ways that we hadn't anticipated, but it's just gotten better. Just getting it out there in front of people and iterating on their needs has been working so far.

[Eric Vicenti @EricVicenti]

I'm launching a new project tomorrow. Excited to show everybody where my head has been for the past year!

[Dave Sibiski @dsibiski]

@gabegreenberg @reactnative @Eli_White @reactiflux Thanks Gabe! Those were definitely some good times 😀

[Changelog @changelog]

Dependency Injection

[Kevlin Henney @KevlinHenney]

"The connections between modules are the assumptions which the modules make about each other." — David Parnas

Easy to fall into trap of thinking dependencies must be explicit in code, e.g., import/#include/etc or via type system, but many not so obvious, and no less problematic.

[Kevlin Henney @KevlinHenney]

Once more, with feeling:
• POJO does not mean DTO.
• POJO does not mean that a class has to be as dumb as rocks, with nothing more than getters and setters.
• POJO means that a class is not tied to a particular framework, whether by inheritance or annotation.

[eileencodes @eileencodes]

@searls I just learned about `--autostash`. `git pull --rebase --autostash` will stash the commits, do the pull rebase dance, and reapply your stash!

[Stephen Olmstead @0lmstead]

One of my design beliefs: An idea should live in its lowest fidelity form until it has meaningful reason to do otherwise.

The more we invest in the fidelity of something the harder it is to abandon... even if its the wrong solution. Embrace lo-fi; dont let ideas become precious.

[Devin Abbott @dvnabbott]

To answer a few questions I've been getting about consulting, I'll do:

✅ React/RN
✅ Design systems
✅ Design tools
✅ GUI app builders

I'm consulting 2 days a week, so I'm not available for full time work at the moment. SF or remote. Just mention or DM me!

[I Am Devloper @iamdevloper]

Boilerplates:

For when you don't want to learn the underlying technology, immediately bloat your codebase with 80% unused code and find it impossible to customise literally anything 3 months down the line.

[Faith Popcorn @FaithPopcorn]

Forget nap pods and candy dispensers. Workers are going remote, and they are outperforming your employees in the office. https://t.co/x6eOZrvqN8

[Dave Sibiski @dsibiski]

@arnarths @reasonml @cullophid @jordwalke @Sander_Spies @matheus1lva @ReasonTownFM How is this something unique to Reason? Also, how can Reason prevent coupled code? (perhaps I don’t understand the conversation here, sorry...)

[Justin Searls @searls]

It's simultaneously true that (a) snapshot tests are easy & some will use them who otherwise wouldn't test at all and (b) that exact scenario is, on net, a counter-productive exercise in most cases. The only case I'd consider them is locking deps' behavior https://t.co/I4tDm1QO6U

[Allen Holub. https://linkedIn.com/in/allenholub @allenholub]

If a programmer is sitting in front of a computer at a Sprint Review, you’ve blown it. Put your user at the computer. Watch him/her work. Ask questions (in both directions), get feedback. If your Sprint review is a status meeting or a presentation to a PO, you’ve failed.

[George Dinwiddie ([email protected]) @gdinwiddie]

There are two ways to do something noticeably quicker:
1. do an exceptionally good job, or
2. do an exceptionally bad job.
The first is not achieved by focusing on speed, and provides other benefits than just speed.

[Dave Sibiski @dsibiski]

@mattapperson @isaiahgrey93 @AppersonLabs I think I’d be more interested in working on a project that demonstrates the concepts and principles in JS in the way we implemented them. These things have been written about for many years now and the thing people always ask is, “Let me see code like this!”

[kenbot @KenScambler]

1,000,000 components but you only need to think about 5 at once = a simple system.

20 components but you need to fit them all in your head all the time = a complicated system.

Stopping things from knowing about each other is the big game in growing a system