Ruby on Rails is a huge framework. There are modules, class, established conventions, and a slew of code that's meant to be off-limits. But, what if we took our ornery childish self and played around? This is a talk about strategies for debugging, taught through the lens of experimentation and childish play. In this talk, we will override, extend, and disable all sorts of Rails internals and see what happens.
Tech hiring has a bad reputation for a reason - it's usually awful. But it doesn't have to be that way. In this talk, we'll dive into what is wrong with many current tech hiring practices and what you can do instead. You'll learn ways to effectively assess technical ability, what makes a great interview question, how to be more inclusive, the pros and cons of giving homework assignments, and much more. You'll leave with ideas to improve your interviews, and ways to influence your company to change their hiring practices.
Woodworking and writing code go hand in hand, right?
On the surface these two activities may seem different, but the skills, tools, and mindset required to create quality furniture are consistent with the qualities required to write code that delights both the customer and developer.
As a woodworking hobbyist and software developer, I was amazed at how learning to build a table taught me to be a more impactful developer. In this talk we’ll discover how woodworking can teach us to move fast and not break things, be more consistent in our execution, and deliver lasting value to customers.
Hey there! I'm your friendly Rails controller. I bet you're wondering how you got here. Well, you visited a page in my app, and through a long path, we ended up here, in my #show method. Don't worry, I'll guide you through the steps that led you here. Then, we'll work through your request and how I put together a response for it, from building the params and caching to how I render the response. By the end, you'll know more about what we controllers actually do and how best we can meet your needs. I look forward to our adventure!
What can software learn from one of the world's oldest examples of hyperlinked data? More than 5 centuries ago the first edition of the Babylonian Talmud was printed. With its printing a unique approach to working through complex data was made accessible. I spent 20 years as a student and teacher of Talmud before becoming a developer. The methodologies I learned from Talmud have informed my code. After this session you'll have new tools for visualizing problems and how to work through them. No previous experience with Talmud is necessary, and all materials will be presented in English.
Travis. npm. Etsy. It seems like every well-loved tech company eventually becomes the kind of disaster that we whisper and rage-cry to each other about. No one ever sees it coming… but maybe we can. Let’s talk about “governance” and “alignment” -- two MBA euphemism words for “how will this organization behave under stress?” Turns out, you can predict a company’s failure mode from its business model. In this talk, you'll learn how to tell good companies -- ones with stable funding, reasonable owners, and the competence to survive -- from the ones that just have good intentions.
Whether it's @ mentions for users, hashtags, or other resources, many application these days need rich text fields. ActionText allows you to embed rich snippets for any model in your Rails app, but it requires a bit of communication with the backend. You'll learn how to add @ mentions for users and YouTube embeds as ActionText attachments and see how it all works together.
We know testing is vital and makes refactoring painless. But how to set sail to that TDD treasure? Yarr, we need to test to get experience, but need experience to test. Let’s draw a map with simple strategies for identifying test cases and building a robust test suite. X marks the spot w/ TDD tools for newbies and seasoned pirates alike.
The increased debate around ethical source threatens to divide the OSS community. In his book "The Structure of Scientific Revolutions", philosopher Thomas Kuhn posits that there are three possible solutions to a crisis like the one we're facing: procrastination, assimilation, or revolution. Which will we choose as we prepare for the hard work of reconciling ethics and open source?
You've probably experienced this. CI times slowly creep up over time and now it takes 20, 30, 40 minutes to run your suite. Multi-hour runs are not uncommon.
All of a sudden, all you're doing is waiting for CI all day, trying to context switch between different PRs. And then, a flaky test hits, and you start waiting all over again.
It doesn't have to be like this. In this talk I'll cover several strategies for improving your CI times by making computers work harder for you, instead of having to painstakingly rewrite your tests.
Have you ever stared at a blank feature spec file hoping for tests to magically appear? Well, you’re not alone! In this talk we’ll take a look at how the combination of Test-Driven Development, pseudocode and RSpec can help get you to your initial commit with confidence, one RSpec error at a time!
How you onboard someone to your team can have lasting effects on their professional success, growth, and happiness, but many teams treat onboarding as an afterthought. In this talk, you will learn how to successfully onboard a junior engineer in three steps, with the goals of building their trust, instilling confidence in their technical abilities, and enabling them to be an autonomous contributor to your team.
A/B tests should be a surefire way to make confident, data-driven decisions about all areas of your app - but it's really easy to make mistakes in their setup, implementation or analysis that can seriously skew results!
After a quick recap of the fundamentals, you'll learn the procedural, technical and human factors that can affect the trustworthiness of a test. More importantly, I'll show you how to mitigate these issues with easy, actionable tips that will have you A/B testing accurately in no time!
Clear, constructive feedback is one of the most useful gifts we can receive. We seek it tirelessly in situations where it’s denied us - that job interview we thought we aced, the dreamy date that ghosted us - but when presented in the form of an error message, many new developers recoil. They prefer to bang their heads against the same wall over and over rather than read the errors. This talk will explore the resistance new developers feel toward engaging with error messages, provide tips for overcoming it, and cover what to do when confronted by some common Ruby errors.
Mary Shelley’s Frankenstein is not a story about Frankenstein. It’s about the creation, the monster, and what we owe it.
Software does not belong to its creators. It belongs to its users. But creators bear responsibility.
Shelley warns us about the hubris of creation and the consequences of neglect. She warns that our creations will live to outrun us. But Shelley was not anti-technology. She was anti-Frankenstein. The monster is us.
How can we create ethical software? How can we care for our monster, once it’s here?
Shelley has answers. Our society depends on us learning the lessons.
Sorbet is a powerful static type-checking tool for Ruby. Type checking can catch errors early and improve the developer experience—and with the right tools, it can even be used with dynamic methods in Rails.
In this talk, we’ll cover the basics of type checking and share the lessons learned from our adoption of Sorbet type checking across our 2,500-file codebase in just six months. We’ll talk about the technical challenges we faced and how we solved them with a new Sorbet-Rails gem, which makes it easy to gradually integrate type checking into your Rails app & improve your team’s efficiency.
Modern humans aren’t great at risk assessment.
We often blithely ignore that which could harm us, and are conversely intimidated by things that are quite safe. This inability to recognize threat has vast implications for many aspects of our lives, including our careers.
Do you want to be less stressed? Make better decisions? Learn strategies for identifying (and dealing with!) unnecessary worry? Let's explore the root causes of fear and anxiety together, and discover how we can start to deliberately rewrite our instincts.
When writing code, we never have the full picture, or even know exactly where things will end up. This leads to deliberately, or accidentally, introducing small amounts of technical debt along the way, which can easily snowball out of control if ignored for too long.
In this talk we look at some typical patterns of technical debt and how to identify them. We will then learn how we can address these areas of technical debt in our codebases using a variety of static analysis techniques, making use of git history and Ruby's
Any app serving data has one main feature: a search bar. It is an experience all unto itself: the syntax, boolean sets, accuracy, paging. The problem is equal parts tooling, language processing, and data structures. Getting it right means a query syntax and UX reproducible to any underlying database adapter.
But often it's an afterthought. We reach for "good enough" in regexp and regret it when we need to make a change.
This talk will prove parsing isn't arcane compiler magic and is actually an intuitive design for code that is flexible to extension and simple to change.
While we can all say that we know a thing or two about writing code, how many of us can say we have a solid understanding of the best way to teach our practice to others? In this talk, we mine the world of educators - the real experts! - to find theories and frameworks that can help us serve as better teachers in our engineering roles. We'll talk about andragogy (pedagogy for adults), learning theories, learning styles, the Zone of Proximal development, and more.
We come from a world of facts and metrics so obviously the people with the most data wins, right? Engineering comes from a place of logic but telling the story behind that information is how the best leaders get buy-in and support for their plans. In this talk, we'll examine the how and why of storytelling, develop a framework of putting an idea into a narrative, and what tools you’ll need to complement a good story. By the end, you’ll be able to break out a story whenever you need to generate excitement, find advocates, or more budget. Is there anything more irresistible than a good story?
Unlike models and controllers, Rails views are not encapsulated. This makes them hard to reason about and difficult to test, leading us to use abstractions such as presenters and decorators. In this talk, we'll explore the inner workings of how Rails compiles and executes views today, the lessons we've learned building encapsulated views at GitHub over the past year, and how you can do the same with the support for 3rd-party component frameworks coming in Rails 6.1.
How does the Webpacker gem provide "it-just-works" webpack integration with Rails? That simplicity did not come easily. The rich functionality, complexity, and rapid evolution of the webpack ecosystem necessitated extension points beyond a simple Ruby config file.
This talk will explain the magical plumbing of Webpacker so you can leverage the webpack ecosystem on your terms.
Why is it so hard for Project Managers and Developers to communicate? After 8 years in product and project management, our speaker made the switch to the world of development, with a personal mission to make communication within technical teams easier.
This talk is intended for developers, project managers, and other members of a technical team that have experienced communication challenges across disciplines. We'll cover what a ticket looks like when you shift perspective, and include actionable steps for improving communication and understanding on your team today.
We all write code to interface with external systems, like a web service or a message queue. Can you confidently write tests without requiring the system as a dependency? How can you shield users of your code from the inner workings of the interface? Explore one attempt to answer these questions.
There's no shortage of tools at your disposal to solve these problems. This talk will introduce some available options, provide guidance on when one approach may be more appropriate than another, and discuss how to use these tools together to ease the testing process.
This breathtaking documentary series combines rare action, unimaginable scale, impossible locations and intimate moments captured from the deepest depths of Rails internals. Last year, we followed the lifecycle of best loved, wildest and most elusive Rails components through a request, from the browser to a controller action. This year, our journey takes us across the great text/plain, following the flow of HTTP streams, taking in the spectacular Action View as we find our way back to the browser. Join us to unearth the amazing lifecycle of a Rails response.
It’s a simple question: can ActiveStorage be used for image serving in your modern web apps? The answer is not so simple. Can it handle the speed requirements and size specifications of images that the modern web browsers deems as “fast”?
We’ll look at the out-of-the-box approach ActiveStorage takes on asset serving, where it works well - resizing, versioning, and security, and where we run into rough edges - image load times, CDN integration, and next gen image format storage. And then we’ll look at one pattern working in production today.
Are you newer to development and curious about freelance consulting? You can be great at it, but there’s a lot of hard work you're going to put into getting ready. How do you track hours and cost, manage client expectations, handle last minute requests and have a healthy pipeline of new clients? We’ll walk you through it, and more, both from the perspective of someone who’s been in the game for 10+ years and someone who just made the leap and is figuring it out along the way.
"Your mission, should you choose to accept it..." A stakeholder has brought you a failing project and wants you to save it.
Do you accept your mission? Do you scrap the project and rewrite it? Deciding to stabilize a failing project can be a scary challenge. By the end of this talk, you will have tangible steps to take to incrementally refactor a failing application in place. We will also be on the lookout for warning signs of too much tech debt, learn when tech debt is OK, and walk away with useful language to use when advocating to pay down the debt.
Deleting old data is awesome. Delete all the things! But sometimes, you can’t...
In fintech the financial regulators want you to keep everything, track everything and count everything. The data privacy regulator wants you to do the exact opposite.
If we are wrong, the privacy regulator will fine us, but the financial regulator will shut us down.
This is the story of confidence in privacy automation, of tests that can fail a build if an engineer forgets about privacy. This is the story of how we threw away everything we built for GDPR, and made something much better.
Then we open sourced it.
In 1883, The Boston Public Library began hiring librarians for reference services. Since then, a discipline has grown around personally meeting the needs of the public, as Library Science has evolved into Information Science. Yet, the goal of assisting with information needs remains the same. There is disciplinary overlap between programming and information science, but there are cultural differences that can be addressed. In other words, applying reference library practices to our teams can foster environments where barriers to asking for and providing help are broken down.
Debugging is one of the hardest parts of being a dev. It pushes you to understand your creations at a whole new level. Your friendly Ruby debugging tools like pry and byebug are wonderful when you are trying to track down a bug locally. But what happens when the bug is in production? What if the bug only occurs when thousands of concurrent jobs are running? How do you handle debugging those scenarios? In this talk, I will share a real-life production debugging story and the strategies my team and I used to help us debug the issue safely in production.
To the new software developer wanting to build a web app with Rails, callbacks and associations are gifts from the gods. As your application grows in complexity however, you may notice your favorite tools have actually turned on you. New users suddenly aren't getting welcome emails and you've somehow orphaned associations. Come learn proven patterns for managing lifecycle events for associated records in a way that sparks joy.
Usually people try to remove drama from their teams and their process. I’m here to tell you the opposite! As an ex-playwright I’d like to share with you the similarities I’ve found between being a professional software developer and working as part of a theatrical team. Using a theatrical lense to look at the art and craft of both theater and writing code helps us see the roles of coders, designers, testers, and managers as one cohesive goal and, I hope, helps bring us all to a deeper understanding of how to improve our individual efforts as well as work together more successfully.
Mentorship is a great way for a newer developer to benefit from the experience of a more senior developer. While there are lots of available resources on how to be a good mentor or mentee, there are far fewer guidelines on how to set up a mentoring program within your engineering organization. I'm doing this now, and I'll share the process with you: why we decided to start a team-wide mentorship program, how we got volunteers and how we matched them, and how we followed up and what worked and what didn't. You'll get everything you need to start a mentorship program at your organization.
Your team’s just inked that enterprise deal: 5000 seats at a well-known brand. But wait! Every week 100 people get hired or leave. Soon the customer's HR is complaining to the CEO and their engineers are hacking scripts against your undocumented API. Want to avoid this situation? We did too! Join us and learn how to automate identity management in Rails. We’ll demystify SCIM, peer under the hood of key Ruby auth and identity gems, and share insights to help you anticipate the twists in the road.
You want to contribute to Open Source. Great! Now what? In this talk, we'll demystify the process to help you grow your community and your career. If you can code for a living, then you can contribute. Follow our system and you'll gain the skills and mindset needed to get started and to keep going.
Accessible web applications reach wider audiences, ensure businesses are in compliance with the law, and, most importantly, remove barriers for the one in seven worldwide living with a permanent disability. But limited time, lack of knowledge, and even good intentions get in the way of building them.
Come hear my personal journey toward accessibility awareness. You will learn what accessibilility on the web means, how to improve the accessibility of your applications today, and how to encourage an environment where accessibility is seen as a requirement, not simply a feature.
How can I be more aware of my privileges and disadvantages and what do I do with that information? How can I be a better ally? What are microaggressions? How can I identify and stop my unconscious biases? We'll be navigating the answers to those questions and more in the quest to be more inclusive of others in not only our daily lives, but also in our work.
When we built our single sign-on service, we learned that syncing identity changes among applications can be deceptively complex. This is because we had to iteratively deploy the SSO service while supporting our existing applications that used the service. In this talk, we discuss lessons learned and recommendations on three key identity sync problems: 1) using editable fields such as email as an ID, 2) relying on unproven promises by standards such as SCIM, and 3) split-tenant situation. This talk will help developers avoid some pitfalls while building or working with an identity service.
While many software engineers don’t work directly with prime numbers on a daily basis, they play a crucial role in keeping your web applications secure in the form of Hypertext Transfer Protocol Secure (HTTPS).
In this talk, you will learn the inner workings of how HTTPS uses prime numbers to keep your data private as it travels over the internet. We will cover topics such as symmetric and asymmetric encryption, and why prime numbers are just so damn hard to crack. By the end, you will understand how to encrypt and decrypt data yourself with Rails and the Ruby standard library.
So come join me as we demystify HTTPS using code, color theory, and only a pinch of math 🤓.
As Rails developers, we depend on network protocols to ensure the products we build are available and accessible to our users. Despite this, many of us are poorly aware of how the layers of the network stack actually work, or why they are there.
Understanding the things that happen between physical signals on the wire and your Rails application will help you hone your craft and level you up. Fortunately, the basic concepts of network protocols are easy to grasp, with a little guidance. So let's walk together through these concepts, and peel away the layers of the network stack one by one.
The internet grows every day. Every second, one of us is making calls to an API, uploading some images, or streaming the latest video content. But what is the cost of all this?
Every day, a data center stores information on our behalf. As engineers, it's easy to focus on the code and forget the tangible impact of our work. This talk explores the physical reality of creating and storing data today, as well as the challenges and technological advancements currently being made in this part of the tech sector. Together, we'll see how our code affects the physical world, and what we can do about it.
How does Spring boot your Rails app instantly, or Puma route requests across many processes? How can you fine-tune your app for memory efficiency, or simply run Ruby code in parallel? Find out with a deep dive on that staple UNIX utensil, the
fork() system call!
After an operating systems primer on children, zombies, processes and pipes, we'll dig into how exactly Spring and Puma use
fork() to power Rails in development and production. We'll finish by sampling techniques for measuring and maximizing copy-on-write efficiency, including a new trick that can reduce memory usage up to 80%.
Understanding new concepts and complex systems is hard. Explaining them? That’s even harder.
Like anyone in a highly specialized career, software engineers may struggle to convey information concisely, confidently, and clearly to their technical and non-technical teammates. As a former illustrator and graphic designer,
Data increasingly drive the world around us, but humans are motivated by stories. While there may be no such thing as a 10x engineer, you can 10x your team—making each teammate X% more productive over a sprint, project, or a whole career—by telling the right story. In this talk, we'll learn the art of "10x storytelling": calibrating your message for your audience, crafting memorable narratives, and structuring your story so your audience reaches your intended conclusions on their own. By the end, you'll come away with a rich new set of tools to help push you and your teammates to new heights.
What would you do to convince a large audience, who has little context, to use your solution to a problem? One way is to write a design document, which helps scale technical communication and build alignment among stakeholders. The wider the scope of the problem, the more important alignment is. A design document achieves this by addressing three key questions: “what is the goal?”, “how will we achieve it?” and “why are we doing it this way?”. This talk will cover identifying your audience, effectively writing answers to these questions, and involving the right people at the right time.
Professor When is an lemur that travels through all of DateTime and Space on wondrous adventures, but something is askew! In their DARTIS (Doing ActiveSupport Rigging of Time including Space) something is broken in their TimeyWimey extensions, and now they can't travel through time!
Join us in this magical adventure in manipulating Time itself to save Professor When through writing our own TimeyWimey extensions for their DARTIS!
Setting up a performance analytics tool like NewRelic or Skylight is one of the first things many developers do in a new project. However, have you ever wondered how these tools work under the hood?
In this talk, we will build a basic performance analytics tool from scratch. We will deep dive into ActiveSupport instrumentations to collect, group and normalise metrics from your app. To persist these metrics, we will implement a simple time series database and visualise the data on a webpage. By the end of the talk, you will know how your favourite performance analytics tool works.
Secrets. They are everywhere. From urban legends, fried chicken recipes, to encrypted messages... okay, one of these is not like the rest. In this talk we will focus on one of them, and it's not the fried chicken. Active Support provides a suite of little-known cryptography APIs. While you may not have encountered them directly, they secretly power your Rails app. From cookies to CSRF tokens, these APIs are crucial building blocks in the framework. Let's take a look at the motivations behind them, what they are used for in Rails, and why you may want to take advantage of them in your own apps.
- Why do our workplaces make us feel burnout and emotional exhaustion?
- Why do books about object-oriented programming prefer composition to inheritance?
These questions seem unrelated, but here's what they share: assumed context—details of ONE situation that we assume to be true in ALL situations. Learning to recognize assumed contexts has given me the power to see more options when I make software decisions.
In this talk, you'll learn how to challenge assumptions in common programming advice, solicit new perspectives, and give yourself options when you previously thought you had none.
As a new or experienced leader, you spend your time worrying about your team and their performance. That's not unique to software; the oldest entity in the government, the Army, has been honing world-class leaders for 245 years. But if you have no interest in shipping off to bootcamp, how can you glean these lessons?
In this session, I'll share the lessons of being a squad leader and military interrogator. We will analyze relatable stories of hardship, teamwork, and triumph from combat and software teams to drive home principles that will make your confidence as a leader bulletproof.
I studied both medieval literature and computer science in college, but I never expected the hours I spent reading Chaucer would help prepare me to be a software engineer. Luckily, I was wrong. Medieval literature taught me how to trace language as it evolved and immerse myself in historical context. I’ll demonstrate how you can use those same strategies to navigate large, long-lived codebases. Whether you’ve never read a line of Middle English or you’re an expert on courtly romances, you’ll gain a new perspective on working with legacy code from this talk.
For the longest time your application has supported two types of users: 'users' and 'admins'. Role Based Access Control with broad sets of permissions has been your goto until now - but what happens when things get more complicated? Multitenancy, permissions to individual resources, and enterprise level compliance create an explosion of roles and a need for a more fine-grained approach. In this talk we'll discuss all things authorization, with an overview of common paradigms (RBAC, ABAC, LBAC, so many BACs), popular libraries for Rails, and general tips on a topic that has so much information on how to get started but so little on what to do when 'admin: true' just isn't enough.
You’ve rolled up your sleeves and built the most secure custom auth ever conceived by a dev team. Suddenly, your CTO informs you that your app will be participating in the Org's new Bug Bounty program. Terror fills your heart as you imagine security experts making mince-meat of your beautiful auth system. If only you knew their game plan...
Kolide’s CEO, Jason Meller has been rolling his own Rails auth for over a decade and has the bug bounty receipts to prove it. In this talk, he will walk you through Kolide's actual bounty reports so you can level up your team’s auth system.
Identity management? Stick a username and (hashed) password in a database, and done! That's how many apps get started, at least. But what happens once you need single sign-on across multiple domains, or if you'd rather avoid the headache of managing those passwords to begin with? This session will cover protocols (and pitfalls) for delegating the responsibility of identity management to an outside source. We'll take a look at SAML, OAuth, and OpenID Connect, considering both the class of problems they solve, and some new ones they introduce!
If you're lucky there's a good chance your application's User models will one day grow a Team association — if it hasn't happened already. With teams, you're no longer making an app for individuals but modeling entire companies full of them. In this talk we'll look at sustainable patterns for authenticating and managing Rails users into collaborative groups without falling into the many user-hostile pitfalls along the way.
Passwords are pretty risky these days, with millions of them compromised in leaks and sophisticated phishing pages everywhere. SMS or one-time codes are no silver bullet, they just require fancier attack techniques. But fear not - WebAuthn is here! Part of the FIDO2 framework, WebAuthn lets you authenticate with your fingerprint, your face or other passwordless hardware authenticators. In this talk, we'll go through the nuts and bolts of FIDO2's passwordless authenticators and by the end of it, you'll have a good understanding of FID02, how WebAuthn works, and how to support it in your Rails app.
We picked the wrong technology. We worked in silos. We prematurely optimized. We introduced too many changes at once. And yet somehow we delivered a system that is integral to a shopping rewards app used by millions across the United States. I want to tell you the story of how the best of intentions led to crucial blunders. In this public, honest, and vulnerable post-mortem I will share the missteps I made so that you can avoid them.
Sometimes applications are behaving “normally” along strict definitions of HTTP statuses but under the surface, something is terribly wrong. In 2017, Checkr’s most important API endpoint went down for 12 hours without detection. In this talk I’ll talk about this incident, how we responded (what went well and what could have gone better) and explore how we’ve hardened our systems today with simple monitoring patterns.
Have you ever looked at a bug and wondered why it actually happens? It's easy to chalk it up to sloppy coding but that's almost never the case.
In this talk we'll be dissecting a exploit from Pokemon Blue known as the "Missingno" glitch. We'll look at the details of each of the seemingly random bugs behind this exploit. We'll look at why these bugs happened, and the lessons we can apply to our Ruby code more than 20 years later.
If you've never played or even heard of Pokemon, that's ok! As long as you're interested in a deep dive into a fascinating set of bugs, this talk is for you.
Large test suites can become slow, flaky, and expensive to maintain over time. In this talk, we will walk you through how we scale testing of one of the largest Rails apps in the world. We have developed a test selection tool based on dynamic analysis that selects a subset of tests to run, improving speed and reducing costs of running CI, while still ensuring >99% of test failures are detected. Come and join us to hear about the benefits of test selection, why it works, and how to deliver it to 1000+ engineers with minimal disruption, as well as our plans for the future.
Tens of millions of people can download and play the same game thanks to mobile app distribution platforms. Highly scalable and reliable API backends are critical to offering a good game experience. Notable characteristics here is not only the magnitude of the traffic but also the ratio of write traffic. How do you serve millions of database transactions per minute with Rails?
The keyword to solve this issue is "multiple databases," especially "sharding". From system architecture to coding guidelines, we'd like to share the practical techniques derived from our long-term experience.
Rails applications tend to turn into giant monoliths. Keeping the codebase maintainable usually requires architectural changes. Microservices? A distributed monolith is still a monolith. What about breaking the code into pieces and rebuild a monolithic puzzle out of them?
In Rails, we have the right tool for the job: engines. With engines, you can break your application into components—the same way as Rails combines all its parts, which are engines, too.
This path is full of snares and pitfalls. Let me be your guide in this journey and share the story of a monolith engine-ification.
A strength of the tech industry is its ability to facilitate remote work. Remote work helps people — particularly people who are part of marginalized communities, such as folks who are undergoing a gender transition. We often talk about how to foster inclusive teams and remote work can be a big factor in that!
In this talk, you’ll learn about barriers that disproportionately affect underrepresented folks in tech, like health concerns, financial/geographical logistics and emotional burnout, as well as the ways working remotely can ease those burdens, and how to promote healthy distributed teams.
Jessie is a junior developer looking for a new job, and has gotten an offer! She'll probably accept it as is: she doesn't want to risk doing anything that would jeopardize the opportunity. What Jessie doesn't know is that the company she interviewed with is lowballing her: she could have negotiated a much higher salary!
Most of us receive a job offer at least once in our lives, and many of don't negotiate. Negotiating salary sounds scary, but it doesn't have to be. In this talk you'll learn how to negotiate your next job offer or raise, even if you hate confrontation.
There are a lot of talks and advice about Imposter Syndrome out there, and most of those talks assume it's all in your head. Well, what if it's not? What if you're not good enough and they fire you for it? In this session, we'll talk about how to succeed when you're bad enough to get fired. It's also a talk that teaches practical approaches for negotiating salaries, having difficult conversations, and owning all of your skills. These are ideas that can work whether you're one of the rockstars, an imposter, someone on the chopping block, one of the fired, or you just want a broader perspective.