Do you ever find yourself with an itch to write but end up staring at a blank screen until you eventually give up and do something else? We’ve been there, and we’re ready to help you get started.
Sharing your expertise with the developer community online through thought-leadership articles and tutorials has many benefits, including becoming known as the go-to expert for a topic, building connections with others who share a passion for your topic, and enhancing your case for a promotion. In this workshop, we’ll guide you through:
- Brainstorming and selecting a topic
- Optimizing your content for search engines (SEO)
- Leveraging best practices as you write your article or tutorial
- Reusing your content on other platforms
By the end of this workshop, you will publish an article or tutorial online and have a topic for your next piece.
GDSC MESCOE is here with its very first event - LET'S TALK ANDROID Dev with Shreyas Patil.
Android app development is pivotal for businesses to reach out to more customers, improve their sales, brand image and create a loyal customer base.
So if you have myths, questions, or an unquenched thirst to know more about Android, this is the perfect session for you!
Kickstarting career as an Android developer.pdfShreyaDhurde
Shreyas Patil outlines a roadmap for becoming an Android developer. He recommends starting with learning programming fundamentals like Java and Kotlin, as well as concepts like OOP and software engineering. Developers should build small sample projects, contribute to open source, and learn from documentation rather than videos. Networking within communities and showcasing skills on websites and GitHub can boost one's career. Maintaining skills and helping others are also important parts of the process.
Broad-stroke overview of a systematic self-publishing process. This presentation is intended to help aspiring authors overcome any obstacles they may face during the writing, publishing and promoting of their first book. Includes tips and resources for each phase of the process.
Content hustle. How to build a strategy and grow a blogDakiry
This document provides tips on how to build a content marketing strategy and grow a blog. It recommends defining goals, researching buyer personas, creating a buyer's journey map and content flow, making a content audit, and setting up an editorial calendar. It also offers advice on choosing blog topics, writing headlines, outlining content for writers, publishing posts, and avoiding common mistakes. The overall strategy involves creating valuable content aligned with buyer needs to attract and engage an audience.
This is a workshop put together by the UC Berkeley Library on how to get started with Pressbooks as digital book creation and publishing platform. It was delivered on September 15, 2020.
GDSC MESCOE is here with its very first event - LET'S TALK ANDROID Dev with Shreyas Patil.
Android app development is pivotal for businesses to reach out to more customers, improve their sales, brand image and create a loyal customer base.
So if you have myths, questions, or an unquenched thirst to know more about Android, this is the perfect session for you!
Kickstarting career as an Android developer.pdfShreyaDhurde
Shreyas Patil outlines a roadmap for becoming an Android developer. He recommends starting with learning programming fundamentals like Java and Kotlin, as well as concepts like OOP and software engineering. Developers should build small sample projects, contribute to open source, and learn from documentation rather than videos. Networking within communities and showcasing skills on websites and GitHub can boost one's career. Maintaining skills and helping others are also important parts of the process.
Broad-stroke overview of a systematic self-publishing process. This presentation is intended to help aspiring authors overcome any obstacles they may face during the writing, publishing and promoting of their first book. Includes tips and resources for each phase of the process.
Content hustle. How to build a strategy and grow a blogDakiry
This document provides tips on how to build a content marketing strategy and grow a blog. It recommends defining goals, researching buyer personas, creating a buyer's journey map and content flow, making a content audit, and setting up an editorial calendar. It also offers advice on choosing blog topics, writing headlines, outlining content for writers, publishing posts, and avoiding common mistakes. The overall strategy involves creating valuable content aligned with buyer needs to attract and engage an audience.
This is a workshop put together by the UC Berkeley Library on how to get started with Pressbooks as digital book creation and publishing platform. It was delivered on September 15, 2020.
6 important guidelines for paper presentation conference 2023 | IFERPIFERP
Consider yourself on a stage in front of a large audience of distinguished academics, researchers, and industry professionals, presenting your most recent research findings at a major international conference. You have spent months preparing, meticulously researching your topic, and putting together a compelling presentation. As you begin to speak, all eyes are on you, and you can feel the weight of their expectations on your shoulders. Visit https://www.iferp.in/blog/2023/02/25/6-important-guidelines-for-paper-presentation-conference-2023/ to know more.
If you are inspired during practical and hands-on sessions during the three days at Devoxx UK 2015, have you thought about how you might pass on this knowledge and experience to others? If so, then we have just the right solution for you! Running a Hackday, either at your workplace or within your local community, can be very rewarding. Come along to this session and learn all about the art of running hack session from Richard Warburton, author of Java 8 Lambda and regular organiser of hackdays in the London Java Community.
You will be able to answer your own questions like: Why you should run a hackday ? What’s involved in running one ? Examples of successful hackdays Tips for being successful
This document discusses best practices for writing documentation. It explains that documentation is important for users to understand how to install and use a project, and for contributors to understand how to contribute. The document outlines different types of documentation including installation instructions, user guides, API references, examples, and tutorials. It also discusses formats like HTML, PDF and interactive help. The document provides examples of well documented projects and gives tips for documentation quality like maintaining examples, writing documentation alongside code, and considering your audience. It recommends tools for documentation and provides guidance on where new users and contributors should start with documentation.
A firm grasp of scientific method and ability to write clearly and convincingly is a great assert to any professional in sciences.
Conducting research and publishing peer reviewed papers train professionals in both scientific method and writing. Moreover, having research papers in your resume is considered a huge plus in both industry and academia. However, conducting research and getting them published requires professionals to approach the problem and present their solutions form a unique angle. The talk will address research in general and writing research papers. Specifically, the talk will cover peer review process, what is a contribution?, and basic composition of
a research paper, describing potential pitfalls.
I've been in the technical writing field for a few years now. This pdf covers the responsibilities of technical writers, research methods, style guides, and best practices in technical writing.
How To Guide : Researching Topics For BlogsOmnePresent
The document provides tips for researching topics for blogs. It recommends creating a research system to organize notes and materials collected from various sources. Specific keywords should be chosen and included in the content to improve SEO. Related search terms on Google can help identify commonly searched phrases. Tools like Twitter and Google+ help gauge reader interest and ensure the topic has ample information available. Qualitative research is necessary to write great blog posts with correct information, statistics, and unique elements like infographics to stand out.
How to deliver the right software (Specification by example)Asier Barrenetxea
Talk about Specification by Example. What's the problems it tries to tackle and how to solve them.
I gave this talk at Thoughtworks on a "lunch and learn" meeting for the company.
This is a new version of my previous presentation about "Specification by example"
https://www.slideshare.net/AsierBarrenetxea1/spec-byexample-v2
Derek Parham gives a talk on how to be an effective tech lead based on his experience leading large engineering teams at Google. He outlines key responsibilities of a tech lead including communicating with different stakeholders, building up the team, and looking for unaddressed problems. Parham emphasizes limiting meetings to protect engineering time, using design reviews to spread knowledge, and delegating tasks to empty one's plate and develop other leaders. He encourages tech leads to teach their engineers, build more tech leads as the team grows, and make team success a higher priority than personal success.
6 Academic Research Paper Writing Tips - 2023.pdfIFERP
Writing an academic research paper frequently necessitates some level of academic research writing experience and prowess. Both aspiring research authors and research authors who have previously struggled with academic writing will find the six tips highlighted in this blog to provide a wealth of information about what steps they can take to make their next research writing endeavor a pleasant one. Visit https://www.iferp.in/blog/2022/08/10/6-tips-for-how-to-write-academic-research-paper/ for more information.
This document provides tips and strategies for college students related to organization, note-taking, studying, and writing papers. It discusses organizing emails and files using technology like Moodle and Google apps. It offers various note-taking methods and strategies for effective studying, such as the Cornell note-taking system and the Cornell 5-day study plan. The document also covers best practices for test-taking, writing strong papers using MLA or APA style, and emailing professors appropriately.
The document discusses growth and development. In a concise yet informative manner, it touches on the natural process of expanding and increasing in size over time through nourishment and care. While brief, it implies the importance of fostering growth through proper support and conditions.
This document provides advice and guidance for writing books related to open source software. It discusses leveraging community involvement to gain recognition, finding inspiration in open source projects, and strategies for working with publishers or self-publishing. The key recommendations are to write daily to build skills and an audience, contribute to open source documentation projects to gain experience and exposure, and understand publishing contracts and self-publishing options.
This document provides guidance on how to write a thesis. It discusses organizing the thesis by including elements like the title page, abstract, table of contents, introduction, literature review, methods, results, discussion, and references. It emphasizes developing a clear structure with an outline and using visual elements like figures and tables to present data. The document also covers writing each section, editing for clarity and flow, attention to style/formatting details, and managing the writing process with planning and regular writing. The overall message is that a well-organized thesis with a logical structure and flow is important to effectively communicate the research.
This presentation is an introduction to the field of technical writing based on my personal journey and philosophy of documentation, and was presented to the first meeting of Write The Docs Nigeria on February 20, 2021.
The document outlines 7 ways to build an API that developers will hate, including keeping endpoints secret, using offensive language, pushing changes whenever desired without versioning or documentation, inconsistent naming, and ignoring errors and rate limits. It then provides 7 ways to build an API that developers will love, such as making the API discoverable, using inclusive language, versioning, following processes for changes, consistency, clarity on rate limits, and appropriate use of status codes.
Developer Advocacy: A Career Path for Those With a Passion for Code, Communit...Lauren Hayward Schaefer
Chances are good that you’ve interacted with a developer advocate at one point or another. Perhaps you’ve chatted with them at a booth at a conference, read their blog post, or cloned their code sample on GitHub. This session will provide you with a deeper understanding of the role of developer advocacy and its significance in the tech industry.
What is a developer advocate? A developer advocate advocates for two entities at the same time: at their company, they advocate for the developer community, and, in the developer community, they advocate for their company. Developer advocates have a passion for developer experience and reaching developers where they are, through a variety of mediums, including conference talks, documentation, written tutorials, social media, videos, live streams, code samples, online forums, and more.
Come chat with Liz and Lauren about their experiences as developer advocates and discover if developer advocacy could be the right next step for your career. They'll reveal the highs and lows of their positions, how they successfully transitioned into these roles, and how they’ve customized their careers to fit their unique strengths and interests.
More Related Content
Similar to Intro to Technical Writing: Creating Content that Google and Readers will Love
6 important guidelines for paper presentation conference 2023 | IFERPIFERP
Consider yourself on a stage in front of a large audience of distinguished academics, researchers, and industry professionals, presenting your most recent research findings at a major international conference. You have spent months preparing, meticulously researching your topic, and putting together a compelling presentation. As you begin to speak, all eyes are on you, and you can feel the weight of their expectations on your shoulders. Visit https://www.iferp.in/blog/2023/02/25/6-important-guidelines-for-paper-presentation-conference-2023/ to know more.
If you are inspired during practical and hands-on sessions during the three days at Devoxx UK 2015, have you thought about how you might pass on this knowledge and experience to others? If so, then we have just the right solution for you! Running a Hackday, either at your workplace or within your local community, can be very rewarding. Come along to this session and learn all about the art of running hack session from Richard Warburton, author of Java 8 Lambda and regular organiser of hackdays in the London Java Community.
You will be able to answer your own questions like: Why you should run a hackday ? What’s involved in running one ? Examples of successful hackdays Tips for being successful
This document discusses best practices for writing documentation. It explains that documentation is important for users to understand how to install and use a project, and for contributors to understand how to contribute. The document outlines different types of documentation including installation instructions, user guides, API references, examples, and tutorials. It also discusses formats like HTML, PDF and interactive help. The document provides examples of well documented projects and gives tips for documentation quality like maintaining examples, writing documentation alongside code, and considering your audience. It recommends tools for documentation and provides guidance on where new users and contributors should start with documentation.
A firm grasp of scientific method and ability to write clearly and convincingly is a great assert to any professional in sciences.
Conducting research and publishing peer reviewed papers train professionals in both scientific method and writing. Moreover, having research papers in your resume is considered a huge plus in both industry and academia. However, conducting research and getting them published requires professionals to approach the problem and present their solutions form a unique angle. The talk will address research in general and writing research papers. Specifically, the talk will cover peer review process, what is a contribution?, and basic composition of
a research paper, describing potential pitfalls.
I've been in the technical writing field for a few years now. This pdf covers the responsibilities of technical writers, research methods, style guides, and best practices in technical writing.
How To Guide : Researching Topics For BlogsOmnePresent
The document provides tips for researching topics for blogs. It recommends creating a research system to organize notes and materials collected from various sources. Specific keywords should be chosen and included in the content to improve SEO. Related search terms on Google can help identify commonly searched phrases. Tools like Twitter and Google+ help gauge reader interest and ensure the topic has ample information available. Qualitative research is necessary to write great blog posts with correct information, statistics, and unique elements like infographics to stand out.
How to deliver the right software (Specification by example)Asier Barrenetxea
Talk about Specification by Example. What's the problems it tries to tackle and how to solve them.
I gave this talk at Thoughtworks on a "lunch and learn" meeting for the company.
This is a new version of my previous presentation about "Specification by example"
https://www.slideshare.net/AsierBarrenetxea1/spec-byexample-v2
Derek Parham gives a talk on how to be an effective tech lead based on his experience leading large engineering teams at Google. He outlines key responsibilities of a tech lead including communicating with different stakeholders, building up the team, and looking for unaddressed problems. Parham emphasizes limiting meetings to protect engineering time, using design reviews to spread knowledge, and delegating tasks to empty one's plate and develop other leaders. He encourages tech leads to teach their engineers, build more tech leads as the team grows, and make team success a higher priority than personal success.
6 Academic Research Paper Writing Tips - 2023.pdfIFERP
Writing an academic research paper frequently necessitates some level of academic research writing experience and prowess. Both aspiring research authors and research authors who have previously struggled with academic writing will find the six tips highlighted in this blog to provide a wealth of information about what steps they can take to make their next research writing endeavor a pleasant one. Visit https://www.iferp.in/blog/2022/08/10/6-tips-for-how-to-write-academic-research-paper/ for more information.
This document provides tips and strategies for college students related to organization, note-taking, studying, and writing papers. It discusses organizing emails and files using technology like Moodle and Google apps. It offers various note-taking methods and strategies for effective studying, such as the Cornell note-taking system and the Cornell 5-day study plan. The document also covers best practices for test-taking, writing strong papers using MLA or APA style, and emailing professors appropriately.
The document discusses growth and development. In a concise yet informative manner, it touches on the natural process of expanding and increasing in size over time through nourishment and care. While brief, it implies the importance of fostering growth through proper support and conditions.
This document provides advice and guidance for writing books related to open source software. It discusses leveraging community involvement to gain recognition, finding inspiration in open source projects, and strategies for working with publishers or self-publishing. The key recommendations are to write daily to build skills and an audience, contribute to open source documentation projects to gain experience and exposure, and understand publishing contracts and self-publishing options.
This document provides guidance on how to write a thesis. It discusses organizing the thesis by including elements like the title page, abstract, table of contents, introduction, literature review, methods, results, discussion, and references. It emphasizes developing a clear structure with an outline and using visual elements like figures and tables to present data. The document also covers writing each section, editing for clarity and flow, attention to style/formatting details, and managing the writing process with planning and regular writing. The overall message is that a well-organized thesis with a logical structure and flow is important to effectively communicate the research.
This presentation is an introduction to the field of technical writing based on my personal journey and philosophy of documentation, and was presented to the first meeting of Write The Docs Nigeria on February 20, 2021.
Similar to Intro to Technical Writing: Creating Content that Google and Readers will Love (20)
The document outlines 7 ways to build an API that developers will hate, including keeping endpoints secret, using offensive language, pushing changes whenever desired without versioning or documentation, inconsistent naming, and ignoring errors and rate limits. It then provides 7 ways to build an API that developers will love, such as making the API discoverable, using inclusive language, versioning, following processes for changes, consistency, clarity on rate limits, and appropriate use of status codes.
Developer Advocacy: A Career Path for Those With a Passion for Code, Communit...Lauren Hayward Schaefer
Chances are good that you’ve interacted with a developer advocate at one point or another. Perhaps you’ve chatted with them at a booth at a conference, read their blog post, or cloned their code sample on GitHub. This session will provide you with a deeper understanding of the role of developer advocacy and its significance in the tech industry.
What is a developer advocate? A developer advocate advocates for two entities at the same time: at their company, they advocate for the developer community, and, in the developer community, they advocate for their company. Developer advocates have a passion for developer experience and reaching developers where they are, through a variety of mediums, including conference talks, documentation, written tutorials, social media, videos, live streams, code samples, online forums, and more.
Come chat with Liz and Lauren about their experiences as developer advocates and discover if developer advocacy could be the right next step for your career. They'll reveal the highs and lows of their positions, how they successfully transitioned into these roles, and how they’ve customized their careers to fit their unique strengths and interests.
10 Best Practices for Writing Documentation (For Those Who Would Rather Do An...Lauren Hayward Schaefer
When I joined my current team, I discovered that writing external documentation was part of my role. While I had experience writing tech blogs, writing documentation felt like an entirely new skill. And I didn't love it.
Chances are good you've written documentation previously or will need to in the future. Perhaps you’re writing official documentation for your users or something more informal, like internal documentation for your teammates or a GitHub readme.
In this session, I’ll share ten best practices for writing documentation. You’ll leave with the knowledge you need to successfully write documentation your readers will enjoy, and you’ll possibly even be excited about the prospect of doing so.
We commonly think about leveling up our technical careers by exploring new technology, learning best practices, or finding a mentor. But we don’t always think about the power of the written word.
In this keynote full of personal stories and practical advice, Lauren will explain how you can use writing to level up your technical career. She’ll provide you with concrete strategies for how to write internally at your company as well as externally in the wider tech community. Then she’ll share steps you can take to improve the quality of your writing.
You’ll leave this keynote energized and ready to level up your career by writing.
The first page of this worksheet will help you identify what your profile is and how you want your profile to evolve. The second page of this worksheet helps you make a plan for raising your profile.
Recording of talk associated with this worksheet: https://www.youtube.com/watch?v=Z3tgvOZdinM&feature=youtu.be
Slides associated with this worksheet: https://www.slideshare.net/LaurenHaywardSchaefe/how-to-raise-your-profile-as-a-developer-and-why-you-should-bother
If you've ever found yourself questioning how to apply data modeling best practices to your projects, you're not going to want to miss this session.
Lauren Schaefer recently worked with Maxime Beugnet and Mark Smith to rapidly build an app. The app retrieves daily stats about YouTube videos and visualizes the data in a dashboard. In their two-week sprint to get a working MVP, they did their best to model the data, but they didn't get it all right the first time.
In this stream, Lauren will share five things she learned while modeling data for this app. You'll leave with practical data modeling tips you can apply to your next project that uses MongoDB.
This session is based on https://www.mongodb.com/developer/article/7-things-learned-while-modeling-data-youtube-stats/
How to Raise Your Profile as a Developer (And Why You Should Bother!)Lauren Hayward Schaefer
We like to think the tech industry is a meritocracy: if you put your head down and do your work well, you will be recognized. Unfortunately, this is not typically the case. In order to advance your career, you will likely need to raise your profile internally at your company and/or externally in the broader developer community. During this session, Lauren Schaefer will share personal stories of how she has worked to overcome the discomfort of raising her profile. You'll leave this session with practical steps you can take in the coming weeks and months to raise your profile.
This document discusses building continuous integration and continuous delivery (CI/CD) pipelines for MongoDB Realm apps. It begins by defining CI/CD and explaining the benefits, such as faster releases, smaller releases, and fewer manual tasks. It then provides an overview of the key components in a sample CI/CD pipeline for a Realm app, including development, staging, and production environments. The document concludes by recommending resources for setting up a CI/CD pipeline, such as using GitHub, MongoDB Developer Hub, Realm documentation, and the MongoDB community.
Did you grow up on relational databases? Are document-based databases a bit of a mystery to you? If so, you don't want to miss this meetup! We’ll compare terms and concepts, explain the benefits of document-based databases, and walk through the 3 key ways you need to change your mindset to successfully use document-based databases.
When you need to model data, is your first instinct to start breaking it down into rows and columns? When you want to develop apps in a modern, agile way, NoSQL databases can be the best option.
As a startup, you're probably interested in spending more time on shipping features than managing your database.
We will discuss:
- What is NoSQL?
- How terms and concepts in MongoDB relate to those in relational databases
- The benefits of MongoDB for startups
- The 3 key ways you need to change your mindset to successfully use MongoDB for your startup
and more!
https://mongodbcom.website.prod.corp.mongodb.com/webinar/why-use-no-sql-for-startups
Want to learn the fundamentals of document databases and why they have become the widely used alternative to traditional relational databases? If so, you don’t want to miss this webinar!
In Back to Basics, we’ll introduce you to the foundational concepts of the world’s most popular NoSQL database, MongoDB, and explain how you can leverage the MongoDB Cloud to build modern, data-driven applications.
Agenda includes:
- A brief overview of how data is stored in MongoDB vs relational databases
- A live demo of MongoDB Atlas, a fully managed multi-cloud database service
- Tips and tricks you should know to get the best out of MongoDB
Serverless application development is fabulous…but if you don’t have a CI/CD pipeline with a strong foundation of test automation, you’ll likely fail.
In this session, MongoDB Developer Advocate Lauren Schaefer will walk you through the process of crafting test automation and DevOps pipelines for serverless apps that are built on MongoDB Realm. Then, she’ll jump into the always-terrifying-for-the-presenter live demo so you can see how this all works in a very practical way. She’ll make some changes to her codebase, update her automated tests, and push her code changes. You’ll watch as the various pieces of the pipeline fail and (hopefully) succeed.
You’ll walk away from this session equipped to build test automation and DevOps pipelines for your serverless apps.
As Daniel Tiger wisely sings, "It's OK to make mistakes. Try to fix them, and learn from them too."
Come learn common mistakes developers make as they model their data in document databases. You'll leave this session ready to spot and correct common document database schema design anti-patterns.
A presentation for the MongoDB WICS Summit.
If you're comfortable with relational databases but not so comfortable with document databases like MongoDB, this is the session for you! We'll walk through an example of how you would store the same data in both a relational database and a document database. Then we'll discuss how common relational database terms and concepts map to terms in document databases. You'll leave feeling comfortable with the basics of how to store data in document databases.
The document describes Lauren Schaefer's presentation on changing from a relational database mindset to a document database mindset using MongoDB. It provides an example of mapping user data from tables to embedded documents, showing how additional user details like hobbies and job history can be embedded within a user document rather than stored across multiple tables. The presentation aims to help developers understand the key differences between relational and document databases.
Shakespeare knew what he was talking about when he wrote "Some are born great remote workers, some achieve great remote work, and some have great remote work thrust upon them." Ok, maybe that's not exactly what he wrote. Whether you love working remotely or you were voluntold to work remotely, this is the session for you. Come discover tips and tricks to being a successful remote employee from a ten-year remote work veteran.
https://home.yougotthis.io/
Serverless application development is fabulous…but, if you can’t automate your delivery pipeline, you’ll likely fail.
In this session, MongoDB Developer Advocate Lauren Schaefer will walk you through the process of crafting test automation and DevOps pipelines for serverless apps that are built on the MongoDB Data Platform. Then, she’ll jump in to the always-terrifying-for-the-presenter live demo so you can see how this all works in a very practical way. She’ll make some changes to her code base, update her automated tests, and push her code changes. You’ll watch as the various pieces of the pipeline fail and (hopefully) succeed.
If you’re a DevOps engineer or a developer responsible for creating your own Continuous Integration/Continuous Delivery automation, you won’t want to miss this talk! You’ll walk away from this session equipped to build DevOps pipelines for your serverless apps.
Register for the webinar at https://www.mongodb.com/webinar/devops-with-mongodb-serverless
Does NoSQL feel like a bunch of NoSense to you? If so, you don’t want to miss this webinar!
In Back to Basics, we’ll teach you the fundamentals of the world’s most popular NoSQL database, MongoDB.
We'll start with a brief overview of how data is stored in MongoDB and compare that to the legacy table-based (relational) structure you may be used to. After that, we will dive deep into a demo! The demo will include:
- How to create a MongoDB database using MongoDB Atlas (for free!)
- A walk through the basic CRUD (create, read, update, and delete) operations
- Some tips and tricks for better efficiency/productivity
After this webinar, you'll be able to confidently use MongoDB to build your next app.
Does NoSQL feel like a bunch of NoSense to you? If so, you don’t want to miss this workshop! We’ll walk you through the basics of how to use the open database MongoDB.
We’ll begin with an overview of how data is stored in MongoDB and compare that to the table-based (relational) structure you may be used to. Then we’ll get hands-on! You’ll create a database and learn how to perform the basic CRUD (create, read, update, and delete) operations. Then you’ll load a large dataset into your database so you can see how to explore it and understand what schemaless data really looks like. We’ll wrap up with some tips and tricks, so you will leave the workshop feeling confident you’re ready to use MongoDB when you build your next app!
When you need to model data, is your first instinct to start breaking it down into rows and columns? Mine used to be too. When you want to develop apps in a modern, agile way, NoSQL databases can be the best option. Come to this talk to learn how to take advantage of all that NoSQL databases have to offer and discover the benefits of changing your mindset from the legacy, tabular way of modeling data. We’ll compare and contrast the terms and concepts in SQL databases and MongoDB, explain the benefits of using MongoDB compared to SQL databases, and walk through data modeling basics so you feel confident as you begin using MongoDB.
Jill Pizzola's Tenure as Senior Talent Acquisition Partner at THOMSON REUTERS...dsnow9802
Jill Pizzola's tenure as Senior Talent Acquisition Partner at THOMSON REUTERS in Marlton, New Jersey, from 2018 to 2023, was marked by innovation and excellence.
5 Common Mistakes to Avoid During the Job Application Process.pdfAlliance Jobs
The journey toward landing your dream job can be both exhilarating and nerve-wracking. As you navigate through the intricate web of job applications, interviews, and follow-ups, it’s crucial to steer clear of common pitfalls that could hinder your chances. Let’s delve into some of the most frequent mistakes applicants make during the job application process and explore how you can sidestep them. Plus, we’ll highlight how Alliance Job Search can enhance your local job hunt.
A Guide to a Winning Interview June 2024Bruce Bennett
This webinar is an in-depth review of the interview process. Preparation is a key element to acing an interview. Learn the best approaches from the initial phone screen to the face-to-face meeting with the hiring manager. You will hear great answers to several standard questions, including the dreaded “Tell Me About Yourself”.
Job Finding Apps Everything You Need to Know in 2024SnapJob
SnapJob is revolutionizing the way people connect with work opportunities and find talented professionals for their projects. Find your dream job with ease using the best job finding apps. Discover top-rated apps that connect you with employers, provide personalized job recommendations, and streamline the application process. Explore features, ratings, and reviews to find the app that suits your needs and helps you land your next opportunity.
4. Benefits of
Writing
- Become known as an expert on a
topic
- Demonstrate scope (promotion at
your current company)
- Get your name out for future roles
- Reinforce your learning
- Traffic is measurable
- Content lives on for years
✍
5. Meet Megan ● Las Vegas, NV, USA
● Developer Relations @ MongoDB
● Writing and editing for ~13 years
● Hobbies: Fostering dogs, reading,
writing, lifting weights, being
outside
● https://www.mongodb.com/dev
eloper
6. Meet Lauren ● Pennsylvania, USA
● Career
○ Software engineer at IBM
○ Developer advocate at SugarCRM
○ Developer advocate at MongoDB
○ Developer advocate at Grammarly
● Love traveling, doing jigsaw
puzzles, reading light fiction, and
hanging with my husband and
daughter
● https://linktr.ee/lauren_schaefer
15. How to Brainstorm
Topics 🧠⛈
● What do you enjoy?
● What do you know a lot about?
● What is something you want to
learn?
● What is something you failed at
or messed up?
● What is something that surprised
you?
● What is going on in pop culture
that you can tie to technology?
● Consider technical topics as well
as soft skills
Think about you
16. How to Brainstorm
Topics 🧠⛈ ● Who are they?
● What do they already know?
● What topics are hot right now?
Think about your audience
17. How to Brainstorm
Topics 🧠⛈
● Answer the Public
● Ubersuggest
● Google
● Auto-complete
○ People also ask
○ Related searches
○ People also search for
Tools you can use
18.
19. Time to Brainstorm Topics 🧠⛈
In this workshop, youʼre going to create a blog post
from start to finish! Write down every topic that
comes to mind, so you will have a list for future
content.
● Whatʼs something you already know a lot
about?
● Whatʼs something that wonʼt require you to
write a lot of code?
● Whatʼs something you will be allowed to
publish tomorrow (without your companyʼs
approval process)?
● Consider articles (e.g., best practices,
thought leadership, soft skills) and tutorials
Individual brainstorming (20 min)
Partner brainstorming (20 min)
20. Agenda
● Selecting Your Topic
● Selecting Your Keyword
● Researching Your Topic and
Making an Outline
● Writing Your Content
● Wrap-up
Day 1
23. Keywords
What to look for 👀
● High-traffic, low-competition
keywords
● At least 1,000 searches a month
24. Keywords
Tools you can use 🛠
● SEMrush (free)
○ Keyword Magic Tool
● Ubersuggest (free with limited
access)
● Keywords Everywhere (lowest
tier is $10 and it goes a long way)
25. Keywords
● Determine what the user is trying
to learn when they search for
your topic
● Search your keyword incognito
and look at the top three results
Determine user intent 🤔
(a.k.a. search intent)
26. Pick Your Keyword
Take 15 minutes to:
● Make a list of possible keywords.
● Use one of the tools we discussed to identify the best keyword for your topic.
● Determine user intent for that keyword.
27. Agenda
● Selecting Your Topic
● Selecting Your Keyword
● Researching Your Topic and
Making an Outline
● Writing Your Content
● Wrap-up
Day 1
28. Research &
Build 🧱
This is the fun part!
● Research your topic
● Take notes–especially things that
surprise you or trip you up
● Write your code–all of it
30. Create an
Outline
● Identify your key points
● Hint: Look at what content is
already ranking
● Outline your entire series
Donʼt skip this!
31. Sample Outline
Topic: data lake // Keyword: data lake architecture
● Introduction
○ Tell the reader what theyʼre about to learn.
● What are data lakes?
○ Supporting point #1
○ Supporting point #2
○ ...
● The benefits of data lakes
○ Supporting point #1
○ Supporting point #2
○ ...
● What does data lake architecture look like?
○ Supporting point #1
○ Supporting point #2
○ ...
● Conclusion
○ Recap what the reader learned.
32. Get to Work! ✍
You have the next hour (ish) to:
● Research
● Build any code (if applicable)
● Write your outline
35. Stop and Get Feedback 🛑
Share your outline with a partner! (~30 min)
As your partner shares, consider:
● Are they covering the main pieces of the topic?
● What other questions do you have about the topic?
● Are they addressing any common objections?
● Is the flow logical?
If you have time, do a code review.
36. Agenda
● Selecting Your Topic
● Selecting Your Keyword
● Researching Your Topic and
Making an Outline
● Writing Your Content
● Wrap-up
Day 1
38. Writing Your
Content
Get in the zone
● Block your calendar
● Silence notifications
● Write the first draft in one sitting
39. Writing Your
Content
● Identify your audience
● Provide as much value as
possible, including links to learn
more
● Use inclusive language
○ Google Developer Documentation
Style Guide
○ Grammarly Premium
● Make it skimmable
○ Turn your outline points into headers
○ Write in short paragraphs
○ Break up the text
○ Example
Best practices 🏆
40. Writing Your
Content
● Strong introduction
○ Start with a hook
○ Identify the audience
○ Tell readers what theyʼll learn
● Conclusion that recaps the key
points
● Call to action (CTA)
What to include 📝
41. Writing Your
Content
● Optimize your title
○ Sharethrough Headline Analyzer
● Donʼt plagiarize anyone, including
yourself
○ Grammarly plagiarism checker (free)
● Use your keyword in the :
○ URL
○ Title (as close to the beginning as
possible)
○ Introduction
○ At least one H2
○ Sprinkled throughout the post
● Optimize your URL
○ Use the title as your URL
○ Make all words lowercase
○ Convert spaces to dashes
○ Remove stop words
SEO best practices 🔍
42. “Data Lakes vs Data Warehouses: What’s
the Difference and Why Do We Care?”
mongodb.com/blog/data-lakes-vs-data-warehouses
43. Get to Work on Your First Draft! ✍
Use your outline to write your first draft. Tomorrow you will share your draft with a
partner, so we recommend using Google Docs.
Ask Lauren for a Grammarly Premium free trial code if youʼd like one.
You have until about 4:50 p.m.
44. Agenda
● Selecting Your Topic
● Selecting Your Keyword
● Researching Your Topic and
Making an Outline
● Writing Your Content
● Wrap-up
Day 1
45. What We
Covered Today
● Selecting Your Topic
● Selecting Your Keyword
● Researching Your Topic and
Making an Outline
● Writing Your Content
Wow!
54. Self Review
Donʼt skip this one!
● Wait at least a day after your first
draft
● Use a tool like Grammarly or
Hemingway App
● Eliminate fluff
● Get your post into the best
possible shape before requesting
a review from someone else
55. Self Review
Checklist ✅
❏ I have tried the steps from top to
bottom in a new environment
❏ All images have alternate text and
(optionally) captions
❏ The post contains all relevant
links
❏ The post lists any prerequisites
❏ The post includes a call to action
56. Review Your Work 👀
Use the checklist below to review your work (~45 minutes).
❏ I have tried the steps from top to bottom in a new environment (if applicable)
❏ All images have alternate text and (optionally) captions
❏ The post contains all relevant links
❏ The post lists any prerequisites
❏ The post includes a call to action
57. Technical
Review
Checklist ✅
❏ I have tried the steps in the post
from top to bottom in a new
environment
❏ The code is idiomatic to the
programming language, follows
best practices, and is easy to follow
❏ The post uses technical terms
correctly
❏ The post is complete and easy to
understand
❏ The post contains all relevant links
❏ The post lists any prerequisites
58. Copy Review
Checklist ✅
❏ The post is grammatically correct
❏ The post is engaging and easy to
follow
❏ The post uses inclusive language
❏ All images have alternate text and
(optionally) captions
❏ The post includes a call to action
59. Tips
💡
● Your name will be on the post, so
you are the decision-maker
● Donʼt get too many reviews
● Give reviewers a deadline
● Be kind in your reviews
60. Review Your Partner’s Work
Technical Review
❏ I have tried the steps in the post from top
to bottom in a new environment
❏ The code is idiomatic to the programming
language, follows best practices, and is
easy to follow
❏ The post uses technical terms correctly
❏ The post is complete and easy to
understand
❏ The post contains all relevant links
❏ The post lists any prerequisites
Take about 45 minutes to review your partnerʼs work. Do your best to act as both the
technical reviewer and the copy reviewer. Remember to be kind and say what you like.
Copy Review
❏ The post is grammatically correct
❏ The post is engaging and easy to follow
❏ The post uses inclusive language
❏ All images have alternate text and
(optionally) captions
❏ The post includes a call to action
64. It’s time to publish! 📰
Pick a site and publish your work. Share your URL in Slack once your work is live. If you
have a Twitter handle, include that in your Slack message. (~1 hour)
68. Promote 📣
Especially in the first 48 hours
● Tweet
○ Once a day for 3 days
○ Tag any relevant pages mentioned in
your blog, like @nodejs or @java
● LinkedIn
○ Pick 3-5 hashtags based on the topic,
like #Tech, #MongoDB, #Java, #SwiftUI,
or #Nodejs
○ Tag any relevant pages, like @nodejs.
● TikTok
○ Make a video about your content
● Instagram
○ Share in a post, story, or reel
● Company Slack or Teams
○ Share the link to your post and your
Twitter handle
74. How Can You Promote & Repurpose Your Post? ♻
● Brainstorm ways you can promote and repurpose your content. Start drafting as time allows. (15
minutes)
● Share your ideas with a partner. (20 minutes) Consider:
○ What other ways can your partner promote or repurpose their content?
○ How can they improve what theyʼve drafted?
● Promote and start repurposing your content. (15 minutes)
○ Share links to your social media posts in the Slack channel, so we can amplify them!
78. You did it! 🎉
Consistent publication leads to:
● Larger scope and influence
● Becoming known as the expert
● More traffic
● Improved Google rankings
(Donʼt stop here!)