typingcyclist

6 ms·

1.
Internationalization-check: Validating your Next.js internationalization(lingual.dev)
1 points by typingcyclist 1y ago|0 comments
2.
End to end React internationalization testing(lingual.dev)
1 points by typingcyclist 2y ago|0 comments
3.
How to Write Complex Software(grantslatton.com)
7 points by typingcyclist 2y ago|0 comments
4.
How to validate your React internationalizationext application(lingual.dev)
1 points by typingcyclist 2y ago|0 comments
5.
How can you tell if the company you're interviewing with is rotten on the inside(charity.wtf)
4 points by typingcyclist 2y ago|2 comments
6.
Validating your react-intl applications(lingual.dev)
1 points by typingcyclist 2y ago|0 comments
7.
Checking Your Internationalization on the CI(lingual.dev)
2 points by typingcyclist 2y ago|0 comments
8.
Building International User Interfaces(lingual.dev)
3 points by typingcyclist 2y ago|0 comments
9.
Querying Top-N Rows(use-the-index-luke.com)
2 points by typingcyclist 2y ago|0 comments
10.
In Search of the DX in Internationalization(lingual.dev)
1 points by typingcyclist 2y ago|0 comments
11.
Zoom Out: The missing feature of IDEs(medium.com)
4 points by typingcyclist 4y ago|0 comments
12.
Notes on Building a Modern Typing Training App: Code Based Training(gist.github.com)
1 points by typingcyclist 4y ago|0 comments
13.
Thriving on the Technical Leadership Path (2019)(keavy.com)
3 points by typingcyclist 4y ago|0 comments
14.
The Hierarchy Is Bullshit (and Bad for Business)(charity.wtf)
3 points by typingcyclist 4y ago|0 comments
15.
Notes on Modern UI Development: Taking Ideas from Spaced Repetition(gist.github.com)
2 points by typingcyclist 4y ago|0 comments
16.
You Might Not Need the Virtual DOM (2018)(blog.functorial.com)
1 points by typingcyclist 4y ago|0 comments
17.
Notes on Modern UI Development: Iterating over the Other 80%(gist.github.com)
1 points by typingcyclist 4y ago|0 comments
18.
From design patterns to category theory (2017)(blog.ploeh.dk)
3 points by typingcyclist 4y ago|0 comments
19.
Ship Small Diffs (2017)(blog.skyliner.io)
15 points by typingcyclist 4y ago|1 comments
20.
Notes on Modern UI Development(gist.github.com)
2 points by typingcyclist 4y ago|0 comments
21.
Behavior Change = Revenue versus Structure Change = Option(tidyfirst.substack.com)
2 points by typingcyclist 4y ago|1 comments
22.
Work is work, in which returns diminish (2020)(codahale.com)
227 points by typingcyclist 4y ago|105 comments
23.
by typingcyclist 4y ago
The Github API is definitely a good benchmark. Linear's GraphQL API might be another interesting one to look into https://developers.linear.app/docs/graphql/working-with-the-... .
24.
Outcome over Output: Also Impact and Effort(medium.com)
2 points by typingcyclist 4y ago|0 comments
25.
by typingcyclist 4y ago
Good point. Also probably the performance problem will come from some slow query on the server side rather than some React code on the UI side.
26.
by typingcyclist 4y ago
Not sure I understand the point of this article. It seems that we're trying to talk about how popularity doesn't reflect the most advanced technical solution. But where is that the case? Java's adoption is huge compared to sa
27.
by typingcyclist 4y ago
Depending on what you want to build and how many people will contribute, the answer might vary. HTML/CSS/JS can be enough, but mostly you will need to handle streamlining browser differences etc. explicitly. Frameworks are popular
28.
by typingcyclist 4y ago
I doubt that Scrum is about helping developers or whatever this post is trying to imply. It's a very mechanical framework with rigid rules and meetings. It's very fragile and breaks apart as soon as you try to change something. On
29.
by typingcyclist 4y ago
What exactly is the goal for adding yet another meeting? There is a try to fix these issues within the agile community by "rethinking" instead of simply removing it. If it doesn't work, then remove it.