"What I had been calling “Linux knowledge” was actually two different things bundled together: understanding of how systems work, and familiarity with where things live on a particular filesystem. The first transfers perfectly to NixOS. The second becomes largely irrelevant, and whilst that felt like a loss at first, I now think it is fine. Knowing that configuration files live under /etc is useful context, but it is not deep understanding. Deep understanding is knowing what the configuration does and why, and that knowledge is entirely portable."
Particularly:
>> "familiarity with where things live on a particular filesystem."
Taken in context with mightyiam's quote:
>> "because I get to keep it, share it across multiple computers, "
It seems to me like a primary advantage of NixOS is that familiarity with where things live on your particular filesystem is made to be portable across machines, and not a constant beachead.
Today I vibe coded a webapp that is simultaneously capable of being hosted for free on github pages, uses a 22mb model (small enough to run in browser) to do semantic search across any 2 pdf's uploaded, and only took 1 working day to build.
- you don't come back every month for the next three years advertising the same job without hiring anyone for it
Placing a $100 bounty for anyone who can extend the "HN Hiring Pro"(1) extension with an adjustable filter to remove posts by companies that also posted last month, 2 months ago, etc.
This could be a product. I'd pay for an app that fwd'd messages from other apps and gave me a wikipedia feed to scroll on the elevator / other places where the phone is a social respite
The only AWS service I still use is SES, for sending emails from client applications. Surely that can be self hosted? Can anyone reccommend a competitor?
Location: Seattle, WA
Remote: Yes (Remote / Hybrid / In-Office)
Willing to relocate: Yes (would prefer to relocate)
Technologies: Full-stack web (Postgres, Express, React, Node), Cloud infrastructure (AWS, GCP), Browser automation (Selenium), Windows desktop apps (Tkinter, PyInstaller)
Résumé / Portfolio: https://www.douglasmckinley.com
Email: cadocary@gmail.com
Seattle-based full-stack engineer open to remote, hybrid, or in-office roles. Willing to relocate and actively interested in doing so.
My experience spans production full-stack web applications (Postgres, Express, React, Node), cloud infrastructure on AWS and GCP, browser automation using Selenium, and Windows desktop tooling with Tkinter and PyInstaller.
I’m currently operating as a consultant, working across technical implementation and customer-facing responsibilities, and I’m comfortable partnering closely with sales and non-technical stakeholders. Clients range from startups that nobody’s heard of to aerospace manufacturers that everybody’s heard of. I’m happy to sign NDA’s and bill against PO’s, but I would prefer a full-time W2 role. (https://cadocary.com)
Earlier in my career, I worked in electronics and hardware, including DO-160 compliant aircraft electronics testing, circuit design, and electrical bench tools. More recently it’s fullstack webapps and AI wrappers, including training and deploying own models, specifically supervised classification. My most recent W2 position was as a Patent Examiner in AI (Art Unit 2121) at the USPTO.
A defining part of my background is teaching computer science at Central Washington University. I taught nearly all core CS degree courses, authored four original courses that were added to the official catalog, and earned the highest student evaluation scores in the department across all quantitative metrics.
Student evaluations: https://drive.google.com/file/d/1zb9vbd4TYhYxqA_o_aZVg7-nIWm...
Let's assume good intent and that the problem came up without foreknowledge of the solution (which I think is endemic whether or not it is the case here)
How would you reccomend someone discover/decide is faster to learn/learn/implement existing solutions?
I'm asking because I'm currently in my "cambrian explosion" phase of homelabbing, so implementing that loop for myself personally will pay dividends.
Particularly: >> "familiarity with where things live on a particular filesystem."
Taken in context with mightyiam's quote: >> "because I get to keep it, share it across multiple computers, "
It seems to me like a primary advantage of NixOS is that familiarity with where things live on your particular filesystem is made to be portable across machines, and not a constant beachead.