saysjonathan
0: https://www.ifixit.com/Teardown/iMac+Intel+27-Inch+EMC+2309+...
1: https://www.ifixit.com/Teardown/iMac+M3+24-Inch+Teardown:+Ap...
I would love to see more interpreted languages offer shells with native constructs for operating as daily drivers shells (not just REPLs). When I first started learning Ruby I used `rush`[0] as my main shell. Being immersed in the language, even if there were a few helpers for shell operations, really helped me reason better about Ruby and think in the language. `scsh`[1] was enlightening as well. Ultimately the ergonomics of both pushed me back to more conventional variant but they were really helpful learning mechanisms.
0: https://github.com/adamwiggins/rush 1: https://github.com/scheme/scsh
I've had mixed results overall. Primarily looking at senior+ TPM, TPGM, SI roles. My network is hard to leverage due to being remote for so long. Lots of cold applications. 25% of applications got recruiter responses within a day, 25% within a week, 50% blocked at ATS, ghosted, or hiring being re-evaluated. Not as many direct recruiter outreaches as I've received in the past.
From the JD side, salaries seem to be more stratified and requirements, even for lower roles, seems to be higher than before. I've seen quite a few requests for 10+ years experience for mid-level PGM roles. In loose convos with friends, everyone wants a big name on a resume but no longer will pay a premium to get it.
No degree seems to be a bigger gate now than it was the last time I was searching. Being a generalist also seems to be more of a risk but I'm sure that's at least partly a fault in my own framing. I do not play the LinkedIn game well. My major contributions have been either inside a company (internally-focused, hard to share publicly or company-specific), mildly popular open source dev work (>100 stars), or things actually used everywhere but no one cares because it's not "real" dev work (created puppetlabs-firewall module, 10M+ downloads, adopted as part of Puppet Enterprise, used globally, no one cares). Without a strong public profile in a specific direction, I've been told I read as too hard to quantify.
Overall, it seems "bad" in that everyone is battling uncertainty about where things are going and being more vigilant to avoid the wrong hire. Credentials and resume pedigree seem to matter more than ever and roles are much more vertically aligned than I've seen them in the past. If you're good, with some amount of credentials, and a lot of vertical ownership then you'll probably be fine though it might take longer. If you're a generalist who's hard to pin down, you might be in for some pain.
0: https://ia800708.us.archive.org/25/items/pdfy-MgN0H1joIoDVoI...
0: https://www.discogs.com/master/1664187-The-National-Juicy-So...
If you already have a robust tmux workflow with a desired layout (or lack of layout) and custom keyboard shortcuts then this may not work for you. It's just one way to manage panes/windows in tmux that I hadn't seen before and different from the usual ad hoc methods.
Like most window managers, I think it's all preference. What're your current preferences for pane layout, window management, etc? Do you always create/layout panes in the same way or is it situationally dependent?
Do I regret using `ed` as my primary editor? No.
Do I still use `ed` as my primary editor? Absolutely not.
Commit with the switch to shell here: https://github.com/saysjonathan/dwm.tmux/commit/c8752b978390...
I think there's a lot of potential to scripting terminal multiplexers in various ways and I would love to see more work exploring what's possible!
This is really just a personal project that I wanted to share in case others might like to try it.
I will add that, especially at the time of creation, I was heavily in the 'unix is my IDE' camp. A terminal window manager was a logical next step to that notion. As someone called out below, I even used `ed` as my main editor for a while (which was as bad as it sounds).
227g (94.58%) margarine
30g (12.5%) sugar, powdered
240g (100%) flour
5g (2.1%) vanilla (assuming liquid extract)
15g (6.25%) water
200g (83.33%) pecans, pieces
Show HN: Dwm.tmux – a dwm-inspired window manager for tmux
https://github.com/saysjonathan/dwm.tmux
Hey, HN! With all recent agentic workflows being primarily terminal- and tmux-based, I wanted to share a little project I created about decade ago.I've continued to use this as my primary terminal "window manager" and wanted to share in case others might find it useful.I would love to hear about other's terminal-based workflows and any other tools you may use with similar functionality.
Additionally, at least in iOS 17.5, the Recently Deleted album itself has a disclaimer at the bottom that says that “items will be permanently deleted. This may take up to 40 days.”
0: https://www.phaidon.com/store/food-cook/the-silver-spoon-978... 1: https://evanfunke.com/orderamericansfoglino
Would you use a Maple Ridge (TB4) card instead of Titan Ridge?
I am impressed with Apple's ability to seamlessly handle all of these scenarios. Their product integration really does create a great experience within their ecosystem. I didn't expect my setup to work perfectly but I'm happy it gets most of the way there. I'm not pulling the trigger on Apple Studio Display but I'll be watching progress to see if it works.
My use case is an outlier, I guess: I'm in the Apple ecosystem for all personal stuff but use a Dell Latitude for work (TB3, GPU chokes on 5k but technically works) and have a beefy Windows desktop for gaming and personal development work in WSL. I love the idea of just plugging a single cable into whatever system I'm using at that moment.
0: http://johnwilger.com/2019/01/27/lg-utlrafine-on-linux-gnome...
In a larger sense, Apple seems to be saying that, at least for consumer apps, they have an expected user flow from launch/beta through purchase. That flow makes Apple the primary channel and pipeline. If you have a multi-channel app (web + app, in this case), they want the main experience through the app regardless of business model or context. This makes the customer experience argument seem like misdirection.