sigfubar

Is it all vibe coded? Looks and feels like LLM slop.

[flagged]

I’ve learned so much, and it took only a few minutes. What a treat.

I had no idea about masking, even though I’ve been doing it for as long as I remember being alive. Aaaah, it’s so draining. When I was younger (in my 20s) I used to think there’d come a time when I’d finally come out of my shell. I’m pushing 40 now, but the shell is only thicker, the cave deeper, the walls taller. Instead of dreaming that one day I’ll be “like everyone else”, I’m contemplating the day I’ll cease to exist. Funny.

In the US, we can learn a lot too.

Alas, American exceptionality as part of its premise precludes any act of learning from anywhere other than itself. Culturally, this is what inbreeding looks like.

I get a good chuckle out of these articles. “Here’s another thing I lack that was supposed to make me live longer!”

Speaking of living longer: I’ve had my fill of fast cars already, but how about an airplane? I watched some guys fly Piper Cubs in Alaska. That looked fun as hell. https://youtu.be/XXuIA_b35fs

Perhaps I’ll buy one of those. They aren’t so expensive.

The repo is 100% AI slop.

Advice to OP: lay off the Claude Code if your goal is to become an “independent researcher”. Claude doesn’t know what it’s doing, but it’s happy to lead you into a false sense of achievement because it’ll never tell you when you’re wrong, or when it’s wrong.

LinkedIn is for those who don’t have a GitHub. My work speaks for itself; if it’s somehow not enough, the company isn’t worth my time anyway.

We just got back from watching the launch in person from Cocoa, FL. It seemed as if ten thousand people have come out to watch the rocket climb up. Everyone cheered hard, and spirits were unbelievably high despite traffic and rain.

fly literally every employee out once a quarter and throw a giant party

Please don't! I love working remotely; but I don't want to travel for work. I don't need a party. I don't need a fancy offsite. I don't want to spend a week with colleagues in some ridiculous tropical destination.

I want to quietly work from home, deliver quality work, get paid for it, and enjoy my life. Being forced to travel is the opposite of enjoying life.

This was my stance before the era of COVID-19... Now, I'm definitely not boarding any kind of airplanes.

It's the parents' job to teach kids how to tell junk food from healthy food; predatory apps from apps which add value; "you're the product" from "you're consuming the product". I do this with my kid, and technology is a boon for her. However, most adults aren't qualified to make the distinction between good and evil, so their kids suffer too.

For me the daily standup is a chance to be debriefed by the project manager so that they can convert my updates to actions in JIRA. It's what liberates me from having to personally interact with JIRA. In that sense the standup is worth its weight in gold no matter the format.

Such folks normally designate one property as their "primary residence", commonly defined as a place where one sleeps 183 nights out of the year. That's where one pays local taxes.

You'll end up paying New York income tax too, which is quite hefty.

There are plenty of people who moved out of NYC/SF and continued making their NYC/SF salary while working remotely from Nowhere, USA. Companies who cut pay based on locale will soon see their workforces dwindle to nothing.

Start looking for that new job before the previous one has ended. This is just a slightly next-level variation of simple networking, where you don't merely make friends all over the place, but make it clear that you'd take a better offer if one were to come along.

We call ourselves trapped.

I've worked for a certain IoT startup that at one point paid $850k/month (eight hundred and fifty thousand USD per month) for AWS usage. After about a year of full time work by a team of SREs and programmers, the bill was made to go down by half.

Recruiting new engineers was sometimes a challenge because candidates had to accept that they were joining an organization with a homegrown programming language and build system.

I got an offer from NYT in 2009, but rejected it because of the custom language thing. My interview was conducted entirely using this custom language, and the interviewers were uninterested in discussing any other technology. Even architectural questions, which I attempted to answer in terms of industry standards, were steered towards Context.

We wanted platforms that connect the world - now we’ve got them. We’ve given everyone a voice: the pedophiles, the self-harm fetishists, the terrorists. Now we’re reaping what we’d sown.

How developed can the US be considering that we have destroyed our manufacturing base and cannot even provide clean water and healthcare for our own citizens?

You failed your Triplebyte interview because you neglected an extremely important aspect of the job: communication. You made assumptions about the ask which turned out to be grossly out of tune with those of the interviewer. In the real world, engineers are often left holding the bag when other participants of the process leave out important details. It’s our job to ask questions and establish the boundaries of each problem before diving into a solution.

Good riddance! A project is undertaken to achieve some specified result, not to advance a career or learn some new tool. Don’t get me wrong: those lofty things are welcome when they occur as a byproduct of developing commercial software, but these cannot be the driving factor behind decisions that affect the bottom line.

The message is build with what accomplishes your goals and works with your team's skills.

Unfortunately most teams cannot be trusted to pick the right tool for each job without overcomplicating the planned implementation. Ego and the yearning to do “cool stuff” conspire to derail projects that could have been built without fuss using simpler tools.

If you ever find yourself thinking "If only there were a product that solves my problem XYZ? I'd pay money for that!", then you already know what to build.

If you haven't had such thoughts yet, I'm sure others around you could make suggestions. You'll make even more money by building for a niche market that has been overlooked or underserved by technology companies. The more specific the market, the better, as these tend to be quite sticky.

Good riddance! NYC is already overcrowded. Let's build some subways to non-hipster neighborhoods first, then we can talk about adding more office space.

It’s not free.

See what I did there?

I pay for Spotify. I pay for concert tickets. As far as I'm concerned, this fulfills my obligation to support my favorite artists. Digitally downloaded music is thus already inherently "paid for" and can be downloaded from any source, even if some random entity considers this source "against the rules". No moral hazard, no hassle. Just music.

Pino is an open source web app built on Drupal

closes tab

I do love me a hint of scandal, but the whole "thou shalt not BDSM in your spare time" thing is a major turnoff.

Save the Wikipedia links: surely you remember the time when database selection boiled down to "Oracle or bust". I'm not implying that S3 was first & dominant early on: I'm stating it as a flat fact.

Yes, many RDBMS offerings have preceded Oracle, but none gained such wide adoption early on. Oracle has always had a strong sales team, so they've been able to grow their business rapidly. Good for them. SQL standardization has nothing to do with it either, because SQL is the user-facing language, not a wire protocol. What travels over the wire between an Oracle client and the server has about as much to do with SQL as the S3 API has to do with XML.

In your rush to defend AWS you seem to be falling into the same trap of immaturity as the people who have assumed that S3 will always remain the one true storage layer. It is not your fault, just a sign of the times. You're part of the generally apparent downward trend in level-headed, long-term thinking among the software cadre. For your next project, I recommend that you keep in mind that proper abstractions and clearly defined interfaces are crucial for maintainability of software over the long term. Good luck!

S3 API compatibility is there because creators of open source "data engineering" tools have in the early days rushed to develop their tools around the S3 API. I can make the case that the need for a properly abstracted storage layer should have been obvious, but in that early gold rush no one would have listened to such reason. Nowadays vendors are stuck shipping S3 compatibility layers in order to avoid locking out tools that cannot work without S3.

If you think I'm wrong, imagine for a moment what life would be like if every RDBMS client in existence got written in terms of Oracle's wire protocol, back when Oracle's RDBMS offering dominated its respective market. Thankfully that parallel universe is somebody else's problem right now, but it could have happened.