I've been reading the "garage door open" posts here on hacker news, and figured others might be interested in this project. The project is just the examples in "c programming language" by Kernighan and Ritchie written in library form. I reviewed some github repos that other people have posted here on hackernews and tried to copy their style. Rather than putting "main.c" in the top directory, I put the library in the top directory, and tests with main functions just use the library. Everything in the book is likely already in <stdlib.h>, <stdio.h> or <string.h>, but it is useful to go through to see how the underlying functions work. While going through the book, I've been inspired to create a few other projects using the functions from libkr as the base. You can see those here: https://dmillerfork.codeberg.page
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)
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.
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?
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.
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?
The first site looks prettier, but the newer site actually explains the concept. You still need to work on your copy. "Point out in the description what you could do for the advertiser and how the advertiser would benefit in choosing your team" -> what? Could be a lot easier to understand. How about "Request sponsorship for your team or event"
Hi Replwoacause! Do you have any additional information on what your individual needs might be? It would be very helpful to us to know what tools you currently use, and why those tools are useful to you. We have received a lot of positive feedback and some feature requests, so we are trying to group feature requests by common use cases.
Thanks for the feedback! We are looking for more info on user needs in this space. Sounds like you currently use Alteryx + Snowflake. Any additional information you could provide about your use case/needs would be helpful. Seems like some people are more interested in open source tools that can be run on their own computer (like DBT) while others are looking for more of an enterprise use case. What about you?
When I think of a basic programming book, I think of references to a certain language or tool. If that is what you are looking for, then I wouldn't suggest reading or listening to a programming book without a computer open. If you have a certain understanding of the big picture, then there are some really good seminars out there. I love the "Uncle Bob" lectures on Youtube.