We are a remote-first company. This is how we make sure our team can effectively work together to create the last marketing and analytics tool you will ever need!
The flow is what makes a programmer thrive or fail. How many interruptions did you have today? Can you stop them?
Interruptions turn each day into chunks of productivity. Each interruption costs a programmer at least 10 minutes, plus the time spent during the interruption.
Here are some tips to avoid interruptions and get to a flow state of mind. Kill interruptions before they kill your productivity.
When was the last time that you programmed without any interruptions?
Some of the tips:
1. Keep your email clients closed
2. Keep Twitter closed
3. Keep Facebook closed
4. Start tracking time spent on every project
5. Unplug your phone
6. Silence your cell phone
7. Use Slack
Manage your interruptions before they manage your productivity.
Marta Turek: Too Busy to do Good Work- MozCon 2015Erica Lewis
The document discusses strategies for improving productivity and reducing distractions at work. It recommends making small, specific changes to daily habits over 21 days to develop new habits. Some strategies include blocking out uninterrupted work time, avoiding unnecessary meetings, planning work activities, organizing information, standardizing processes, and continuously learning new skills. The overall message is that small, incremental improvements can help maximize productivity and minimize wasted time at work.
To compete effectively in a marketing environment that is changing at an unprecedented rate, we need to do meaningful work and update our skills as the marketing skills gap widens.
5 tricks to know before you outsource your drupal projectEbizon
Take time to thoroughly document project requirements to avoid misunderstandings. Encourage offshore developers to ask questions to gain a clear understanding of the project. Define communication methods and frequency, such as weekly calls, to ensure the project stays on track. Conduct regular reviews of deliverables and provide feedback to minimize mistakes. Require daily status reports from developers on tasks completed, time spent, and any clarifications needed to maintain transparency.
5 Essential Tips For Improving Your Website Mockups & Prototypes!Usersnap
Have you ever received feedback on new website mockups or prototypes starting with “Which language is that? I don’t understand “lorem ipsum!!”?
Well, yes? Then you’ve been there. And it isn’t really a great feeling. Not because of the question itself.
In this post we are going to show you 5 tips on how to prevent yourself from receiving such feedback and how to make your website mockups even better.
Matt Hubbard, FullContact - Denver Startup Week 2016
Product Management is a nebulous and challenging career path, but Product Management at a startup comes with a host of additional demands. How do you stay focused on your customers, features, and roadmap when you are helping out with Project Management, Design, Marketing, Customer Support, and other related functions? How do you employ cheap or free tools to achieve the same results as larger companies with big budgets for user testing, design, and marketing? How do you negotiate with passionate founders who are still learning to let go of the product vision and roadmap? During this session, we’ll show you how.
How To Be An Emergency Response Technician (ERT)Chris Fullman
For many small companies, the added need for an IT or “Swiss Army Knife” employee (aka “Emergency Response Technician” or “ERT”) often falls on one person who has their own work to perform. In this presentation, AgencyNet’s Senior Producer (and ERT) Chris Fullman will offer valuable tips and philosophies to improve the productivity, prioritization and sanity of that often-overwhelmed individual. This presentation was originally given at SXSW Interactive 2010 and revised for Refresh Lauderdale's April 2010 meet-up.
The flow is what makes a programmer thrive or fail. How many interruptions did you have today? Can you stop them?
Interruptions turn each day into chunks of productivity. Each interruption costs a programmer at least 10 minutes, plus the time spent during the interruption.
Here are some tips to avoid interruptions and get to a flow state of mind. Kill interruptions before they kill your productivity.
When was the last time that you programmed without any interruptions?
Some of the tips:
1. Keep your email clients closed
2. Keep Twitter closed
3. Keep Facebook closed
4. Start tracking time spent on every project
5. Unplug your phone
6. Silence your cell phone
7. Use Slack
Manage your interruptions before they manage your productivity.
Marta Turek: Too Busy to do Good Work- MozCon 2015Erica Lewis
The document discusses strategies for improving productivity and reducing distractions at work. It recommends making small, specific changes to daily habits over 21 days to develop new habits. Some strategies include blocking out uninterrupted work time, avoiding unnecessary meetings, planning work activities, organizing information, standardizing processes, and continuously learning new skills. The overall message is that small, incremental improvements can help maximize productivity and minimize wasted time at work.
To compete effectively in a marketing environment that is changing at an unprecedented rate, we need to do meaningful work and update our skills as the marketing skills gap widens.
5 tricks to know before you outsource your drupal projectEbizon
Take time to thoroughly document project requirements to avoid misunderstandings. Encourage offshore developers to ask questions to gain a clear understanding of the project. Define communication methods and frequency, such as weekly calls, to ensure the project stays on track. Conduct regular reviews of deliverables and provide feedback to minimize mistakes. Require daily status reports from developers on tasks completed, time spent, and any clarifications needed to maintain transparency.
5 Essential Tips For Improving Your Website Mockups & Prototypes!Usersnap
Have you ever received feedback on new website mockups or prototypes starting with “Which language is that? I don’t understand “lorem ipsum!!”?
Well, yes? Then you’ve been there. And it isn’t really a great feeling. Not because of the question itself.
In this post we are going to show you 5 tips on how to prevent yourself from receiving such feedback and how to make your website mockups even better.
Matt Hubbard, FullContact - Denver Startup Week 2016
Product Management is a nebulous and challenging career path, but Product Management at a startup comes with a host of additional demands. How do you stay focused on your customers, features, and roadmap when you are helping out with Project Management, Design, Marketing, Customer Support, and other related functions? How do you employ cheap or free tools to achieve the same results as larger companies with big budgets for user testing, design, and marketing? How do you negotiate with passionate founders who are still learning to let go of the product vision and roadmap? During this session, we’ll show you how.
How To Be An Emergency Response Technician (ERT)Chris Fullman
For many small companies, the added need for an IT or “Swiss Army Knife” employee (aka “Emergency Response Technician” or “ERT”) often falls on one person who has their own work to perform. In this presentation, AgencyNet’s Senior Producer (and ERT) Chris Fullman will offer valuable tips and philosophies to improve the productivity, prioritization and sanity of that often-overwhelmed individual. This presentation was originally given at SXSW Interactive 2010 and revised for Refresh Lauderdale's April 2010 meet-up.
The document provides tips for running effective remote meetings and participating in remote video calls. Some key tips include being intentional about communication when nonverbal cues are lacking, ensuring all participants have a chance to engage, and agreeing on technical protocols in advance. It also recommends muting by default for large meetings and keeping video on.
10 Things To Drive Your Scrum Master CrazyMarc Löffler
This document lists 10 things that can frustrate a ScrumMaster, including doing tasks outside the sprint backlog, hiding impediments, not communicating with the product owner during sprints, ignoring definitions of done, claiming to have nothing to do when the sprint backlog is not complete, last minute preparation for sprint reviews, not splitting large tasks, chronic tardiness, constantly asking what task to do next, and disrupting scrum meetings. The document is authored by Marc Löffler, a certified scrum professional and agile coach.
Dnepr IT PM Club #9
Speaker - Artem Fursenko [PM at Sitecore]
https://www.linkedin.com/in/artemfursenko/
Тема: "Sayless. Less is more в проектной коммуникации"
"Расскажу как не смотря на проблему информационной перегрузки в современном мире, зацепить внимание нужных людей в нужный момент и быть эффективным в деловой коммуникации. Также, приведу примеры рабочей переписки с техническими коллегами, с заказчиками и т.п."
Об Артеме:
Team Manager, Cloud Operations в Sitecore. 7 лет опыта в IT, последние 3 в менеджменте.
Опыт:
- Product Support команда поддержки и консалтинга разработчиков на платформе
- Cloud Operations, delivery облачных сервисов 24x7. Работа с разработкой, продажами и поддержкой.
Keep internal communications brief, concise, and relevant to the audience. Include visuals to engage employees and remember different communication preferences exist based on employee roles and mobile usage. Regular communication is important, especially during outages or changes, but not all employees can be reached so reserve critical channels. Measure the success of messages and seek employee feedback to improve engagement over time.
A new Alexa skill is quickly built and certified at Amazon. Depending on its complexity, this process can be completed in a few weeks. The same applies to Google Actions. But some people put their hands in their laps afterwards and wonder why their new, innovative voice application does not go through the roof. History repeats itself: 25 years ago, with the advent of the World Wide Web, many HTML projects were published whose content was not updated for a long time. Today nobody would launch a website or a smartphone app and then leave it to itself. Why should it be different with an Alexa skill, a Google Action or a Bixby capsule? In this session you will learn about strategies and solutions to make your voice application up-to-date, interactive and interesting. Use the existing tools of the providers and make sure that your content can easily be kept up-to-date. We will also look at the insights and modernization measures from the three-year operation of one of the first German-speaking Alexa Skills.
This document provides 20 tips for hosts to have a successful online meeting using the Ezymeetz platform. The tips include sending meeting invitations in advance, uploading and testing any presentations beforehand, minimizing distractions and ambient noise, presenting an agenda, engaging participants through questions and feedback, and summarizing conclusions. Ezymeetz is described as a secure online environment for meetings and webinars that provides user guides and customer support.
Presentation by Mike Rylander at Code4Lib 2007 in Athens, GA.
At PINES we have the luxury of a very supportive administrative team. Through trial and error over the last three years we have had the chance to glean a set of do's and don'ts for the building of a successful in-house development team and environment. We would like to share our experience in the hope that others may be able to duplicate our successes and avoid our missteps at all levels, from developers on up to management.
This document provides 7 secrets to nailing a video job interview in the 3D printing industry. The secrets include: being familiar with the video technology beforehand and doing a test run; approaching the video call like a director by ensuring proper lighting, camera angle, and maintaining positive body language; maintaining eye contact with the camera; speaking slowly and clearly; avoiding fidgeting; being careful when screen sharing; and avoiding too much body motion. The goal is to appear as professional as possible on video by addressing technical aspects and body language.
The document discusses issues facing libraries and proposes strategies for addressing them. It focuses on the problems with current library software and promotes adopting the open source library system Evergreen as a solution. The summary promotes Evergreen by focusing on its cost-effectiveness and support model while addressing common concerns directors have about open source software.
Challenges employees face while Remote Working Xoxoday
This summary provides the key points from the document in 3 sentences:
The document discusses challenges that employees may face while working remotely such as lack of resources, maintaining motivation, work-life balance, isolation, communication issues, and maintaining productivity. It provides tips on how to tackle each challenge like using alternative tools to office resources, creating a dedicated work space, over-communicating, and setting boundaries between work and personal life. The document also offers 8 ideas for making the best use of time gained such as taking online courses, focusing on well-being, reconnecting with others, and future planning.
How to Make Working From Home More ProductiveSpringworks
Are you wondering how to stay productive when you work from home and surrounded by distractions? Here are 7 practical ways to make working from home more productive.
5 practical tips to leverage the power of simplicityLisa Jansen
Many of the greatest business leaders of our time are big advocates of simplicity. But, simplicity is everything but simple. In today’s super-connected and super-informed world simplicity has become rare and an after thought. But there are a few 'simple' things you can do to leverage the power of simplicity in your business and live.
This document discusses various productivity technologies that can help get work done more efficiently. It describes tools for information management like scanner apps and RSS feeds, as well as tools for streamlined communication like screen capture and mass texting apps. Task management apps are also covered, such as those for tracking individual and team tasks, setting reminders, and getting unstuck creatively. The overall message is that these technologies can help repair productivity systems and reduce waste and clutter.
This document outlines the pre-production planning for a project including props and locations needed, contingency planning for potential issues, health and safety considerations, and a proposed 8-day schedule. Props needed include a laptop, computer, and Photoshop. Potential locations are a house and college. Contingency plans address issues such as computer crashes, distractions, and files not saving. Health and safety risks addressed are tripping, hand cramps, overheating, and hitting knees. The schedule spans 8 days for initial plans, research, production experiments, a proposal, pre-production, the final product, and a product reflection.
The document provides tips for effectively using PowerPoint in presentations. It recommends using PowerPoint to illustrate main points, using sparse slides with limited text and visuals, and rehearsing presentations. Slides should highlight speech content but not replace it, and presentations should engage audiences rather than just moving from slide to slide. The goal is to focus audiences on the speaker rather than the slides. It also provides classroom-specific tips like keeping designs simple, using contrast, and limiting effects.
Mistakes I Have Made: Collected Project Management FailuresAmye Scavarda
The document summarizes mistakes and failures that the author, Amye Scavarda, a project manager, has experienced in her career in project management. It discusses how project management can be difficult due to managing teams, clients, services, and alignment, as well as having to make hard decisions. The author then categorizes the types of mistakes made as frequent, occasional, every once in awhile, and once. Examples are provided for some of the categories, such as frequent mistakes including estimating errors and juggling teams.
So with all that is going on, we have put together a guide for help with remote work. Including communication tools, productivity hacks, forming habits, video, and marketing tips.
Webinar on how to work remotely in construction with a focus on office staff and leadership. Register for the webinar here to watch it on demand: https://zoom.us/webinar/register/WN_0MVokf0LQKKZrT5hQAAW_A
The document provides tips for running effective remote meetings and participating in remote video calls. Some key tips include being intentional about communication when nonverbal cues are lacking, ensuring all participants have a chance to engage, and agreeing on technical protocols in advance. It also recommends muting by default for large meetings and keeping video on.
10 Things To Drive Your Scrum Master CrazyMarc Löffler
This document lists 10 things that can frustrate a ScrumMaster, including doing tasks outside the sprint backlog, hiding impediments, not communicating with the product owner during sprints, ignoring definitions of done, claiming to have nothing to do when the sprint backlog is not complete, last minute preparation for sprint reviews, not splitting large tasks, chronic tardiness, constantly asking what task to do next, and disrupting scrum meetings. The document is authored by Marc Löffler, a certified scrum professional and agile coach.
Dnepr IT PM Club #9
Speaker - Artem Fursenko [PM at Sitecore]
https://www.linkedin.com/in/artemfursenko/
Тема: "Sayless. Less is more в проектной коммуникации"
"Расскажу как не смотря на проблему информационной перегрузки в современном мире, зацепить внимание нужных людей в нужный момент и быть эффективным в деловой коммуникации. Также, приведу примеры рабочей переписки с техническими коллегами, с заказчиками и т.п."
Об Артеме:
Team Manager, Cloud Operations в Sitecore. 7 лет опыта в IT, последние 3 в менеджменте.
Опыт:
- Product Support команда поддержки и консалтинга разработчиков на платформе
- Cloud Operations, delivery облачных сервисов 24x7. Работа с разработкой, продажами и поддержкой.
Keep internal communications brief, concise, and relevant to the audience. Include visuals to engage employees and remember different communication preferences exist based on employee roles and mobile usage. Regular communication is important, especially during outages or changes, but not all employees can be reached so reserve critical channels. Measure the success of messages and seek employee feedback to improve engagement over time.
A new Alexa skill is quickly built and certified at Amazon. Depending on its complexity, this process can be completed in a few weeks. The same applies to Google Actions. But some people put their hands in their laps afterwards and wonder why their new, innovative voice application does not go through the roof. History repeats itself: 25 years ago, with the advent of the World Wide Web, many HTML projects were published whose content was not updated for a long time. Today nobody would launch a website or a smartphone app and then leave it to itself. Why should it be different with an Alexa skill, a Google Action or a Bixby capsule? In this session you will learn about strategies and solutions to make your voice application up-to-date, interactive and interesting. Use the existing tools of the providers and make sure that your content can easily be kept up-to-date. We will also look at the insights and modernization measures from the three-year operation of one of the first German-speaking Alexa Skills.
This document provides 20 tips for hosts to have a successful online meeting using the Ezymeetz platform. The tips include sending meeting invitations in advance, uploading and testing any presentations beforehand, minimizing distractions and ambient noise, presenting an agenda, engaging participants through questions and feedback, and summarizing conclusions. Ezymeetz is described as a secure online environment for meetings and webinars that provides user guides and customer support.
Presentation by Mike Rylander at Code4Lib 2007 in Athens, GA.
At PINES we have the luxury of a very supportive administrative team. Through trial and error over the last three years we have had the chance to glean a set of do's and don'ts for the building of a successful in-house development team and environment. We would like to share our experience in the hope that others may be able to duplicate our successes and avoid our missteps at all levels, from developers on up to management.
This document provides 7 secrets to nailing a video job interview in the 3D printing industry. The secrets include: being familiar with the video technology beforehand and doing a test run; approaching the video call like a director by ensuring proper lighting, camera angle, and maintaining positive body language; maintaining eye contact with the camera; speaking slowly and clearly; avoiding fidgeting; being careful when screen sharing; and avoiding too much body motion. The goal is to appear as professional as possible on video by addressing technical aspects and body language.
The document discusses issues facing libraries and proposes strategies for addressing them. It focuses on the problems with current library software and promotes adopting the open source library system Evergreen as a solution. The summary promotes Evergreen by focusing on its cost-effectiveness and support model while addressing common concerns directors have about open source software.
Challenges employees face while Remote Working Xoxoday
This summary provides the key points from the document in 3 sentences:
The document discusses challenges that employees may face while working remotely such as lack of resources, maintaining motivation, work-life balance, isolation, communication issues, and maintaining productivity. It provides tips on how to tackle each challenge like using alternative tools to office resources, creating a dedicated work space, over-communicating, and setting boundaries between work and personal life. The document also offers 8 ideas for making the best use of time gained such as taking online courses, focusing on well-being, reconnecting with others, and future planning.
How to Make Working From Home More ProductiveSpringworks
Are you wondering how to stay productive when you work from home and surrounded by distractions? Here are 7 practical ways to make working from home more productive.
5 practical tips to leverage the power of simplicityLisa Jansen
Many of the greatest business leaders of our time are big advocates of simplicity. But, simplicity is everything but simple. In today’s super-connected and super-informed world simplicity has become rare and an after thought. But there are a few 'simple' things you can do to leverage the power of simplicity in your business and live.
This document discusses various productivity technologies that can help get work done more efficiently. It describes tools for information management like scanner apps and RSS feeds, as well as tools for streamlined communication like screen capture and mass texting apps. Task management apps are also covered, such as those for tracking individual and team tasks, setting reminders, and getting unstuck creatively. The overall message is that these technologies can help repair productivity systems and reduce waste and clutter.
This document outlines the pre-production planning for a project including props and locations needed, contingency planning for potential issues, health and safety considerations, and a proposed 8-day schedule. Props needed include a laptop, computer, and Photoshop. Potential locations are a house and college. Contingency plans address issues such as computer crashes, distractions, and files not saving. Health and safety risks addressed are tripping, hand cramps, overheating, and hitting knees. The schedule spans 8 days for initial plans, research, production experiments, a proposal, pre-production, the final product, and a product reflection.
The document provides tips for effectively using PowerPoint in presentations. It recommends using PowerPoint to illustrate main points, using sparse slides with limited text and visuals, and rehearsing presentations. Slides should highlight speech content but not replace it, and presentations should engage audiences rather than just moving from slide to slide. The goal is to focus audiences on the speaker rather than the slides. It also provides classroom-specific tips like keeping designs simple, using contrast, and limiting effects.
Mistakes I Have Made: Collected Project Management FailuresAmye Scavarda
The document summarizes mistakes and failures that the author, Amye Scavarda, a project manager, has experienced in her career in project management. It discusses how project management can be difficult due to managing teams, clients, services, and alignment, as well as having to make hard decisions. The author then categorizes the types of mistakes made as frequent, occasional, every once in awhile, and once. Examples are provided for some of the categories, such as frequent mistakes including estimating errors and juggling teams.
So with all that is going on, we have put together a guide for help with remote work. Including communication tools, productivity hacks, forming habits, video, and marketing tips.
Webinar on how to work remotely in construction with a focus on office staff and leadership. Register for the webinar here to watch it on demand: https://zoom.us/webinar/register/WN_0MVokf0LQKKZrT5hQAAW_A
Pair programming involves two programmers working together, with one typing and the other reviewing the work. It allows for knowledge sharing and immediate feedback. When used selectively, it can produce higher quality code and help onboard new programmers. Mob programming takes this further by having the entire team work together on one task using one screen and keyboard, rotating who physically types. It aims to improve shared understanding and code quality through extensive collaboration, but may reduce delivery speed and be challenging for those who prefer individual work. Effective use of these techniques requires open communication, shared goals, and avoiding forced participation.
Trong talk lần này của Grokking, anh Huy sẽ chia sẻ về điểm hay và tác hại của văn hoá chat ở công sở, và đưa ra thêm những lựa chọn khác phù hợp hơn cho từng trường hợp cụ thể. Đối tượng là dành cho các team khi gặp các vấn đề sau:
1. Bạn cảm thấy bỏ rất nhiều thời gian, nhưng lại không làm được gì nhiều vì luôn bị đồng nghiệp nhờ/hỏi khi có công việc gấp
2. Cuối ngày nhìn lại bạn chả nhớ mình làm được gì quan trọng
3. Bạn dành thời gian trao đổi với team rất hăng hái để đưa ra quyết định, nhưng 3 tháng sau lại quên mất tại sao hồi đó quyết định như vậy..
Bài talk sẽ nói về thói quen giao tiếp bất đồng bộ, thói quen ghi lại những gì mình cần nói & cách xây dựng wiki cho team của mình nhằm mục tiêu hạn chế những ảnh hưởng không tốt của việc sử dụng chat.
Speaker: Huy Nguyen - CTO @ Holistics
Flip the Script Friday - Working From HomeHeather Newman
Flip the Script Friday - Working from Home session - learning about all the different ways folks are connecting along with all of you. Talking Microsoft Teams, Zoom and WFH tips from me and Microsoft
So now we’re all remote workers. Whether you’re managing teams or working for studios that are rapidly transitioning to remote work, it’s important to start understanding the new skills, disciplines, and technology required for all of us to be collectively successful as remote workers. But where do you start? This talk focuses on precisely how the clever application of technology and technique can untether you from your location, keep you deeply connected to your team and project, and distinguish yourself as a spectacularly effective Remote Work Superhero.
This document provides lessons and tips for thriving as a remote worker during the COVID-19 crisis. It discusses the importance of being forgiving with colleagues, leaning into asynchronous communication, setting boundaries for communication tools, experimenting with different tools, and ensuring employees feel valued and supported. The document also lists tools used by the Buffer team and tips for using Slack effectively when remote.
This document provides guidance on remote work for teams, managers, and employees. It emphasizes that remote work requires trust management and servant leadership rather than just task management. It recommends mimicking company culture, allowing for social times, and enhancing transparency when working remotely. It also provides tips for remotely brainstorming such as using the right tools, keeping everyone involved, and maintaining timelines. Additional advice includes building trust with remote employees through communication, assigning meaningful work, and clearly defining expectations. Getting valuable output from remote workers requires focusing on team dynamics, using the right tools, and establishing good processes along with organizing routines and avoiding distractions.
This document provides guidance for employees on working from home during the COVID-19 outbreak. It offers tips on setting up a safe and productive physical and virtual workspace. It emphasizes the importance of staying connected to colleagues through communication, collaboration, and leading inclusive online meetings. Finally, it provides guidance on managing time and well-being while working remotely, including sharing availability, taking breaks, and the role of managers in supporting remote employees.
This document provides guidance and tips for employees working from home during the COVID-19 outbreak. It covers setting up an effective physical and virtual workspace, staying connected with colleagues through communication and collaboration tools, managing time and well-being, and tips for managers to support their remote teams.
The document provides guidelines for companies on having employees work remotely during the COVID-19 pandemic. It discusses how working remotely can help minimize virus transmission. Recommendations include establishing work schedules, finding a dedicated work space, taking breaks, and maintaining communication with teammates through video calls and messaging. The challenges of remote work such as disconnecting after hours and loneliness are also addressed.
13 easy tech tricks to make you more productiveProofHub
There are only 24 hours in a day and everyone wants to be more productive. In this presentation we have listed 13 easy tech tricks to make you more productive. It’s so easy and useful you can begin using it now.
This document provides guidance for implementing Scrum in distributed teams. It discusses the importance of effective communication and building trust between distributed teams and product owners. Specific recommendations are provided to improve communication through investing in videoconferencing equipment, setting clear contact protocols, and shifting away from relying primarily on email. Building trust is also emphasized through overcoming inevitable misunderstandings that arise in distributed settings. Overall, the document encourages distributed Scrum teams to focus on the core Scrum principles while adapting practices to address the unique challenges of working across distances.
Clerk Smarter, Not Harder - Productivity Tips for Parish and Town ClerksScribe
The document provides productivity tips for clerks to help them work smarter, not harder. It discusses common time management challenges clerks face and presents 10 tactics and 10 tools to improve productivity. The tactics include clearing your mind, using the two minute rule to complete small tasks immediately, prioritizing tasks with the Eisenhower matrix, eating your frog/tackling the biggest task first, combating Parkinson's law by setting deadlines, creating a daily to-do list with the 1-3-5 rule, and using habits and the Seinfeld method to build chains of productivity. The tools suggested include using voice assistants, note taking apps, task managers, group messaging, Google Docs for collaboration, scheduling apps, self-tracking
Life of a Remote Developer - Productivity tips (MSBuild 2020)Davide Benvegnù
[These are the slides from my session at Microsoft Build 2020]
Working remotely is not easy, even if you are a developer.
Let’s take a look at some techniques and tools to improve our productivity when working remotely (and that works as well if you’re working in office!)
8 Productivity Tools Not-For-Profits Can Use To Increase Office Productivityrgtechnologies
As our funding models change, our organisations must become more productive and efficient to ensure we can keep serving our clients.
In this presentation, we'll introduce you to some amazing apps and tools that can help boost your office productivity.
Clerk Smarter, Not Harder - Productivity Tips for Parish and Town Clerks Scribe
YOU WILL DISCOVER:
• Task management and prioritisation
• Simple digital tools to improve your productivity
• Wellbeing tips to reduce stress and clear your head
Speaker John Fagan has over 20 years of international experience running and coaching teams of professionals. During this workshop he will share some of his favourite techniques and tools that helped him survive working in high growth businesses.
This document discusses rapid prototyping techniques for quickly building products from ideas. Rapid prototyping allows developers to build products faster through instant feedback on code changes and leveraging existing open source libraries. It is suggested that dynamic languages, interactive development environments, and pushing code to the browser can provide very fast feedback. While prototypes may be thrown away, the rapid trial and error process of prototyping can lead to higher quality products and better engineers through continuously improving ideas.
Similar to Communication @ Funnelll - Doing Remote-First the right way (20)
Explore the key differences between silicone sponge rubber and foam rubber in this comprehensive presentation. Learn about their unique properties, manufacturing processes, and applications across various industries. Discover how each material performs in terms of temperature resistance, chemical resistance, and cost-effectiveness. Gain insights from real-world case studies and make informed decisions for your projects.
8. 1. Slack over email always
a. I check my emails a couple of times a day
b. I always keep an eye on Slack
2. Use one-on-one chat for your one-on-one discussions,
use #general for team wide discussions/questions
9. 1. We span multiple time zones so folks might get your
message late in the night or too early in the morning
a. Don’t mention (@) someone unless you want them to know
that they need to act ASAP
b. Use common sense to decide what needs to be handled
ASAP
c. If EVERYTHING is urgent, then nothing is urgent
Example of urgent cases: Customer satisfaction issues/bugs, the
apocalypse (although arguably communicating that is useless)
10. #Alerts: Errors/Exceptions from production
environment go here
#Circleci: Build events are reported here as part of
our gitOps
#Code: Code commits made by everyone are
reported here
#Registration-alerts: Notifies us about actions
customers take on the website: e.g Register, Enable
App, Initialize Checkout, and subscriptions
#Customers_lounge: We give access to some
customers to our Slack workspace. Those are usually
active customers and they are very vocal about what
works (or doesn’t)
11. Use Zoom for one-on-one and ad-hoc calls
● You can start a Zoom call right from Slack by writing /zoom
Use Google Hangout for 2+ participants
If a call can save discussion time then, by all means, jump on a
call. For the other 90% of the cases, chat fits better
Always document the call conclusions
12. Use Notion to document everything, solutions, hacks, etc.
This should be the first place to search for information and
documents on Funnelll
If it is not on Notion, add it
13. We prefer to use WebStorm as our IDE
By having everyone using the same IDE, we keep the same
indentations and code format across development
environments
By hay, who are we to tell a developer which IDE to use?!
14. Use Asana to manage our requirements and backlogs
Marketing Backlog,
Experiment backlog,
Feature backlog, etc.
20. ● Daily Scrum (15 mins)
○ Daily (duh!)
● All team meeting (45 mins)
○ Bi-weekly
● One on One with Sherif (30 - 45 mins)
○ Monthly
○ Whenever you feel like it