trevor-e

Because there are plenty of devs who take the output, actually read if it makes sense, do a code review, iterate back and forth with it a few times, and then finally check in the result. It's just a tool. Shitty devs will make shitty code regardless of the tool. And good devs are insanely productive with good tools. In your example what's the difference with that dev just copy/pasting from StackOverflow?

This has me very curious! How did you decide on eliminating wheat and sugar? Or did you cycle through various eliminations until you found a combination that worked? And how did you know when to keep going/stop?

What are the actual rules/laws about scraping? I have a few projects I'd like to do that involve scraping but have always been conscious about respecting the host's servers, plus whether private content is copyrighted. But sounds like AI companies don't give a shit lol. If anyone has a good resource on the subject I'd be grateful!

Uh, probably the man page for the CLI and the official documentation at https://www.ffmpeg.org/documentation.html

Yea agreed, these kinds of websites feel obsolete now with LLMs. I just tried a couple in ChatGPT and it worked flawlessly.

fyi the pricing page has a typo for "Singel Sign-On"

Yea, that's the exact point I'm trying to make. And I'm getting very similar vibes in this post with folks refusing to use LSP.

This thread is certainly eye opening. It reminds me of a post I saw somewhere, maybe on Reddit, where someone was describing their experience working as an intern at an old-school tech shop. All of the developers there were hardcore Vim/Emacs users with 20+ years of experience.

The intern was tasked with a large-scale refactoring of some modules which the senior devs estimated would take months of work to complete. After shadowing a senior dev to get an idea of the work involved, they realized the dev was literally string replacing a lot of the code, hence why the estimate was ridiculously long. The intern instead loaded the project into IntelliJ and used the built-in refactoring tools to get the task done in a couple days. This caused a bit of an internal shit-storm with the product owners because the intern made the devs "look bad".

The downvotes I'm assuming are because you replied 303 words to a simple question, with the actual answer at the very end which is frustrating to readers. Not saying what you mentioned wasn't interesting though.

I thought the exact same thing, especially since one of the main selling points is around self-hosting which I thought was for the file syncing.

This is really neat but of course ripe with copyright abuse. It was very happy generating some Super Mario Bros variants for me. xD

I came across a similar issue when experimenting with the Crystal language. I thought it would be fun to build a simple web scraper to test it out, only to find the default HTTP client fails to parse many cookies set by the response and aborts.

The property access is looking a lot like Swift, particularly the `private(set)` part which I haven't seen in many other languages.

I think it depends entirely on the product/audience. The selling points around infrastructure tooling are stability and reliability. Zany marketing like this invokes an "unpredictable" feeling in me which I'm not sure is a good fit.

To be fair to Republicans, we definitely didn't learn about this today. They've been consistently pushing this issue over the last eight years (build the wall) and crafted a narrative that the Democratic party did absolutely nothing to get ahead of. And it turns out the minority voters that the Democrats rely on, many who came here legally as immigrants, don't like illegal immigrants "cutting the line", regardless of how true any of it is.

A great example is the viral marketing Republicans did where they went house to house in largely blue towns asking when they'd like their shipment of an illegal family to house.

fwiw I was very confused with what I was supposed to do on this site and I run a few websites using Tailwind colors. I don't really get how the color selector on the right interacts with the mock previews on the left. It also wasn't obvious I'm supposed to hover over each element in the mock preview.

Thanks for the 12 Factor tip, makes sense.

As someone new to Docker, the thing that is never answered (including in this post, the irony of the title...) is what an actual dev workflow looks like.

Let's say I'm working on a web app. I start my container, awesome. Now I make a code change. What do I do? Since the code is copied in the container, do I have to stop, rebuild the image, and start again? Or does it automagically rebuild like most frameworks support? And how about debugging, are there any hoops to jump through connecting a debugger to a container? And what about the filesystem. If I need to inspect the output of something, say a log file in the container, is that easy to do? I've tried this before and got pretty lost trying to access the filesystem.

None of these questions are obvious to Docker beginners like myself. We get the whole "consistent environment" benefits of Docker, now talk about a practical workflow please. :)

edit: thanks for the answers!

Very surprising this page doesn't mention loco.rs which seems like the most "Rails" Rust framework out there.

I've been going down the VPS rabbit hole lately since I have some toy projects I want to host and really don't like the unpredictable pricing model of these "pay as you go" providers like Vercel. E.g. I really love Supabase but it's hard to justify jumping straight to the $25/month plan in combination with Vercel costs.

I was surprised how extremely easy it is to get set up with Coolify on a Hetzner VPS, which has preset install options for NextJS + Supabase + Posthog + many others. And I get the standard autodeploy on commit functionality. The open-source versions are missing some features, and I don't get the slick Vercel admin interface, but for a pet project it works great. I'm also by no means a sysadmin expert, but with ChatGPT it's pretty easy to figure things out now.

Which begs the question of why they don't rearrange that part to the first in the error message. Like you said, 9/10 times I scroll down without thinking which is silly.

Not OP but have the same frustration, and no a video would not be helpful. Let users maybe view the first N items of an itinerary before requiring an account to see the full thing. As-is I have no incentive to sign up for an account because everything interesting is account-walled.

Nice, so Rails does work well with Cursor? I'll give it a try then. Like you said, maybe it just struggles on random Ruby code but not Rails which has a ton of existing examples to go off of.

I really want to try Rails, but the main selling points to me were the fast scaffolding and opinionated structure. With the advent of AI editors, are these points still relevant? Last I tried, CursorAI struggled with Ruby due to the lack of types. It seems like nowadays you can be nearly as productive with Node + Typescript + Cursor.

edit: care to explain the downvotes for asking a question?

I tried using https://www.tavus.io/ and it worked at first, but after 40 seconds the guy just kept blinking and twitching at me and became unresponsive to further questions lol. Pretty neat though.

Sure, being the top 1% of employees (which I'm assuming L7 principal is) at any company is sure to be great. Very few engineers will ever make that position at a FAANG.

Yea there's a huge element of randomness to these kinds of interviews. I wasn't a big fan of them at Stripe. You can get some signal like:

- do they methodically approach the problem? - do they understand the bug? - do they know how to use debugging tools? - do they know advanced debugging tools? - do they work well in an unfamiliar codebase?

But in practice I'd say most candidates check those boxes, at which point it becomes an arbitrary evaluation unless you pass/fail them based on whether they solved the bug.

From what I remember (left Stripe in late 2022) much of Stripe's codebase was/is a Ruby tangled "big ball of mud" monorepo due to lack of proper modules. Basically a lot of the core modules all imported code from each other with little layering so you couldn't deploy a lean service without pulling in almost all of the monorepo code. And due to the way imports worked it would load a ton of this code a runtime. This meant that even a simple service would have extremely high memory usage and be unsuitable for a local dev environment where you have N of these bloated services running at the same time. There was a big refactoring effort to get "strict modules" in place to cut down on this bloat which had some promising results. I'm not an expert in this area but I believe this was the gist of it.

I wouldn't say that's true, I personally find Go code more confusing to read than the average language. For example:

``` func (r rect) area() int { return r.width r.height } ```

This syntax is strange to me despite being a simple example. I can tell that it's a function that takes in a rect pointer, is maybe named area() (but I'm now confused why this definition doesn't have an argument?), and returns an integer value. I've tried reading larger Go files and constantly run into syntax confusion like this and get exhausted.

So sure, I understand the gist of this code, but this is more difficult to understand IMO than any Python, Ruby, Java, Swift, Rust, Gleam code I've read.

They tasted horrible but were cheap and would get you incredibly wired and drunk in a short amount of time. A perfect storm for binge drinking students, especially pre-gaming early in the night for other parties/bars. It was a fun time for a year or so but can understand the ban.