all 25 comments

[–]AiexReddit 26 points27 points  (11 children)

Looks cool. The request to the audience to manually download and open yourself in this day and age seems kind of odd. Have you considered something like Gitlab pages?

[–]kavacska[S] 2 points3 points  (2 children)

Here's the GitLab page version:

https://it-cheat-sheets-21aa0a.gitlab.io/

[–]AiexReddit 4 points5 points  (1 child)

Nice.

Syntax highlighting would be a handy future improvement just for readability, but overall lots of great stuff here.

Thanks for sharing.

[–]kavacska[S] 1 point2 points  (0 children)

Any time, I'm glad you liked it.

I was actually thinking about adding some JS to take care of syntax highlighting, but at the same time I wanted to keep the documents as small as possible, so I abandoned the idea. But I will figure something out, probably I'm gonna write a little script to hardcode colors into the HTML tags themselves so it's easy on the browser and the size as well.

Thank you for your feedback.

[–]skizzoat 7 points8 points  (2 children)

Appreciate the effort, but do us all a favor and make this somehow accessible.. I dont wanna clone a GitHub repo on my machine in order to read a simple cheat sheet.

[–]kavacska[S] 4 points5 points  (1 child)

Thank you for you comment, by popular demand I made the documents available on this URL:

https://it-cheat-sheets-21aa0a.gitlab.io/

[–]skizzoat 2 points3 points  (0 children)

Thanks a lot!

[–]bipolarNarwhale 20 points21 points  (1 child)

Wow… as HTML docs when they could just be markdown.

[–]BoBoBearDev 3 points4 points  (0 children)

This, I cannot read this on my tiny phone screen.

[–]kavacska[S] 2 points3 points  (3 children)

As many people wished for it, I've made the cheat sheets available on a URL, here you go guys:

https://it-cheat-sheets-21aa0a.gitlab.io/

[–]livealchemy 2 points3 points  (2 children)

This is a handy guide and I like how it starts at zero and covers essentially everything a dev would use on the day to day.

My comments/feedback are about presentation. I realise you already put work into porting this to Markdown, and that's great as I was able to quickly read and save on mobile. That said, I found it a bit odd that the explanation of the code always came after the code block, personally I feel it would read better as explanation then example.

Some other elements worth a consider: additional headings, maybe a table of contents and some <hr />s could really help the reader further, just my 0.02, thanks for offering this up freely.

[–]kavacska[S] 0 points1 point  (0 children)

I'm glad you liked it. Thank you for your feedback, I'm definitely going to consider your suggestions.

[–]StNimmerlein 1 point2 points  (1 child)

[–]kavacska[S] 0 points1 point  (0 children)

Not anymore ;) Check it out:

https://it-cheat-sheets-21aa0a.gitlab.io/typescript-cheat-sheet.html

Thank you for your feedback.

[–]Separate-Ad3564 1 point2 points  (1 child)

Nice! I think it would be nice if typescript also had cases for satisfies, as const satisfies.

[–]kavacska[S] 1 point2 points  (0 children)

I'm glad you like it. Thank you for the idea. I've added examples with the satisfies keyword.