General

Cultivating Value Through Developer Communities with Ronald Williams

Published Jun 25, 2024

Updated Dec 11, 2024

1 min read

In this JS Drops presentation, Ronald Williams, Senior Community Programs Manager at Cypress.io, discusses key tips for cultivating and capturing value within a developer community. Ronald emphasized the need to differentiate between creating useful content and deriving business gains from it. He highlights the significance of reporting the impact of initiatives by combining both aspects, stressing that it's crucial not only to focus on providing valuable content for the community but also to understand how it translates into tangible business outcomes.

To illustrate this concept, Ronald provides examples such as ambassador programs and conferences, which offer useful content and networking opportunities for the community while directly impacting revenue generation. He emphasizes the importance of understanding revenue impact through metrics like conversion rates, retained members, influenced members, and expansion. By measuring these metrics, businesses can effectively gauge the success of their community initiatives and make informed decisions to enhance their strategies.

The presentation emphasizes the value of developer communities in various aspects. Data from the Developer Marketing Alliance supported the notion that developer communities are crucial for feedback gathering, creating ambassador programs, understanding the developer audience, and educating others about products. Ronald stresses the need for effective communication of the business value of community initiatives to stakeholders and advised refining existing programs to maximize value rather than starting from scratch. This approach allows businesses to build upon their current community initiatives and make them even more impactful.

This Dot is a consultancy dedicated to guiding companies through their modernization and digital transformation journeys. Specializing in replatforming, modernizing, and launching new initiatives, we stand out by taking true ownership of your engineering projects.

We love helping teams with projects that have missed their deadlines or helping keep your strategic digital initiatives on course. Check out our case studies and our clients that trust us with their engineering.

Engineering Management: Just a Detour? - Charity Majors, CTO at Honeycomb

Rob Ocel interviews Charity Majors, CTO at Honeycomb on engineering leadership. Engineering management was once thought of as an inevitable destination for engineers who sought advancement in their careers, but now engineers have more options than ever. Many engineering managers are becoming engineers again, and the role of manager requires a significant amount of emotional labor. Should anyone want to be an engineering manager? Charity shares her journey of becoming an accidental CTO and founder, despite never aspiring to be a manager. She talks about the importance of engineering managers, and how they help teams outperform those without one, but acknowledges the role is challenging and not always enjoyable. Charity and Rob discuss how good managers can transform a company. They are compared to the nervous system of a company, routing information and ensuring everyone has what they need to succeed. Charity highlights the difficulty engineers face when transitioning from a ticket system to a more autonomous work environment. This shift can be challenging, as engineers may struggle with the newfound freedom and responsibility. It can take years to fully make the transition, so leaders looking to promote engineers to management need to be committed to and patient with the transition. Both Charity and Rob agree that a strong social support system for engineering managers is necessary as the role can be isolating, and having a network of peers who understand the challenges can be invaluable. Charity Majors' experiences and perspectives shed light on the challenges and rewards of the role, and when engineers should and should not pursue this career path....

Jan 4, 2024

2 mins

Engineering Leadership

Cybersecurity Leadership 101 with Dr. Joye Purser

Dr. Joye Purser is the field Chief Information Security Officer (CISO) at Veritas, a software company specializing in data backup systems. Veritas' global leadership in cybersecurity plays a critical role in data backup and restoration in the cybersecurity landscape. Dr. Purser's career ranges from her time at the Cybersecurity and Infrastructure Security Agency (CISA) for the U.S. Department of Homeland Security to roles at the Pentagon and the White House. Dr. Purser talks about common misconceptions regarding working in the government in the field of technology and notes the increasing trend of tech companies recruiting individuals with defense and military backgrounds due to rising threats to the private sector. There is an evolution in cybersecurity, particularly post-pandemic, with an increased sophistication of cyber threats and a rise of ransomware attacks. There is now a heightened focus on critical infrastructure security and a new outlook on the potential life-threatening consequences of cyber disruptions. The qualities of effective cybersecurity leadership are vision, adaptability, and emotional intelligence. Dr. Purser elaborates on the importance of having a clear vision, especially in an emerging role like hers at Veritas. She shares her experience obtaining the Certified Information System Security Professional (CISSP) certification, highlighting the necessity of adaptability in acquiring new skills and staying ahead of the rapidly changing cybersecurity landscape. Dr. Purser stresses the significance of soft influencing skills, adaptability in communication styles based on the audience, and the ability to read the room. She emphasizes the need for emotional intelligence when asking for resources or driving change, recognizing the discomfort associated with these demands. Listen to the podcast here: https://engineeringleadership.podbean.com/e/joye-purser/...

Jan 16, 2024

2 mins

Engineering Leadershipcybersecurity

Building a Stripe App: A Step-by-Step Guide to QR Code Generation

Building a Stripe App: A Step-by-Step Guide to QR Code Generation Why Build a Stripe App? I recently participated in an audio space with the Stripe team, and something they said really stuck with me: the Stripe app store is a growing area that isn't overly saturated yet. There's a lot of potential for new apps, and companies can use this opportunity to grow. I work at a company called This Dot Labs, and we've created several Stripe apps and even own one. After looking at the data, I can confirm that the Stripe team was right! Creating a QR Code Generator App For this tutorial, we'll build a QR code app that can take a URL and generate a code for it. This is a good use case to help you understand the ins and outs of Stripe's developer tools. Why QR Codes? QR codes are useful tools that have become common in e-commerce, restaurants, and other industries. While Stripe already has a QR code tool, we'll make our own to familiarize ourselves with their syntax and problem-solving approaches. Project Structure Before we dive into the implementation, let's look at the structure of our Stripe App QR Code project: * .vscode: Contains settings for Visual Studio Code * source/views: Holds the main application views * .gitignore: Specifies files to ignore in version control * stripe-app.json: Defines the Stripe app configuration * ui-extensions.d.ts: TypeScript declaration file for UI extensions * .build: this is where the built Stripe app gets placed. Step-by-Step Implementation 1\. Install Stripe Locally First, you need to install Stripe on your local machine. The documentation provides great instructions for this: * For Mac users: Use Brew to install * For Windows users: Download the package and add it to your environment variables You can find the details here in the stripe docs to install the Stripe CLI https://docs.stripe.com/stripe-cli When using Windows, you must do stripe login from Powershell, NOT from Git bash or any other tool. After the server is up, then you can continue using git bash for everything else. After stripe login, you need to enter stripe apps start. Once you do that, the server is up and running and you can go back to using git bash or any other tool. 2\. Install Dependencies We'll be using an extra package for QR code generation. Install it using npm: ` 3\. Set Up the Main Component Let's look at the home.tsx file, where we'll use Stripe's UI components: ` These components are similar to other UI libraries like Bootstrap or Tailwind CSS. 4\. Create the UI Structure Our app will have: * An input field for the URL * Validation using a regex pattern * Error handling for invalid URLs * QR code generation and display Here is the Home.tsx file that is located in the src/views folder ` * ContextView` is at the top level of the app where we see the Title and the link to the Stripe Docs that we placed in our Context View. * Box is how you use Divs. * Banners can be used to show notification errors or any other item you wish to display. * Textfields are input fields. * Everything else is pretty self-explanatory. 5\. Handle Content Security Policy One problem I personally ran into was when I tried to redirect users, the Stripe policies would block it since I did not express that I knew what it was doing. I had to go into the stripe-app.json file and mention the specific security policies. For this particular exercise, I kept these as null. This is my stripe-app.json file. ` 6\. Configure App Views As you can see here, the stripe-app.json file shows the views for each file I have. The Home.tsx file and the Invoice.tsx are also included This is our way of saying that for each view we have, show the app functionality on that page. Our stripe-app.json file will show it but also, the manifest.js file in our .build folder will also show the same. Any view that doesn't have a file will not show the application's functionality. So, if I were to go to transactions, the app would not show the same logic as the home or invoices page. By following these steps, you'll have a fully functional QR code generator app for Stripe. This is just a simple example, but the potential for Stripe apps is massive, especially for businesses serving e-commerce customers. If you need help or get stuck, don't hesitate to reach out, danny.thompson@thisdot.co. The Stripe team is also very active in answering questions, so leverage them as a resource. Happy coding!...

Dec 18, 2024

4 mins

stripe

Understanding the Difference Between `:focus` and `:focus-visible` in CSS

Understanding the Difference Between :focus and :focus-visible in CSS I have learned my fair share about the importance of keyboard accessibility, so I know that visual indication of the focused element is very important. But the well-known :focus pseudo-class is not always the best fit for this job. That's where :focus-visible comes in. Let's look at the differences between these two pseudo-classes and explore the best practices for using them effectively. What is the :focus Pseudo-Class? The :focus pseudo-class is a CSS selector that applies styles to any element that receives focus, regardless of how that focus was triggered. This includes focus events from keyboard navigation, mouse clicks, and touch interactions. Example Usage of :focus ` In this example, the button will display a blue outline whenever it is focused, whether the user clicks on it with a mouse, taps it on a touchscreen, or navigates to it using the keyboard. What is the :focus-visible Pseudo-Class? The :focus-visible pseudo-class is more specialized. It only applies styles to an element when the browser determines that the focus should be visible. This typically occurs when the user navigates via the keyboard or assistive technologies rather than through mouse or touch input. Example Usage of :focus-visible ` Here, the button will only show a blue outline when focused through keyboard navigation or another input method that usually requires visible focus indicators. Key Differences Between :focus and :focus-visible :focus - Behavior: Applies to any element that receives focus, regardless of the input method. - Use Cases: Ensures that all interactions with the element are visually indicated, whether by mouse, keyboard, or touch. :focus-visible - Behavior: Applies styles only when the focus should be visible, such as using a keyboard or assistive technology. - Use Cases: Ideal for scenarios where you want to provide focus indicators only to keyboard and assistive technology users while avoiding unnecessary outlines for mouse and touch users, typically required by design. Accessibility Implications :focus - Pros: - Guarantees that all users can see when an element is focused, which is critical for accessibility. - Cons: - Can lead to a suboptimal experience for mouse users, as focus styles may appear unnecessarily during mouse interactions. :focus-visible - Pros: - Enhances user experience by showing focus indicators only when necessary, thus keeping the interface clean for mouse and touch users. - Tailors the experience for keyboard and assistive technology users, providing them with clear visual cues. - Cons: - Additional considerations may be required to ensure that focus indicators are not accidentally omitted, especially in older browsers that do not support :focus-visible. - There may be cases where you want to show focus indicators for all users, regardless of input method. Best Practices for Using :focus and :focus-visible To achieve the best accessibility and user experience, combining both :focus and :focus-visible in your CSS is often a good idea. Combining :focus and :focus-visible ` Here is a Stackblitz example of what such styling could look like for you to try out and play with. Additional Tips - Test with Keyboard and Assistive Technology: Ensure that your web application is navigable using a keyboard (Tab, Shift + Tab, etc.) and that focus indicators are visible for those who rely on them. It's never a bad idea to include accessibility testing in your e2e testing suite. - Provide Clear Focus Indicators: Make sure that focus indicators are prominent and easy to see. A subtle or hard-to-spot focus indicator can severely impact accessibility for users who rely on keyboard navigation. Conclusion The :focus-visible pseudo-class offers a more refined way to manage focus indicators, improving accessibility and user experience, particularly for keyboard and assistive technology users. By understanding the differences between :focus and :focus-visible, and applying best practices in your CSS, you can create more accessible and user-friendly web applications. Remember, accessibility should never be an afterthought. By thoughtfully applying focus styles, you ensure that all users, regardless of how they interact with your site, can easily navigate and interact....

Nov 8, 2024

3 mins

AccessibilityCSSPlaywright

Let's innovate together!

We're ready to be your trusted technical partners in your digital innovation journey.

Whether it's modernization or custom software solutions, our team of experts can guide you through best practices and how to build scalable, performant software that lasts.

Cultivating Value Through Developer Communities with Ronald Williams

You might also like

Engineering Management: Just a Detour? - Charity Majors, CTO at Honeycomb

Cybersecurity Leadership 101 with Dr. Joye Purser

Building a Stripe App: A Step-by-Step Guide to QR Code Generation

Understanding the Difference Between `:focus` and `:focus-visible` in CSS

Let's innovate together!

You might also like

Engineering Management: Just a Detour? - Charity Majors, CTO at Honeycomb

Cybersecurity Leadership 101 with Dr. Joye Purser

Building a Stripe App: A Step-by-Step Guide to QR Code Generation

Understanding the Difference Between `:focus` and `:focus-visible` in CSS