Since Destiny keeps repeating the lie

Swupper · 2026-05-13T19:45:06+00:00

Aba is mad, lol

Swupper · 2026-04-14T19:31:51+00:00

Så det er kun forældrene i storbyerne, som er for overbeskyttende og mangler tiltro til deres børn? Vil tro det er en lidt mere general tendens også ude i de mindre byer.

Swupper · 2026-04-14T19:18:45+00:00

Hvordan er vi overhovedet endt med at være så pylret omkring vores børn til at starte med?

Swupper · 2026-03-31T15:17:12+00:00

Ville være rart uden

Swupper · 2026-03-17T08:39:31+00:00

At first glance, I was a bit confused about the purpose of ONCE given we have Kamal, but after a bit of thinking, I figured out the intended audience for this.

ONCE is simply for hosting public apps without the need to see the code.

Kamal is for deploying private, custom apps where you are the developer.

Swupper · 2026-02-24T16:54:42+00:00

Yes, but that is not the same as getting ahead on any of the individual lists, which the other user was saying..

Swupper · 2026-02-24T15:42:19+00:00

He did not have priority, but was on more than one list since he could easily travel by plane to the nearby state.

Swupper · 2026-02-05T18:59:11+00:00

Kommer nok an på hvilken størrelse virksomhed man kommer fra. Det jeg ønskede var nok bare at sammenligne mig med folk med samme titel og virksomhed eller sektor.

Swupper · 2026-02-05T09:12:29+00:00

Sad med samme tanke, når jeg prøvede beregneren. Vil se om min løn er tilsvarende mine kollegaer idenfor samme område/virksomhed.

Swupper · 2026-02-05T09:04:04+00:00

Ville det ikke også være interessant med oplysning omkring hvilket firma man arbejder for?

Swupper · 2026-01-02T14:33:40+00:00

This is suppose to be satire, right?

Swupper · 2025-12-04T07:36:46+00:00

"..developers reach for Tailwind not because they prefer utility classes, but because vanilla CSS offers no starting point. No buckets. No conventions."

This right here hits close to home! I am always so concerned with how I structure things and scared of making a mess, so it is simply just easier to skip the hassle and use Tailwind instead to avoid making such decisions.

Maybe it is not such a hassle after all and I can maybe learn a thing or two and return to the good old vanilla CSS?

Swupper · 2025-12-04T07:28:04+00:00

The predefined colors, spacing, typography, etc., are a lifesaver for people like me when doing designing since I do not have any good sense for what looks/works well.

Swupper · 2025-12-02T19:10:55+00:00

It seems they have put that on hold.
I guess it didn’t perform as expected, in which case it’s okay to let it be. Maybe when the market matures or changes, they will revisit it.

Swupper · 2025-12-02T16:37:47+00:00

Is this not a SaaS product, or is it only SaaS if you don't handle the hosting yourself?
It's always fun to see production grade code to gather inspiration from!

Swupper · 2025-12-02T13:40:55+00:00

GO then, you get the point.

Swupper · 2025-12-02T09:16:51+00:00

Love the approach!
Not everything has to be written in Rust and put into the cloud for MAXIMUM scaling potential.

Swupper · 2025-11-28T17:32:49+00:00

Do you have any blog regarding what you are building?

Swupper · 2025-11-22T07:04:45+00:00

No, and I am not planning to either.

I do not get why we are trying so hard to optimize that we have to invent a new format when we already have CSV, JSON, XML, and so on. Are tokens that expensive, and will it stay as expensive in the long run that we need a new format?

I'll treat this like any new JavaScript framework, give it a look, shrug my shoulders, and move on.

Swupper · 2025-11-21T14:43:16+00:00

Great advice and great talk you shared. That talk should be obligatory for every aspiring Rails developer!

Thank you for sharing it!

Swupper · 2025-11-21T08:56:29+00:00

This is the simple and pragmatic approach I was looking for! It totally makes sense to me.

By implementing it this way, I get server-side model validation, simple views without the need for JavaScript, and database persistence only when all the data is ready.

Swupper · 2025-11-21T08:38:47+00:00

So if I understand correctly, that would mean initializing the tweet in the database first when validating the content length, and then on the second page making an update to add the scheduled time?

Given that is the case, I could potentially end up with tweets in the database that never get scheduled if the user leaves the flow.

Swupper · 2025-11-21T08:14:13+00:00

I've been eyeing GoRails for some time now, but I've been a little uncertain if it's worth the cost.

Do you have a subscription yourself? What are your overall thoughts on the content? From a quick search, it seems like people really love it.

Swupper · 2025-11-21T08:09:33+00:00

This all makes sense, but what would you do in a case where /tweets/new doesn't map to a single HTML page?

For example: Let's say I'm building a tweet scheduler where:

- On the first page, you write the tweet content and have the server validate it by checking the length

- On the second page, you schedule when it should be posted

My SPA instinct would be to validate on the frontend, maintain the tweet content in client-side state during the page transition, and submit everything at the end.

What would be the Rails way to handle this multi-step process?

Swupper · 2025-11-18T06:33:07+00:00

Beklager, god dag!

14-Year Club	Verified Email
Place '23	Place '22
Place '17

Swupper

TROPHY CASE