The Lone Architect @lonearchitect0

Freelance Software Engineer & Architect | Follow me for more articles about System Design, Software Engineering, Distributed Systems and Algorithms blog.thelonearchitect.com France Joined October 2021

Tweets

141
Followers

29
Following

241
Likes

449

The Lone Architect @lonearchitect0

3 years ago

Concept ideas : building an app only from bits copied on the Internet (SO, Github...).

0 0 0 0 0

The Lone Architect @lonearchitect0

3 years ago

Front-end in a nutshell

0 0 0 0 0

Download Image

The Lone Architect @lonearchitect0

3 years ago

blog.thelonearchitect.com/automated-test…

0 0 0 0 0

The Lone Architect @lonearchitect0

3 years ago

medium.com/@Ancyr/a-gentl…

0 0 0 0 0

The Lone Architect @lonearchitect0

3 years ago

One of the most aggressive git command probably is `git branch -M master`

1 0 0 0 0

The Lone Architect @lonearchitect0

3 years ago

No thanks

0 0 0 0 0

Download Image

The Lone Architect @lonearchitect0

3 years ago

Idea : 10 pushups every commit. 30 squats every push. 5 pull ups every successful CI build 50 jumping jacks every failed CI builds

1 0 2 0 0

The Lone Architect @lonearchitect0

3 years ago

"The proper use of comments is to compensate for our failure to express ourself in code" Clean Code.

0 0 1 0 0

The Lone Architect @lonearchitect0

3 years ago

10 years without using IDs in my CSS and counting.

0 0 0 0 0

The Lone Architect @lonearchitect0

3 years ago

Where there's a switch, there's a hidden strategy pattern looking to get in the place.

0 0 0 0 0

The Lone Architect @lonearchitect0

3 years ago

Deadlines lead to problems. Either it's overdue by months, if not years. Or it's enforced and the system is broken in unexpectable and undesirable ways.

0 0 0 0 0

The Lone Architect @lonearchitect0

3 years ago

Most of the programming wisdom is inherited from before 2000. Software Engineering is adapting this wisdom to the new fields.

0 0 0 0 0

The Lone Architect @lonearchitect0

3 years ago

Most often, the first solution for a problem is far from optimized. Also, most often, this same first solution is way sufficient for a starter. Grasp understanding of the problem before optimizing in the wild.

0 0 0 0 0

The Lone Architect @lonearchitect0

3 years ago

Complexity relates to understanding. Difficulty relates to execution. Simple but Difficult : lifting 30kg Complex but Easy : creating an e-commerce with Magento

0 0 1 0 0

The Lone Architect @lonearchitect0

3 years ago

Code is written for human to read, and eventually for machines to execute. Spend time making the code easier to understand and optimize later.

0 0 1 0 0

The Lone Architect @lonearchitect0

3 years ago

A variable name can either carry : - Information about how it is defined : isAdmin - Information about how it is used : canAccessAdminPanel The 1st is bound to the logic used to determine its value, the 2nd is bound to its purpose.

0 0 1 0 1

Download Image

The Lone Architect @lonearchitect0

3 years ago

Framework come and go, but the ideas remain. Functional programming has been there since 1936. React is only 10 years old.

0 0 0 0 0

The Lone Architect @lonearchitect0

3 years ago

Use short variables names where it's idiomatic to do so. Eg : i,x,y for loops/arrays. Otherwise, use long, intent-revealing names that explain the why of their existence. If the name is too long, it probably carries too much context information => extract into a method.