I chose C# for the same reasons. It's probably easier to make C# unreadable than Go due to plethora of features, but it all comes down to how you discipline yourself about writing code.
https://github.com/bflattened/bflat
Readit Newsmats852 commented on Go is my hammer, and everything is a nail maragu.dev/blog/go-is-my-... · Posted by u/markusw
mats852 commented on Learn PHP the Right Way github.com/ggelashvili/le... · Posted by u/schlonger0009
I like PHP, and guess what? I also like PowerShell for web apps. I don't really care what anybody says—I can build fast in PowerShell. My clients are happy, it's simple to debug, and I can tap into .NET classes when necessary. PowerShell + HTML + Alpine = productivity. I'm not building the next Netflix or Amazon and the end-user isn't going to notice or care that I haven't selected Node and React.
I just can't get behind the complexity of build steps and compiling, all just to get a website online. It's crazy. The simplicity that PowerShell (and PHP) bring to this process can't be overlooked... so I like to beat on this drum whenever I get the chance.
Choose the tool that is right for the job, and PHP can be that tool in a surprising number of cases.
I really learned to appreciate what Powershell is after listening to @adamgordonbell CoRecursive episode with Jeffrey Snover (https://corecursive.com/building-powershell-with-jeffrey-sno...).
I really loved PHP, but now with go+templ (https://templ.guide) I personally don't have a use-case for PHP anymore, but that doesn't mean it's irrelevant for the world.
It's like complaining about hardware stores because you can buy your wood from the lumberjack and nails from the blacksmith.
I'd rather have a system devoid of emotional biases, transparent and introspectable and rely on automated tooling to constantly monitor my dependencies.
mats852 commented on Google Maps has become an eyesore fastcompany.com/90930810/... · Posted by u/nkurz
Is the problem the office or the commute?
If offices, schools/nurseries and housing are all within a 20mn cycle radius the question of remote or in-office work becomes different
WFH, everything is in a 5 minutes car or 15 mins walk radius for us. The office would be 1h+ of commute away. And all that just to go there and put noise cancelling headphones to concentrate on my work.
But it's not only that. Kids need more than just being transported, fed and put to bed. You need to rush home to cook, do chores because you didn't have time to pick up the mess in the morning, take care of them. Then once they are asleep, more chores, and then your free time starts at 9-10pm, until you crash.
Being at home, especially flex time, nothing prevents you from doing laundry, and because you eat at home, you can do a bit more dishes after lunch, start cooking something for supper, etc. It alleviates my routine a lot and I also work more time with less stress.
RIP.
The only thing MS Teams has going for it is that it is included in Office 365 subscriptions. That's it.
It's a garbage product that's slowing even the fastest computers down to a crawl. And don't get me started on all the bugs. Horrible.
Then again, the calendar/video call is great, but once I'm back in Teams, I can't video call someone on the web version.
Interesting timing.
2 days ago a place I'm at switched us from Google mail + calendar + meet to Microsoft outlook + calendar + teams.
I almost can't believe at how good Google's suite of tools are compared to Microsoft. I never used any of MS' office tools until a few days ago.
Outlook's web app doesn't even let you click into an email to mark it as read. You have to explicitly click the mark as read button. It also doesn't intuitively support filters with emails that have + in their name (each email ends up being unique instead of Google doing the more expected thing of letting the filter match all + variants). It also doesn't update its title bar with a count of emails in your inbox. That's things I discovered after using it for about 10 minutes.
Microsoft's calendar is designed so poorly, there's so many quality of life things that aren't there vs Google. There's too many to list but the biggest one is not being able to see the calendar details of team mates when inviting them to an event. All you see is a blocked out amount of time, you can't see their exact schedules even if they shared their calendar with you. This removes a huge human element to scheduling meetings because often times I'll avoid scheduling meetings when folks are just getting out of a long meeting, or I'll buffer it by 15-30 minutes depending on who is doing what beforehand.
I'm not not looking forward to the day when we'll need to use all of MS' tools to replace Google docs + spreadsheet and Slack.
I think the worst part is their authentication, for some reason I have a personal account that was invited as a guest in an organization to use Teams. I can only access the Teams workspace if I click through a link in my emails and I have to login twice. It only works on the web version, I can't login the app at all.
But once you're in Teams, everything is so much worse, it's like using a hacked version of MS Word to chat. But where Slack actually shines is around the workflows, automation and bots, I don't think Teams has much of that.
@geerlingguy had a way worse experience recently.
>Erlang style, where we embrace failability of both hardware and software and explicitly design programs to be resilient to partial faults.
>SQLite style, where we overcome an unreliable environment at the cost of rigorous engineering.
I don't think that the way this contrast is illustrated is nearly as helpful as the author intended it to be. Based on my prior knowledge of Erlang and SQLite, I can reconstruct the idea that the difference is that Erlang tries to build a "reliability layer" below the software, while SQLite builds lots of checks and self-correction into the software. But if I didn't already know that, the quoted lines would leave me hopelessly confused.
And also the billions of tests they run against every builds!
https://www.sqlite.org/testing.html
I enjoyed the CoRecursive podcast with Richard Hipp, it's fascinating.
https://corecursive.com/066-sqlite-with-richard-hipp/#billio...