robertakarobin

The parent Wikipedia article: https://en.wikipedia.org/wiki/Wolf,_goat_and_cabbage_problem

Hmm. It seems like the big differences between the two are:

1) Astro is either all-SSG or all-SSR, while VPS is mix-and-match

2) Astro uses `.astro` templates by default, while VPS uses `.js` by default

3) Astro comes out-of-the-box with Typescript, Sass, etc., while VPS requires more configuration (by design)

Other than that, they seem to have fairly similar project structures and use-cases... Or am I misunderstanding?

Really interesting! How would you say it compares to Astro[0]? Astro is currently either all-SSG or all-SSR, but this quarter they're working on configuring that per -route.

[0] https://astro.build

I built the website, and also the underlying algorithm! I'm really excited about the website since it's my first project with Astro -- my new favorite SSG framework, after having tried the rest.

Happy to answer questions! :)

I've always really preferred keeping it simple with HTML/CSS/JS and find most front-end frameworks to be a huge turn-off. You might like Astro (https://astro.build). I love that my sites are still 100% HTML/CSS/JS that I wrote myself. But Astro comes with Sass and Typescript support out-of-the-box (no Webpack necessary), and also makes it easy to do reusable components, scoped styles, supports FE frameworks if you want them, etc. It's the happiest medium I've found yet. :)

My 4 big reasons for wanting to leave my current FAANG:

1. I'm not learning things that feel relevant outside the company. Our build processes, templating language, version control, and even our IDE are all proprietary and internal-only. It requires a lot of work to master these things, and that mastery is not transferable anywhere else.

2. I continually scan the internal job boards, and have yet to see another position that looks significantly more appealing.

3. The amount of red tape required to make any change, while expected and understandable for enterprise software, makes it hard to feel innovative or creative.

4. It takes 2 minutes to recompile/reload after every trivial changes. This is hugely detrimental to my "flow," and this is unlikely to ever be fixed due to the size of the codebase.

After having tried and given up on so, so many SSG frameworks, I'm loving Astro. In particular:

- Templates are plain HTML/Javascript, instead of some other templating language (e.g. Jekyll/Liquid)

- Typescript out of the box

- SCSS out of the box

- Easy remote builds on Netlify

- Scoped stylesheets

- No overcomplicated build process/customization (e.g. Webpack)

- Supports Markdown, YAML, JSON, all the things

- It builds really quickly

And all of that is with virtually no additional configuration. It's great.

Also a big bonus: the team is super friendly and very responsive!

I used this all the time when teaching! Why, Google?

We call that a Shit Midas, where everything they touch turns to shit.

Oooh, I know a lot of Stanford (and Berkeley) students who would be extremely upset to hear you say that. :)

This is really interesting! I started my Stanford undergrad as an engineer. After my first Calculus class, I switched to American Studies because it was one of the least engineering-y majors available. Then I dropped out in my Junior year. That was over 10 years ago. Now, ironically, I work at Google as a software engineer — the only one on my team without an engineering degree, let alone without a degree at all.

I never thought of my disillusionment with engineering in the context of other students, but rather just as an absolute: "Engineering is too hard for me." Taking Calculus at not-Stanford may have led to a very different result.

Everyone experiences depression differently. SSRIs made a tremendous difference to me and my mom where therapy and various other treatments did not.

Please be careful; this attitude places the blame on the person experiencing depression, and feeling guilty about being depressed is a vicious cycle that can have catastrophic effects.

There are some for whom depression is a product of their environment. For some of those, a "tough love" approach may work. But there are also those for whom depression is a physical condition that requires medical treatment

> people will see an ocean of normal content anywhere free speech is allowed

Not sure I agree on this one. Forums like /r/conservative, patriots.win, and Gab claim to be in favor of "free speech," but dissenters quickly get banned. 4chan comes to mind — people do indeed post things of all political slants there, and the only moderation seems to be removing obviously unlawful content. And yet 4chan is almost decidedly covered in turds.

Yes, in general "free speech" platforms seem to quickly turn into Alt-Right platforms that are, ironically, heavily moderated. (Looking at you, Voat)

JLaw == Jennifer Lawrence

Hi, neighbor!

Sue a 500-pound gorilla?

I had a student who used Apple Chancery in her IDE, no joke.

Is it just me, or does it not appear to be working for anyone else? It just shows "You have chosen the winner" and none of the buttons seem to have an effect.

Edit: Clicking 'Restart Tournament' seems to spawn a worker that pushes my CPU over 100%. Open source your code, perhaps?

> they are in distress

> they just have kids

Is there a difference?

Not, honestly. I'm sure it depends on the company.

Eh, it's just people being people. It's similar to how when you're learning first aid, they always tell you to not say "Someone call 911!" but rather point at one specific person and say, "You, [distinguishing characteristic of said person], call 911!"

Put OP out of a job, why don't you!

Try being a product manager of a web service at a big corporation. I stopped and went back to programming because of how little there was to do. You said you don't want to manage people, but in my experience all I had to do was:

- E-mail calendar invites for a meeting

- Show up to said meeting

- State the topic, point to an engineer at random and say, "What do you think?"

- Zone out for the rest of the meeting, zoning back in only if it sounds like the conversation is starting to get off track

- 5 minutes before time is up, say, "OK, it sounds like we're agreed that we're going to do X?"

- Go back to coding side-projects

It's a funny job, because even though it's very easy to coast, it's also fairly high-visibility and in my opinion very necessary. Without a dedicated person to spend 30 minutes a day watching over meetings, things seem to very quickly go off the rails.

Other standard DOM methods like what? getElementById and getElementsByClassName?

In my opinion, it's not about knowing all the core areas of CS — it's about being OK with the unfamiliar. It's about being confident that if someone hands you a problem outside your comfort zone, you'll be able to search for and find the answers necessary to solve the problem.

I'm a senior engineer, but have never taken a CS class, and have never been able to get past page 1 of any programming book. Possessing knowledge isn't what makes me successful at my job. There is simply far too much knowledge required in this job, and my memory is too sketchy, for me to learn and retain all of it. What makes me successful is that (a) I have a good grasp of how to break projects down into little manageable tasks, and (b) I'm really good at Googling.

For this reason, I do believe that anyone can do it, where the "it" that is being "done" is thinking things through and looking up information, not understanding the ins-and-outs of algorithms and data structures and electronics.

What you're describing is the reason impostor syndrome is so prevalent in the tech industry. Because programming is such a tremendously deep area of study, there will always be people who know things you don't, and this can make one feel inadequate. We're raised to think that being an expert is the same thing as knowing lots of things. In the development world, being an expert is more about being comfortable with what you don't know.

Not necessarily. My twin boys who just turned 3 are identical according to a genetic test, but were in different sacs with different placenta. This is uncommon, but not THAT uncommon. I think it's not unreasonable that they would have received different amounts of chemicals. They are certainly very similar, but have many differences, and were a pound apart at birth.

Just want to chime in that I, too, am mystified by the Ikea hate. I've spent all of my 30+ years living with Ikea furniture. I'm writing this from an Ikea kitchen cart that has become my primary workspace. I remodeled my kitchen last fall with Ikea cabinets -- and was able to do almost the entire installation myself.

I've never had a serious problem with anything from them. The same cannot be said most of the furniture we've gotten from other places. The expensive, fancy-shmancy reclaimed wood dresser and nightstand my wife bought from some other chic retailer has been repaired about 4000 times.

Why not both?

Isn't this taking things to a logical extreme?