The last few years (at least) have brought uncertainty and disarray to jobs in all sectors. I see a lot of comments & threads, here on HN and in other areas, about dysfunctional, difficult workplaces. The responses in these discussions are often full of support, empathy, and very knowledgeable takes on how to improve things. These responses are often coming from those who have earned a lot...
I got a cheap bedroom sublet through a former recurser and sublet my own place back home.
not your comment, but some replies below make it sound like RC would be otherwise, full of rich kids or "retreat" types maybe, but it's the opposite.
leaving work, paying NYC rent, yes it's all expensive but places like RC that create free spaces like this are part of the solution
I love the simplicity of using existing tools in this post. It would be nice to have something similar that would allow for adding online comment threads on a diff, and output it to a simple markdown file. Of course, I'm thinking about a local agent workflow here.
But I also agree that this has limitations. If I were to challenge you and say that Obsidian solves this, or gets close to solving it, what gaps would you say were left unfulfilled?
I am because I'm working on something in this space and your comment touches on my three main ingredients: text files, SQLite, and graphs.
"[1] When computing LOC, we strip blank lines and break long lines into many"
One book I cannot recommend enough is Finding Meaning in the Second Half of Life by James Hollis.
Listen deeply to yourself, be kind with yourself. It's so very hard but so very very rewarding.
Getting a little meta here .
If we were to consider this with an economics-type lens, one could say that there is a finite-yet-unbounded field of possibility within which we can stake our ground to provide value. This field is finite in that we (as individuals, groups, or societies) only have so much knowledge and technology with which to explore the field. As we gain more in either category, the field expands.
Maybe an analogy for this would be terraforming an inhospitable planet such as Mars - our ability to extract value from it and support an increasing amount of actors is limited by how fast we can make it habitable.
the efficiency of industrialization results in less space in the field for people to create value. So the boundaries must be expanded. It's a different kind of work, and maybe this is the distinction between toil and creative work.
And we're in a world now where there is decreasing toil-work -- it's a resource that is becoming more and more scarce. So we must find creative, entrepreneurial ways to keep up.
Anyways, back to the kitchen sink -- doing our dishes is simply not as urgent as doing the creative thing that will help you stay afloat. With this anxious pressure in mind it makes sense to me that people reach for using AI to (attempt to) do the latter.
AI is great at toil-work, so we feel that it ought to be good at creative work too. The lines between the two are very blurry, and there is so much hype and things are moving so fast. But I think the ones who do figure out how to grow in this era will be those who learn to tell the distinction between the two, and resist the urge to let an LLM do the creative work for them. The kids in college right now who don't use AI to write for them, but use it to help gather research and so on.
Another planetary example comes to mind -- it's like there's a new Western gold rush frontier - but instead of it being open territory spanning beyind the horizon, it's slowly being revealed as the water recedes, and we are all already crowded at the shore.
These two solutions look feel and smell like the same thing. Are they the same thing?
Any OpenCode users out there have any hot or nuanced takes?
I haven't used Claude Code, but recently switched to OpenCode. My token usage and cost is a lot higher, I'm not sure why yet, but I suspect Aider's approach is much more lean.
When a working branch falls behind main, I prefer to rebase it instead of merging from main to keep it up to date. However, if you've already pushed your working branch to a repo, after rebasing you need to `git push --force` - which is a problem if there are others who have previously cloned the working branch.
`npx no-masters`https://github.com/good-idea/no-mastersI spent my 4th of July putting together a one-line command that changes your default branch from `master` to `main`, and optionally:- Deletes the local master branch - Updates the origin's default branch to main - Deletes the origin's master branch - Updates your local git config to use main as the default branch when using git initI know...
Full-stack javascript & typescript developer
Skills: React, Redux, GraphQL, Node, TDD, Headless CMSs
I've been working for 8 years as a freelance full-stack developer. I have extensive experience creating boutique UX and working with clients in the creative media industries (artists, designers, musicians, a record label), startups looking building an MVP (e-commerce marketplace, social, education), and e-commerce (stripe, shopify, and more).
I maintain several open-source packages, have managed teams of developers, consult with designers, and have taught beginner to intermediate React courses through General Assembly.
Website: https://www.good-idea.studio
Email: [email protected]
Github: https://www.github.com/good-idea
Twitter: https://twitter.com/typeof_goodidea
Location: Los Angeles
Remote: yes!
Technologies: Node.js, typescript, graphql, React, PostgreSQL, graph databases, web sockets.
Résumé/CV: https://docs.google.com/document/d/1QZFT_miF9MGO42JnS1P43Kra9DKwjRKY23HpxkYhQIk/edit?usp=drivesdk
Website: https://www.good-idea.studio
Email: [email protected]
Location: Los Angeles
Remote: yes!
Willing to relocate: no
Technologies: Node.js, typescript, graphql, React, PostgreSQL, graph databases, web sockets.
Résumé/CV: https://docs.google.com/document/d/1QZFT_miF9MGO42JnS1P43Kra9DKwjRKY23HpxkYhQIk/edit?usp=drivesdk
Website: https://www.good-idea.studio
Email: [email protected]
Then, I'd end up with a stack of index cards for each book, which I'd keep for reference. I rarely looked back at these notes, but the 'chore' of doing this for every chapter really helped the complicated stuff sink in.
I don't see anything in the docs about supplying an unsubscribe link. I don't see an endpoint in the API that could be used with an anchor tag in the footer of the email. Is this something that is supported?
And: my client is concerned about email/spam regulations, which I'm very unfamiliar with. Is there anything I'd need to look out for in this regard?