deepstash

Beta

Do it like an engineer

Understand the size of the problem

It's important to understand what is how big the problem is.

Use questions like:

  • How many requests the system should satisfy?
  • What is the expected response time?
  • How many resources do we have?
  • What about deadlines?

113 SAVES


This is a professional note extracted from an online article.

Read more efficiently

Save what inspires you

Remember anything

IDEA EXTRACTED FROM:

Do it like an engineer

Do it like an engineer

https://hackernoon.com/do-it-like-an-engineer-e64ee3722326

hackernoon.com

4

Key Ideas

Understand the requirements

To solve a problem, you have to understand exactly what the problem is

When you start solving a problem, be sure to understand the starting point, the end goal, and the obstacles in between. The worst possible thing is to produce a solution that actually doesn’t do what’s expected. 

Understand the size of the problem

It's important to understand what is how big the problem is.

Use questions like:

  • How many requests the system should satisfy?
  • What is the expected response time?
  • How many resources do we have?
  • What about deadlines?

Stand on the shoulders of giants

The chance someone else already solved your problem is high. All you have to do is a search in the literature to find out if there is a solution for a problem matching your use case. There is no point in reinventing the wheel.

"Grandma-Driven" Development

Implement your solution trying to make it understandable by your grandma

Avoid fancy and complex implementations. Put them aside in favor of a simple and understandable one. And optimization to the moment they are necessary.

EXPLORE MORE AROUND THESE TOPICS:

SIMILAR ARTICLES & IDEAS:

Basic steps to solving any problem
  • Understand the Problem, so you know you're actually focusing on the the real issue at hand.
  • Create a Plan, so you have a series of actionable steps to follow.
  • ...
Understand the Problem

Often the most difficult step, because it's easy to focus on the wrong part of the problem, or look at the problem too broadly.

The first thing you need to do is reduce it to its simplest and purest form so you know exactly what you're dealing with. While you're doing this, you need to ask yourself questions to make sure you're focusing on the right things. 

Create a Plan

You need a plan with actionable steps. Ask yourself what's barring you from moving forward and make step one. Step one will open doors to other steps. 

Consider which steps will open more doors, add them to the plan, and keep doing that until you get to your solution. Things will change as you act on the plan and you'll need to adapt, so it's best to keep your plan somewhat open-ended and try to include steps that involve preparing for trouble you can foresee. 

one more idea

Beau Lotto

"There is no inherent value in any piece of data because all information is meaningless in itself. Why? Because in..."

Beau Lotto
Data is Not Reality
  • We see organizations and the engineers who work in them steering towards big data, so it is commonly assumed that data means acumen and direction.
  • Any Data, by itself, does not bring clarity. Data is just information, not reality. It does not represent anything in the field of actuality.
  • Data is also, never complete. Getting more and more Data does not equate to getting more clarity.
Incomplete Data is Misleading

Our brains like to fill up incomplete information based on our prejudice and confirmation bias.

As all data is inherently incomplete, we use our minds to fill the missing information, based on the existing data we have, and that can go obverse.

4 more ideas

Practical ways to use First Principles Thinking
  • If you’re starting a business, use first principles to build a product or service that’s fundamentally better than the competition.
  • If your day is too busy, first princip...