Skip to content

Commit bc724ac

Browse files
feat(posts): add "Working backwards"
Post: 2024-08-03-working-backwards.md
1 parent 8523b65 commit bc724ac

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
layout: post
3+
title: Working backwards
4+
date: 2024-08-03 14:42:52
5+
excerpt: Why working backwards is an important engineering skill.
6+
categories: engineering
7+
---
8+
9+
A key engineering skill is the act of **working backwards**. For example, let's say there are plans to update a screen in a software application. If you haven't worked in that area before, how would you go about changing it?
10+
11+
You start off with the text on the screen. Search the frontend codebase for that string. It might be inside an [i18n](https://wikipedia.org/wiki/Internationalization_and_localization) file or an HTML or [UI](https://wikipedia.org/wiki/User_interface) component. Once you identified which file the text is rendered in, then look for any API calls.
12+
13+
[API](https://wikipedia.org/wiki/API) requests will uncover the backend routes that is consumed by the frontend. By identifying the routes, you can identify the controllers that handle the business logic. Afterwards, you should be able to examine the models and understand how the data is manipulated and stored in the database.
14+
15+
As you debug and trace the stack from start to finish, you will form a picture of how the application works end-to-end.

0 commit comments

Comments
 (0)