SCNA

Software Craftsmanship North America is a conference for software professionals interested in improving their craft, their community, and themselves.

[SCNA @scna]

@slowteetoe @scna Nothing planned for 2019 / 2020. Thanks for reaching out!

[SCNA @scna]

@ajw1970 @scna No, not this year.

[SCNA @scna]

Videos from this year's talks are now live on our site! Revisit the insightful and inspiring presentations from @rachelcdavies, @spolsky, @paytonrules, @bryanl, @samjonester, @jleo3, @mona_soni, and @navteniev - https://t.co/vsOJaxgkw0

[SCNA @scna]

Huge thank you to our sponsor @SocGen_US for providing the venue and helping make this year's SCNA such a success!

[SCNA @scna]

"There’s a relationship between code ownership and the quality of that code. Code review is a mechanism for scaling code ownership across teams and organizations." — @navteniev closes out today's talks with ways we can work better together, even on large, distributed teams

[SCNA @scna]

"Four major aspects to make my teams more effective: people, delivery, resources, and architecture. If you address these four areas, your teams will flourish" — @mona_soni helps us reflect on our teams and identify ways we can be more effective in our daily work

[SCNA @scna]

"It’s hard to tell the story of @StackOverflow without describing it as a huge act of generosity from the people who answer questions on there" - @spolsky shares his experience helping developers become more efficient. Each answer on SO saves another developer about 30 minutes.

[SCNA @scna]

"Anti patterns in speech portend disaster. We need to translate 'This has never been done before' to, 'We fear the solution doesn’t exist in this room,' and then act so we don’t head down the path towards doomsday." — @jleo3 helps us predict the apocalypse on software projects

[SCNA @scna]

"Amplify signals that help your team understand what is going on in the code, and do as much as possible to reduce the noise" — @samjonester helps us design better systems by focusing on what's important, not what's convenient.

[SCNA @scna]

"Engineers are also stakeholders. They maintain an asset: code that needs to be managed. They also must support business needs while leaving code in better shape than they found it. That might mean a lot of saying no...nicely" @rachelcdavies confronts the realities of legacy code

[SCNA @scna]

"Measuring people against one another is a recipe for frustration and pain. Measure people against their goals." — @bryanl offers perspective on comparing ourselves to others, and appreciating the long view of the software we write.

[SCNA @scna]

"We want to set up an apprenticeship not for what’s best for the employer but for what’s best for the industry. Those aren’t always the same thing" - @paytonrules starts off this year's SCNA by unpacking where traditional education fits.

[SCNA @scna]

@JosephPMcKenzie Looking forward to seeing you and your team there as well!

[SCNA @scna]

Last call for tickets to next week's SCNA! In just *4 hours* we're closing registration for the day full of inspiring and insightful talks organized by @8thLightInc and sponsored by @SocGen_US! https://t.co/UdSFQAz9VI

[SCNA @scna]

Only *24 hours* left to buy tickets for next week's SCNA in New York! Don't miss @rachelcdavies, @spolsky, @bryanl, @paytonrules, @mona_soni, @samjonester, @navteniev, and @jleo3—buy your ticket now! https://t.co/TurtIWQuHt

[SCNA @scna]

The co-founder of @StackOverflow and author of four books on software, @spolsky is joining us at this year's SCNA to explain how he built and scaled one of the web’s most valuable resources, and how we hold the keys to our own futures https://t.co/N6QrKIgw6a

[SCNA @scna]

Give yourself time to respond before the apocalypse comes to your project! At this year’s SCNA, @jleo3 will share processes and methods that can help you identify and avoid impending danger. https://t.co/p0M3gs06gN

[SCNA @scna]

Universities battle the perception that their courses are “too theoretical,” yet many developers with non-traditional backgrounds report Imposter Syndrome. At SCNA, @paytonrules will propose a solution, and see if the current system can work for you. https://t.co/pdJKYijDMl

[SCNA @scna]

Many projects have adopted code reviews, but empirical research shows that we can be using them more effectively. At SCNA, @navteniev will share his insights, and how he’s leveraged code reviews on @LinkedIn’s Flagship Product Engineering team. https://t.co/uzTqXduNWQ

[SCNA @scna]

Gain some practical strategies for coming to grips with an aging code base—while setting realistic expectations about what’s possible—with @rachelcdavies at this year's SCNA! https://t.co/Bub8p9uQvd