CedricTeyton

For French PR: - https://www.maddyness.com/ - https://www.frenchweb.fr/ - https://www.presse-citron.net/ - https://www.journaldunet.com/ - https://www.rudebaguette.com/

I enjoy reading docs from Algolia and Stripe. Both are educative and visually stunning.

> Five years ago we would have used Medium without a second thought, but we moved away from it as it became less and less usable.

Similar to Medium but developer-friendly, you could use dev.to or Hashnode

> Do I need to talk to actual potential users?

IMHO, that's step 1. Interview people you think are your target. You should be able to understand the following:

- What their pain points are - How they currently solve them

It's key to validate your startup idea and envision the product.

Agreed.

Plus, in this specific case, I think soft skills are far more important as your daily job odes beyond your primary missions as described in your job description.

Above all? You must learn to ship fast.

neat!

Love Golang for its documentation. It's clear and straight to the point.

QED -- thanks!

How radical quality improvement has been set at Toyoto and how to map the Dantotsu process in Software Engineering.

The Hub is an open, resourceful place powered by the community where you can discover best coding practices. We feature 400+ practices from a wide set of domains — architecture, security, programming languages, green IT… These practices have been created from Promyze.

After spending some time to build and maintain a VSCode extension for our software at Promyze, we wanted to share some common use cases that any developer might be willing to address.

Hi Kevsim, thanks for your great comment, I do appreciate :)

Sorry if you had a hard time to read this post.

Your comment for the in Example #1 is right, we've shown only the first step. The second one would be to rename all others code operations: => Renaming `p1`, `p2`, `p1N`, `p2N => Remove the magic numbers 4, 6 and 1.

One important thing in this article is the fact that each tip should be used by a developer locally as an intermediate step during a refactoring of a legacy code. So for each tip, the second piece of code should not be the final version to be committed. It clearly needs additional operations and transformations.

We'll do our best to make our next post easier to digest :)

Hi Kevsim, thanks for your comment :)

I've probably under-highlighted in this article the fact that each operation is intended to be used locally by a developer as an intermediate step during a refactoring of a legacy code. All these tips allow to transform a function to a new state #1, supposed to be easier to understand, and as a root point to perform some modifications in your code.They are just easy-to-implement solutions to assist developers with a messy code. Then, you can start implementing tests to avoid regressions and continue your refactoring to a newer state #2, which will then be commited on your Git repo.

Hope this can help :)