romanhn

I built a React SSR app on Vite using Vike (https://vike.dev), it worked well enough for my simple needs. Best part was I was able to easily reuse a bunch of components from the primary React SPA app that lives side-by-side in the same project without needing to buy into the "Next.js way".

You can do this by either hitting the favorite link or simply upvoting. History of both is retained in your profile (difference being that favorites are publicly visible).

This is incorrect, they absolutely do Leetcode and Leetcode is full of questions cribbed from FAANGs.

I'm working on https://rolepad.com - a platform for managing your job search (rather than searching for jobs directly).

Presumably their role is not to sit in meetings all week and there are actual expectations of delivery. If you just shrug your shoulders and tell your manager nothing got done again because too many people booked meetings with you - don't expect to last long there. Your time management is on you. Working overtime is one way of dealing with this, a bandaid, but a common one. What op is trying is a way better approach and I think deserves props. Others' demands on your time only get worse the more senior you are.

FB employees used to be able to help with these types of requests, but unfortunately some time ago they changed their policy and an employee may only help their relatives or close friends, and must personally vouch on their behalf (this was true a couple of years back, not sure if anything changed). Basically, that loophole is closed for all intents and purposes :(

Interesting to see this here right after finishing six of his novels. My takeaway is that Egan clearly is a talented scientist, a man of unique ideas, and not a very good writer. The books are an excuse to go into scientific minutiae, with plodding storylines and two-dimensional characters. Kept going mostly because the ideas/set-up were fascinating.

I glanced at the two links you shared and I wouldn't call those architectures boring, in fact they're quite involved. "I personally can't even answer with confidence what a single reasonably fat server can handle" - this is too ambiguous of a question anyway, since it depends on the workload. HN still runs on a single server, for instance.

The good news is you should stop worrying about this stuff, and just build. You'll eventually run into bottlenecks and can address them then. That's how best learning happens anyways. Premature optimization is fun and intellectually stimulating, but rarely gets you closer to delivering value.

My rules of thumb for starting out:

  - Start with a monolith (microservices are great for certain problems, but it's very unlikely you'll have those problems in the beginning, and they add quite a bit of complexity)

  - Use a relational DB (same caveats as above for NoSQL, RDBMS can handle search well enough early on as well)

  - Use managed services as much as possible (cloud > managing your own hardware, RDS > managing your Postgres instance, etc). They typically have sensible defaults, provide greater security/scalability/availability, and let you focus on the product.

  - The fewer independent moving parts in your architecture and infrastructure, the better. Let the complexity add over time, as needed.

HN is built on Arc, a dialect of Lisp and runs on a single box. More details here: https://news.ycombinator.com/item?id=28478379

Foundation series is my favorite. Read the Robot and then the Empire series by Asimov which are all set in the same universe as Foundation. Not as good, but there will be some pleasant surprises.

Dune and sequels by Frank Herbert are the next logical option, with similarly large scope.

The Expanse series by James S.A. Corey is great, set in the solar system in the near future.

Andy Weir's Project Hail Mary and The Martian are super fun reads, technically fulfilling the "not on Earth" requirement. Both are about one person's overcoming great odds, so a very different brand of sci-fi.

Base62 is fantastic for URL-friendly encoding. I use GUIDs for primary keys in my web app, and encode them for frontend consumption using Base62. Looks much neater and doesn't cause issues like Base64 extra characters might.

Worked at a company that used this pattern about 15 years ago. We had a homebuilt ORM that codegen'ed these stored procs. If I recall, stored procedures were faster than straight up SQL at one point, but that hasn't been true for a while (same perf characteristics these days). Nowadays it feels like unnecessary overhead. I also like to keep code in the application layer, so try to avoid stored procs if I can. Any reasonable backend framework/ORM should prevent SQL injection so I don't find that to be a compelling argument either.

"Why would anyone hand code a website?" - a FrontPage user in the 90s

PagerDuty: https://news.ycombinator.com/item?id=758653

This was shown during the 2003 Comdex trade show. Sadly, the full version has never been released. Hilarious look at Microsoft's attitudes at that time towards open source. There are a bunch of other spoofs they made, but this one stuck with me the longest.

I was using it for my project because the workflows required access to VPC resources (the database, etc). It worked... ok. There would be times when the runner didn't start, or parallel runs would not work, felt a bit random. Possibly was my config, there were quite a few knobs and dials.

Eventually I stumbled on the idea of running the VPC-requiring commands from an AWS CodeBuild script, and invoking it from a workflow executed on a GitHub-owned runner. Works beautifully and I was able to remove a ton of complexity from my infra that this Terraform module adds.

How is inheritance baggage? If you don't need it, don't use it. Not sure I understand the aversion to OOP.

I wouldn't worry about it. There are tons of reasons for lack of response that are more likely than this kind of backchannelling, i.e. the tough job market, and end of year (new reqs likely to open in January). And fear of legal consequences generally keeps companies from oversharing on employee matters anyways (though I could see inexperienced founders not adhering here). Anyways, good luck, I think it's just the timing here that's not ideal.

The first and last step for so many projects :)

"Still practicing" is as good an answer as any

Continuing to hack on https://rolepad.com, a free job application tracking app. Currently working on the employer side to allow greater visibility into application status for both parties and hopefully lead to less ghosting.

Another favorite bug investigation of you're into this sort of thing: https://www.pagerduty.com/blog/the-discovery-of-apache-zooke...

Depends on perspective I suppose. Lots of people in Russia, for instance, feel this way about Gorbachev. Putin even denied him a state funeral.

At the risk of sounding like a broken record, but "use what you already know" is almost always the right answer for these types of questions (especially since I didn't see "learn new tech" on the list of priorities). This is why every answer has a totally different stack and probably won't help you all that much.

We must have seen different movies, because this one didn't showcase any of his genius. Instead, they opted to show an unambitious little man (not talking about his height) whose fortunes are pushed forward by others rather than himself. Very odd indeed.

I agree with you as far as inactive accounts go, but these TOS terms are typically targeting accounts that are in violation of some rules. Did you experience this or are you worried it might happen? I've usually been notified way in advance if inactivity was going to result in account suspension (only happened once as far as I remember, so not exactly a frequent occurrence).

Why is this surprising? Should a service be forced to keep accounts running in perpetuity? I think this is pretty standard TOS language applicable to pretty much every service in existence (including those that don't explicitly state it).

I'm exactly the same. What helped me was Tailwind + commercial TailwindUI library, which was more than worth the money. I just used the pre-built components for both the application and marketing site, and over time started to iterate on my own. I still wouldn't be able to build something that looks good from scratch, but I find evolving an existing good design to be much easier. Got many compliments on my app's UI, which is funny considering how non-intuitive I find design to be.

My general perception of "thought leadership" is that it's not particularly amenable to changes or self-corrections (lest you start losing your adherents). In that regard, my imagination paints a different picture.

Reputational, for one. For years he has lauded Altman as one of the best and brightest minds out there, playing a major role in Sam's meteoric growth.