Recent submissions

Comment · 2 months ago
For tracking in general you need a system and a medium. The bullet journal method has worked well for me for many years. The systems and structures within the bullet journal change over time, but you can jump back years, and see what you were thinking at the time. More recently I have been using GTD within the bullet journal framework. I highly suggest reading at least those two methods before building your own system.
Comment · 6 months ago
Comment · 7 months ago
Location: San Jose, CA

Remote: yes

Willing to relocate: no

Technologies: HTML, C, React, JavaScript, TypeScript, Node.js, Express, CSS, Claude, Bash, AWS, career in patents, but looking to branch out; specialization in finding white papers and related documents on any topic

Resume:

  - Examiner at USPTO (9/14/2020 - Present)

  - Software Dev at Structure.io (5/21/2020 - 9/11/2020)

  - Student Founder at Startup School (8/20/2018 - 11/5/2018)

  - Associate at Hickman Palermo, LLP (6/02/2014 - 1/1/2017)

  - Associate at Mitchell + Company (5/22/2013 - 5/30/2014)

  - Law Student at Golden Gate University School of Law (9/1/2010-5/1/2013)

  - MSE Student at Georgia Institute of Technology (9/1/2004-5/1/2009)
 
Email: [email protected]
Comment · 7 months ago
I get that, but right now, if you traverse each "console", you end up with a list of 28 trusted "small web" links. The project grows in value if that list gets bigger over time either by you personally adding nodes or the community adding nodes. I don't really have a way of knowing if you are intending to add more links to your console (thus growing the project) or this is a one and done type of system.
Comment · 7 months ago
I love this as a concept. The wander button is great, but it still needs some curating to decide what pages you like, and getting to the actual content. I guess I'd like to know the workflow moving forward? Just re-download the repo every couple weeks, and diff to see what new sites are on the list?
Comment · 4 years ago
I like what the article is going for, but I would prefer to have the actual const { parentPort } = require("worker_threads") code and everything below it at the top. Everything else is fluff.
Comment · 6 years ago
Comment · 6 years ago
I built a tool to do this and supported it for 6 months, but I couldn't really find users. The basic idea was a web page that you could collaboratively work on through a server running socket.io, which included editing css, fonts, and the content of the website. The collaborative idea sounds cool, but in practice, it seemed easier to have a team pair program on a zoom call and edit a page live with google dev tools. Is there a reason this solution doesn't work for you?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton