Things I tried to do: - Not to rely on color alone. Multiple visual indicators, ie. color and symbols. - Include only the most necessary and valuable information - Soft and actionable wording, avoid complicated terms (still needs some work)
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Also what you’re seeing here is just the console output of a diagnostic. The diagnostic is just plain JSON that could be visualised anywhere, eg. an IDE, a browser etc.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It's a consolidated toolchain with a custom bundler, compiler, linter, testing framework, dependency manager etc.
- 3 more replies
New conversation -
-
-
So in your case, Rome was built in one day
-
Actually built over the course of literal years.
End of conversation
New conversation -
-
-
Is it just me or the red-on-black(dark color with greenish tint) is far less readable than red-on-white? Disclaimer : I never find default dark themes of any IDEs usable (sublime's default or darcula on jetbrains)
-
Your terminal can be formatted however you want. ANSI color codes only define a "name" and not something like a hex value so it's entirely configurable.
- 1 more reply
New conversation -
-
-
Actionable feedback is the biggest thing we lack in modern developer tooling. Absolutely love this
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 