I really like Nushell. I would not run it as a daily driver currently, as it mostly doesn’t win me over from Fish, feature-wise, but I love having it available for anything CLI date pipeline work I need to do.
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 │
╰───┴──────────────┴───────╯
Yes, I don’t know how I forgot to mention that Iceshrimp and Sharkey both have Mastodon compatible APIs - so all the same apps work (mostly).
Based on your requirements, I would suggest looking at one of the Firefish / CalcKey forks. They are ideal for single user or small instances and they support s3 compatible object storage out of the box.
I would recommend looking at Sharkey or Iceshrimp. Both are under very active development and have very responsive developers if you need support.
If you would like to check out an example, Ruud (of mastodon.world and lemmy.world) set up an instance of Sharkey at (you guessed it) sharkey.world.
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.
Yes! The concepts are intertwined.
I think the key take away, for me, is to lean heavily into your type system and allow that to do some of the heavy lifting. Accept that something like a username
is not a string, but a subtype of a string (this has to be true if any validation is required, otherwise you’d just accept any valid string).
It’s one of my favourites. Something I revisit every couple of years.
That one has been on my list for a while. Are you finding yourself able to easily apply what is taught to your day-to-day?
Different strokes for different folks, I guess. I enjoyed Heroes for what it was.
I agree that Sonic Battle was one of, if not the best entries for character building. And SB is, in fact, my all-time favourite Sonic game. Breaks me that I may never see a sequel / reboot, and get to relive Emerl’s story.
I’d honestly be happier with no guns. Not sure if that was their greatest move, in their effort to make him ‘edgier’. He was perfect in SA2 and Sonic Heroes.
I am very excited for this. One part of my childhood that I’ve never been able to let go of is my total fanboy-ism of Shadow.
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!
I believe the lower cable connects the two boards. The upper cable is for connecting to your device, so would only be connect to one of the boards when in use.
I use UK standard layout, and Apple UK for work. It always takes me a few minutes to switch between them, but both are absolutely fine for programming. Just the odd placement of #
that bothers me a little, but I tend to use that only for Python comments - which I tend to do more commonly from a keyboard shortcut anyway.
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.
As in, I have Nginx running on my server and use it as a reverse proxy to access a variety of apps and services. But can’t get it playing nicely with AIO Nextcloud.
Yes I’ve not managed to solve this yet. For me, it’s hosting AIO behind my existing Nginx.
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.
Thank you, that’s very kind of you - and I completely agree, healthcare works are so undercompensated for what they do, and yet so vital. I feel the least they deserve is a Christmas meal to celebrate the end of the year together.
I really appreciate your offer to contribute and share this on.
Totally agree. Like most “rules”, it just needs treating with nuance and context.