1
3
2
6
3
4

I’m testing a tiny idea: “README policy as code.”

Not markdown style linting, but more of a maintainer checks:

  • required sections
  • example presence
  • link checks

Would this be useful in your projects?

If yes, what’s the one rule you’d want first?

4
9
Announcing TypeScript 7.0 (devblogs.microsoft.com)
5
3
6
1
7
1
Engineering a Fast Logger (blog.coderspirit.xyz)
8
5
Announcing TypeScript 7.0 RC (devblogs.microsoft.com)
9
9
10
3
11
2
12
0
13
0
14
8
Errors Deserve Better (ifandelse.com)
15
4
Announcing TypeScript 7.0 Beta (devblogs.microsoft.com)
16
6
17
4
18
2

Every as in your TypeScript is a tiny lie. Sometimes a necessary one, but a lie nonetheless — you're telling the compiler "trust me" about data it can't verify. The question is: when can you avoid it?

19
2
20
22
21
8
Announcing TypeScript 6.0 (devblogs.microsoft.com)
22
7
23
6
24
4
25
-1
view more: next ›

TypeScript

1116 readers
1 users here now

founded 3 years ago
MODERATORS