• 12 Posts
  • 42 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle


  • Love this. Always interesting to see novel ways of querying data in the terminal, and I agree that jq’s syntax is difficult to remember.

    I actually prefer nu(shell) for this though. On the lobste.rs thread for this blog, a user shared this:

    | get license.key -i
    | uniq --count
    | rename license
    
    This outputs the following:
    
    ╭───┬──────────────┬───────╮
    │ # │    license   │ count │
    ├───┼──────────────┼───────┤
    │ 0 │ bsd-3-clause │    23 │
    │ 1 │ apache-2.0   │     5 │
    │ 2 │              │     2 │
    ╰───┴──────────────┴───────╯
    
    






  • Honestly, for any large scale project in Python, Pydantic makes it bearable. We use Python heavily at work (and I’d argue we shouldn’t be for the projects we’re working on…), and Pydantic is the one library we’re using that I wouldn’t be without. Precisely because it allows us to inject some of these static typing concepts and keeps us honest, and our code understandable.







  • I have read a few of these books. As for non-fiction:

    Pragmatic Programmer Excellent book; should be compulsory reading for all software developers.

    The Phoenix Project Enjoyable enough. It’s a fictional story and has some extremely role-cast, trope filled characters. But its purpose is not to be a great novel. Its purpose is to teach the history of and purpose of how dev-ops came about. I think it’s worth reading. I’m yet to try the Unicorn Project which I understand is actually more about software.

    Eloquent JavaScript I am not a huge fan of working with JavaScript or front end, but I did read this when I got placed on a long term project where I would be using it for the duration. I found this book excellent, and my JavaScript certainly benefitted from it.

    I also read a bunch of the fictional books. Bobiverse is one of my favourite series ever, despite the weirdness of the fourth book (it was still good). I’m just over halfway through Children of Time, and seriously regret not picking it up sooner. Well kind of, if I had I suppose I wouldn’t be enjoying it so much now!







  • The same reason a lot of companies support a community edition. It means that people can use, learn and become experienced with the product without forking over a tonne of money.

    This results in a larger number of developers, add-ons and community surrounding the product.

    This makes it a more appealing product for companies looking to build a business using it.

    It’s the same reason you can use AWS for free, get some JetBrains products for free and often find community editions for similar products to Magento.




  • I particularly enjoyed a recent company meeting that spent considerable time talking about the importance of flow state. It had an awkward pregnant pause when someone (usually very quiet) unmuted to ask, “is the policy to increase the number of days we must spend in our open-plan office kind of undermining this?”. Literally all of our directors just shifted on their seats hoping another would answer that.

    Eventually, HR director stated “Not at all, that’s what headphones are for!”

    Which was particularly delightful, as our tech director had only 20 minutes before stated how he would like to discourage people sitting in the office in silos with their headphones on.