A maker is a person who likes to make and create things. They like building an idea from scratch and founding startups. Most developers are makers. They enjoy the process of designing, developing, experimenting and building a minimal viable product (MVP). A mender is a person who likes to maintain a product. They help it to growth and change to meet their customers needs over time. About 10% of developers are menders. They enjoy updating, refactoring, testing and remodeling your code. You can depend on menders to help you grow and maintain your products.
What kind of developer are you?
You are a maker if you:
Enjoy tackling a problem and creating a brand new solution
Like to experiment with new ideas and techniques
Get bored if you have to repeat the same tasks
Find refactoring code, fixing bugs and handling customer support requests to be boring
You are a mender if you;
Find refactoring code, fixing bugs and handling customer support requests to be interesting
Enjoy fine tuning or updating existing code
Get stressed if you have to tackle a new problem and build a solution from scratch
Like to work best without hard deadlines
Not sure? Andrea Goulet of CorgieBytes explains the difference.
Staying motivated as a maker or mender
Developers love to write code. Makers and menders are motivated by different things. To create your best code, you need to know what motivates you.
As a maker, you work the best when you can experiment, create prototypes and develop ideas under a deadline. Makers are like home builders. They design, build and move onto the next house.
Menders work best when they have a number of tasks to complete. They enjoy deep diving into the code and fixing bugs and refactoring it. Menders are like home remodelers. They tweak, rearrange and fix what it wrong with an existing house.
When you write code, you have to maintain it. You can make your code more reliable and secure. Legacy Code Rocks is a podcast for menders or anyone who has to maintain code.
Developers like to build stuff. Apps, websites, apis or a quick little script that does something quickly and easily for you. A developer portfolio shows your best work. Whether it is a single page website or a full website with a blog, your portfolio shows your unique style and approach to solving problems.
Tips for building your portfolio
1. Start with a plan
Treat your portfolio like it is a project for a client or your employer. Plan it out. Think about what pages you want to create, what projects you are going to include and additional resources like screenshots you are going to need. Write your copy and sketch out your design. You don’t have to be a graphic designer to showcase your best work.
2. Consider what tools you use
You can build your portfolio with whatever tools you want. Whether you decide to build it from scratch or use an existing framework, don’t choose to use a framework or technology because you can. You want to make it easy for you to maintain.
3. Buy your own domain name
Why? With your own domain name, you control how it looks and what you can do with it. If you want to create new projects like an app or a tutorial website, you can. Your own domain name makes it easier for potential clients or employers to find you.
4. Make sure it works on mobile
You want your website to be readable and look good on as many platforms as possible. There are different ways to test your website for mobile from resizing your browser to testing on a mobile device. Choose the method that works best for you.
5. Choose your best work
Don’t show everything that you have built. Choose projects that demonstrate your current skills. If you develop mobile applications, don’t include projects from when you created websites for WordPress. Be picky. Show the pieces that reflect who you currently are.
See how other developers created their portfolios
When building your first one or updating an old one, it helps to see what other developers have done. Be inspired by other developers.
Brent Krueger is a freelance web designer and developer. He uses a beautiful photo of the state capitol building in Madison, WI in his website’s header.
Christina Richardson is a UX Researcher and Designer. She has a one page portfolio with a timeline of her career in UX and an infographic of her design process.
Jess Johnson is a full stack developer. He uses great typography and a simple color scheme.
Ali Spitel is a developer. Her website has a minimalist design with simple navigation and a great use of color.
Kyle Ledbetter is a designer and developer. He uses a mix of background colors and images for each section. In his About, he uses the states as subtle background images.
What tools do you use to manage your projects? Do you track them using lists, a bullet journal or a project management tool like Trello? With Trello, you can create a meal planner, a weekly to-do list, manage clients and development projects. You create as many board, cards and lists as you need.
With all of this flexibility, it can be a challenge to figure out how to best work with Trello. Use the following tips to make this project management tool work for both your personal and professional projects.
1. Create a projects board
If you are like most people, you may have more than one project to keep track of. A projects board can help you to plan which projects that you want to work on next. Some people like to plan the next six months or year out. Use this board to provide on overview of what you are working on.
2. Make one board for each project
It may be tempting to place all projects on one board. You may find that it grows rather quickly and becomes hard to manage. A single board for each project keeps things simpler and cleaner.
3. Create as many lists as you need
Trello is based on the Kanban method, which starts with three lists: To-Do, Doing and Done. For some projects, these three lists are all you need. For other project, you are going to need more. Make as many as you need.
4. Give your labels meaningful names
Trello provides different colored labels with no names. It is up to you to decide what they mean. You can use these labels to help manage your tasks. For example, you may use red for Stopped or Blocked tasks, yellow for waiting and orange for annoying issues.
5.Use the inspiration boards
Why create a board from scratch? Trello has a public library of boards that others have created and are available for you to use. Use one these boards to get started on your next project.
Looking for more tips and inspiration on how to use Trello?
Trello’s blog has helpful tips and tutorials on using this project management tool more productively and creatively.
Dashboard design sounds simple. You want to create a way of presenting data to your users that is clean and easy to understand. Easy right?
No, dashboard design is more difficult than it seems. You need to consider your users before you can decide what data to present to them and how.
Ask these questions before you start building
What data needs to be show to your users? You want to track a small number of key metrics. Not all data should be on a dashboard. Some data belongs in a report. If the data your considering is a summary or analysis, it may work better as a report.
How am I going to present this data? You can choose to display the data as a chart, gauge, totals or a simple table.
What actions do you want the user to take? Should they click on a link to open a report, update some information or do nothing?
Sketch out your design
After you researched and learned what data the user wants to see, you need to decide how to organize the data. You may find that you have too many pieces of information to present to the user. Sketch out your dashboard before you build it to determine what pieces of data go where. An easy to read dashboard has from 5-9 pieces of information on it. Remember that less is more.
Keep the design simple
You want your users to be able to scan the dashboard quickly. Help them by choosing to limit the number of pieces of information, colors, fonts and other UI elements. Your design should be minimal.
By asking questions before you build a dashboard, sketching out the design and keeping the design simple, you can give your users key pieces of information quickly.
How do you take screenshots of your code? The simplest way is to use your screen capture application that comes with your OS. Then, you can improve it by using a graphics editor like GIMP.
What if you want your code to look right without the extra work? You can capture your code using a extensions that work with your code editor.
Polacode is a Visual Studio Code extension. You launch it by using the command palette and typing Polacode, It opens the Polacode window next to your code. You select and copy the code you want a screenshot of. Paste it into Polacode, click the camera button and it generates a screenshot for you. Then, you can use the screenshot for your blog, social media accounts or future reference.
If you use Visual Studio Code, you can modify the settings to get a clean and easy to read screenshot. Andrew J. Byrnewalks you through the 6 settings he uses. If these tools don’t create the screenshot that you are looking for, you can also use 5 Ideas for making a screen shot great.
What if I want more than a screenshot?
Screenshots are great for static images of your code. What if you want to create a demo or screencast? Travis Fischer on Hacker Noon provides you with different tools for making your code look beautiful.