Hacker News Reader

petr25102018on Nuxt 4.6

I didn't like Nuxt in the past, but I switched to it recently from Django and found it actually awesome for one person team. I am constantly amazed by its ecosystem packages like NuxtUI or NuxtSEO.

petr25102018on Thoughts on slowing the fuck down

No, that's plain wrong (I am from Czech Republic). You can even get an "engineering degree" (Ing.) by studying economics.

petr25102018on I now assume that all ads on Apple news are scams

I am glad I am not the only one. Why do I see it like 50 times a day?

petr25102018on Why we migrated from Python to Node.js

Perhaps because Instagram uses their own Python and a heavily custom Django fork?

petr25102018on Pico CSS – Minimal CSS Framework for Semantic HTML

I like to use Pico CSS as a starting point for websites (as opposed to apps). I even put it in the my Django starter kit (https://github.com/stribny/sidewinder/). Recommended!

petr25102018on Show HN: I wrote a modern Command Line Handbook

Oh that's great. Thanks!

petr25102018on Show HN: I wrote a modern Command Line Handbook

I don't want to just add to it because the entire idea is to have a short book, but I will be thinking about replacing/improving some sections. The examples already demonstrate the practical scenarios, but I think there could be a few sentences about how a particular concept can be used in real world scenario.

Thanks for sharing:)

petr25102018on Show HN: I wrote a modern Command Line Handbook

Thanks for the suggestions:)

petr25102018on Show HN: I wrote a modern Command Line Handbook

Thank you!

petr25102018on Show HN: I wrote a modern Command Line Handbook

Thanks!

petr25102018on Show HN: I wrote a modern Command Line Handbook

Thanks for the tip. I will explore it.

petr25102018on Show HN: I wrote a modern Command Line Handbook

Thanks for the input. I have made several updates to the book in the past and this would be lost in print, but as the book matures and I incorporate feedback it can be interesting to try offering a print version. Perhaps print-on-demand type of thing.

petr25102018on Show HN: I wrote a modern Command Line Handbook

Yes, the linked sample pages are just randomly taken pages from the book PDF, as I put it together quickly for the Show HN. Apologies. I will make a better example when I rework the landing page.

petr25102018on Show HN: I wrote a modern Command Line Handbook

DevOps is not very specific term... so hard to list specific things to learn. But it certainly will be much, much more than just shell/command line knowledge.

petr25102018on Show HN: I wrote a modern Command Line Handbook

Thank you

petr25102018on Show HN: I wrote a modern Command Line Handbook

I definitely recommend to try things as you go along, copy paste things and run them yourself. As for the timeline, everyone is different. My own take is that learning always takes time and repetition, so I would not rush it and focus on practice.

petr25102018on Show HN: I wrote a modern Command Line Handbook

Nice! At least you get your feedback in real time, see what people struggle with and so on. That can be very useful.

petr25102018on Show HN: I wrote a modern Command Line Handbook

Thank you!

Yes, as other people pointed out too, the landing page could do with some mobile and copy improvements.

petr25102018on Show HN: I wrote a modern Command Line Handbook

Thanks for the feedback.

I agree and I try to keep it as nice as I can, but it can be hard to do when the book is being updated and the content changes.

Nevertheless I will be mindful of it for the next update.

petr25102018on Show HN: I wrote a modern Command Line Handbook

I would not say it is trash, but I tend to agree with the general sentiment and personally don't write longer scripts.

> This is also the advice given in the google shell guide.

This advice is also given in this handbook :) But in reality you might come to a work repo that already has such scripts and it is good to understand it a little bit, I would think.

petr25102018on Show HN: I wrote a modern Command Line Handbook

Thanks for the clarification. I will see if I can sneak in a note about this in the next update :)

petr25102018on Show HN: I wrote a modern Command Line Handbook

Great somebody thought of it!

petr25102018on Show HN: I wrote a modern Command Line Handbook

Thanks.

You teach this in a classroom?

petr25102018on Show HN: I wrote a modern Command Line Handbook

Thanks!

petr25102018on Show HN: I wrote a modern Command Line Handbook

I agree too, Just (and others) are better as a pure entry point. But when you come to projects that already have Makefiles, or you know you have just one less thing to install in a container... you use Make.

petr25102018on Show HN: I wrote a modern Command Line Handbook

You are right. It is wrong, will need to look into this.

petr25102018on Show HN: I wrote a modern Command Line Handbook

> I agree with all this. I'm on Firefox android, pixel, lose part of the screen too.

Ah okay, I really wasn't aware. Thanks for reporting.

petr25102018on Show HN: I wrote a modern Command Line Handbook

Thank you for the nice words :)

petr25102018on Show HN: I wrote a modern Command Line Handbook

I wanted to demonstrate the use of the substitution, not the best way to diff directories. Often I tried to create examples that demonstrate multiple concepts or tools at once to save space. But I see your point.

petr25102018on Show HN: I wrote a modern Command Line Handbook

The older standard tools, because they can be easily put in CI pipelines and shared as scripts with coworkers.

For example, in my personal and professional life I use Make everywhere. The book mentions alternatives, but the examples are built on the time-tested tools.

I focused on things that don't require install (if given the option) or the ones that you are more likely to encounter at work. It is a tradeoff and I can see how the reverse would be appealing too.