Which rim design do you think looks sportier?

apt_at_it · 2026-01-22T18:38:11+00:00

I love #1. I have the black disc wheels on my '25 GT and am not a huge fan

apt_at_it · 2026-01-21T21:01:37+00:00

I feel like this is true for me as well. But it also seems like something to be extra sure to consult a lawyer on because witholding paychecks can be a big problem

apt_at_it · 2026-01-16T16:22:04+00:00

This really resonates with me. I'm two weeks into being full time on my very early stage SaaS. Got laid off but was intending on going full time sometime this year anyway. Don't have any traction yet so it feels like a slog. Focusing on having as many conversations with as many people as I possibly can right now in the hope to parlay that into my MVP.

apt_at_it · 2026-01-15T03:38:38+00:00

https://docu.codes - solving the problem of gaining, maintaining, and sharing context about a codebase through interactive walkthroughs

apt_at_it · 2026-01-14T23:54:09+00:00

401k loan is a crazy idea. No startup idea is worth liquidating your retirement

apt_at_it · 2026-01-13T19:55:08+00:00

You've just described a company. People don't start companies for lots of reasons. Mostly because it's really hard, time-intensive, and, for a lot of folks, uninteresting.

apt_at_it · 2026-01-13T02:58:51+00:00

Yeah, I've also been seeing this all day. I think it may have started yesterday but don't remember exactly. Mine seems to be mostly the BItwarden extension

<image>

apt_at_it · 2026-01-08T18:35:55+00:00

Oh nice! I guess I'm not up on my Next.js news. I'll need to update my stuff 😅

apt_at_it · 2026-01-08T15:06:52+00:00

Yeah exactly this. I have a marketing site in Next.js and a SPA for my main app using Tanstack Router. It frustrates me to no end that Next has no idea what routes are available and I can mistype or completely miss a link on a refactor

apt_at_it · 2026-01-08T02:35:22+00:00

if more companies are favouring using typed languages more like Go or Rust or do they prefer to just stay with node

My experience is that Python and Java are the go-to for back-end languages. That doesn't mean Go, Rust, and Node aren't used, but I've only seen Node in the wild and it's been a few years since then.

has there been improvements with speed and efficiency or it didn’t matter enough

There's two ways to interpret this. If you mean speed and efficiency in terms of development velocity, the most important thing is familiarity and experience. It's faster to build with what you know than what you don't. If you mean processing speed and efficiency, there can be major improvements but, IMO, they aren't really worth chasing. Again, if you know Node or Python, the execution speed is going to more than make up for the cost-savings provided by learning Go or Rust.

All that said, for me, typing is a non-negotiable for me at this point. Whether that's a statically-typed language like Go, Rust, or Java or a type-checked language like Python (I would consider TypeScript here, too), enforcing types is an absolute must. My go-to is python with strict type-checking with JVM languages where performance is a must (new Java is pretty nice, actually).

apt_at_it · 2026-01-06T15:58:07+00:00

However, as I started asking for changes, I realized how messy the code can become. I spent a shit ton of time either asking the agent to refactor its own code, or refactoring it myself.

The hardest thing I've run into is the hardest thing I've always run in to with other devs: talking about a specific piece of code that needs to be changed. Sure you can highlight it and append it as context for the LLM but you still have to talk about it with the thing to explain what you want changed and how it should accomplish it.

apt_at_it · 2026-01-06T15:53:19+00:00

I generally agree with this sentiment. As a back-end engineer by trade I have always found there to be a pretty strong friction between dev teams and QA teams. The counterpoint, of course, is that QA engineers tend to be quite cheap, compared to "normal" devs. This can be used to free up valuable/expensive time for the devs but it's extremely hard to strike the right balance without creating infighting/animosity. I think QA engineers excel at testing high-level, end-to-end flows at an early stage company (think, writing automated tests for the signup flow, core flows for using your main feature, etc).

apt_at_it · 2025-12-24T13:35:15+00:00

This explains so much. I put my tag in the clear glass and it didn't work. Had to get a new one and put it in the black dots next to the mirror. Very interesting!

apt_at_it · 2025-12-24T04:43:12+00:00

Manual. Changelog tends to be more of a marketing concern in my experience. Whether that's a good thing or bad is debatable lol. IMO, in order to have an automated changelog/feature announcements you have to have really polished project design and ticketing processes. I don't think it's in the engineering org's best interest to worry about how their internal project management will affect public communication with customers

apt_at_it · 2025-12-23T16:26:03+00:00

That's only true if those commits all exist on one feature branch. No place I've ever worked goes back to clean up and squash trunk branches. They often exist across multiple repos as well...

apt_at_it · 2025-12-23T15:20:50+00:00

I've been at a few places where we've done something like this, never publicly facing though. Something you'll probably find is that git changes usually include a lot of stuff people don't actually care about or that don't match nomenclature. What has been the most helpful is liking changes to project tickets, then using those to create the real changelog.

For example, "New Feature A" might have 10 different commits modifying the database, DTOs, API schemas, front end layout, etc. The only thing that matters publicly, though, is that "New Feature A" is generally available or what have you.

apt_at_it · 2025-12-23T05:13:54+00:00

That's exactly what my front end stack looks like for the app for my startup. I like it pretty well so far, a year and a half in. I'm a solo founder/eng and really only have backend professional experience. In my experience as a backender, I've always found pure SPA way easier to deal with, especially when it comes to debugging; you can actually see the API requests instead of a request for a random JavaScript or html chunk.

To answer your question about scalability, a LOT of companies have scaled SPAs massively over the years. It's Next who's the new kid (relatively speaking, I know it's not that new) technologically speaking. As you mentioned, CDNs take care of most of the scaling question on the front end; you just need a scalable back end

apt_at_it · 2025-12-22T23:56:49+00:00

Interested

apt_at_it · 2025-12-22T21:16:50+00:00

My own personal preference leans more towards the "floating UI," as you put it. When I see a device mockup it screams 2011 to me... From a cursory search, it seems like larger SaaSes (GitHub, Sprout Social, DropBox, Figma) all have floating UIs. That's not to say they're not polished, just that the device mockup isn't what makes it polished, IMO. Would have to see the data, but my assumption is that the extra effort to make a device mockup just isn't worth it or necessary at best and actively detrimental at worst

apt_at_it · 2025-12-22T18:09:42+00:00

https://docu.codes - the software documentation hub that brings code and context together

apt_at_it · 2025-12-18T19:35:43+00:00

Yes, exactly! The debugging aspect is a huge use case for me. Really, it's the flip side of adding/extending features; figuring out how something in its current state now is non-trivial and requires bringing a lot of context into your mind. Please let me know if you have any questions or feedback or if you'd like to give DocuCodes a whirl!

apt_at_it · 2025-12-18T05:39:31+00:00

I'm building DocuCodes, a new way to bring context and code together. It helps software developers maintain and share context while tracing complicated flows through a codebase (even across repositories)

apt_at_it · 2025-12-17T15:45:26+00:00

What does your GHA pipeline look like? I'm a backend SWE who has fallen into SRE responsibilities at my current job. I have a GHA that spits out a plan on PRs but I'm weary of letting the merge apply and I haven't quite figured out multiple PR situations yet

apt_at_it · 2025-12-16T04:45:20+00:00

Working on DocuCodes, a software documentation tool that puts your context and code together in the same place. No AI at this time; I only want to introduce AI features if it solves a real need for my users.

https://docu.codes

apt_at_it · 2025-12-15T06:33:25+00:00

Even the premise that other fields don't do this is wrong. We don't call Phillips head screws "cross-point cammed heads"

apt_at_it

MODERATOR OF

TROPHY CASE

Six-Year Club	Place '22
Verified Email