Mike's Linux Toolchain for 2022, and his first week with CoPilot. Then we chat about the series of choices that led us to go independent so many years ago.
Sponsored By:
- Linode: Receive a $100 60-day credit towards your new account. Promo Code: linode.com/coder
- Tailscale: Tailscale is the easiest way to create a peer-to-peer network with the power of Wireguard.
- System76: Receive the Tinkerer’s Toolkit which includes an iFixit Minnow with your computer purchase until the supply of Tinkerer’s Toolkits runs out!
Links:
- Michael Dominick on Twitter — Is this tweet too corny? ;)
- Matrix Meetup Space
- Calagator — Calagator is an open-source community calendaring platform.
- My Linux Toolbox '22 - dominickm.com — I got some request for what my work stack is like on Linux compared to what it was on macOS. Some of these applications I use on both systems but am listing anyway because they have some feature that facilitates that.
- Junction: Application/browser chooser — Junction lets you choose the application to open files and links.
- Check out Fountain a Podcasting 2.0 App — Send a boost into the show with Fountain.
- Grab a New Podcast App — Check out the Podcasting 2.0 compatible apps with new features and Boost support.
@kaas_peeland
3,690 sats
7 Jul
thanks
@thegoldendragon
2,222 sats
6 Jul
Clippy for code, great analogy! That does make more sense. I was less end of open source, more, code paranoia? i dont know. Anyway, what has driven you to a web terminal versus sonething like Alacritty? My guess would be to check program compatability? Thanks for the show!
@ibuki
1,050 sats
7 Jul
[1/2] My feeling is that as a developer (especially junior) you should devote yourself to read documentation and understand what you are writing more, not having it written by a bot and thus having to understand it less. If abused this copilot thing can have an impact on software quality and security, at least until it becomes so good to completely replace us.
@ibuki
1,050 sats
7 Jul
[2/2] "Isn't it as bad as copypasting from S.O.?" ...almost, but at least there you have to a) understand what you want to solve, b) read an explanation of the solution (usually well written) c) do the effort to adapt the solution to your specific code. Lazyness rarely brings to excellence. My two sats. Thanks for the great show.
@ltguy005
611 sats
6 Jul
@kpovoc
474 sats
6 Jul
Next Episode club! Thanks for all that y’all do!