sibit

> I can’t help but look at it and see immense complexity, because I see behind the simple and intuitive userland

An idiot admires complexity, a genius admires simplicity, a physicist tries to make it simple, for an idiot anything the more complicated it is the more he will admire it. If you make something so clusterfucked he can't understand it he's gonna think you're a god cause you made it so complicated nobody can understand it.

> Unfortunately that requires skill and awareness on behalf of the interviewers;

In my experience it's mostly been laziness. Grabbing leetcode problems is easy compared to preparing a custom scenario that tests the candidates higher-order skills. God forbid they spend up to a day preparing something that could be reused for the next several years.

It may not be like everywhere but in the US most of my education (k-12) was memorization. All we did was memorize names, places, dates, formulas, or a series of steps (depending on the class) over the course of ~2 weeks then we'd be tested to see what we could remember. After the test, we'd move on to the next thing and could forget all about what we just memorized.

The only classes I can recall that required higher-order skills were some woodworking, CAD, and CNC/machining classes I took while at an off-site vocational school alongside my required high school classes.

Completely agree. I think the unofficial Steam Status[0] by xPaw[1] is a great example. I never go to the site unless I'm having issues. Between the service stats and the page views section it is really easy to confirm my suspicion that something is on fire at Valve. If it wasn't for this post I wouldn't have known that they had a minor connection issue a few hours ago.

[0]: https://steamstat.us/

[1]: https://xpaw.me/

Chalk is superior. You don't hear about anyone hoarding whiteboard markers. https://www.youtube.com/watch?v=PhNUjg9X4g8

I always wondered how many other people did this. On the days I have to go into the office I'll spend 15 to 30 minutes sitting in my car sipping coffee and listening to high BPM music. Lately, I've felt like I need to psych myself into being motivated enough to walk into the building.

I don't think they were implying something is inherently wrong with agencies. My interpretation of their comment is that 'agencies' who sell assembling plug-and-play UI kits are not the same as 'agencies' who design and build bespoke products from scratch.

I somewhat agree but I think your signalling factor is wrong. I don't think a high engineer count is the sign for whether or not the company needs a design system. I think it's the number of active products being developed. If you have 10 engineers working on 1 product I would agree that you don't need a design system. If you have 10 engineers building 3 products with a planned 4th future product a design system would be helpful.

In terms of state management, it's a bit of an apples-to-oranges comparison, no? It offers nothing over React because it doesn't offer any state management. AFAIK HTMX is a wrapper for the fetch function that lets you define your request from your HTML. How you manage the state on the server is up to you.

I use something similar to React class components. Under the hood my set function calls Object.assign and I debounce the render function callback. You could implement it yourself in <80 lines of JavaScript[0]. I'm not sure what other people use but I've been using this style of state management for ~4 years and it's been fine so far.

[0]: https://github.com/codewithkyle/supercomponent/blob/master/s...

Edit: if signals are your jam you could us https://github.com/maverick-js/signals

I've raised 3 dogs from pups to death (~14 years old) and they've all consumed water during their lives. Coincidence? I think not and this site agrees.

For me, that's the beauty of Web Components. You can find (or build) a base class that works the way you need it. I like a React class component style class with an XState-inspired state machine built in.

https://github.com/codewithkyle/supercomponent/blob/master/s...

That's a really neat plugin! Couple of questions for you:

1. How many times a [day/month] do you use it?

2. In your experience how often does GPT 'hallucinate' an explanation?

>I don't know the culture

I've been using this site for a little over 3 years now and I was wondering the same thing about replying with my own VTT web app.

2 Hydrogen + 1 Oxygen = H2O. Linking to the U.S. electricity generation by energy source makes sense to me. If anything I'm just disappointed that it's already pushing a green energy (hydropower) agenda. /s

> What drives people?

I've worked on [side/pet/hobby] projects consistently for the last 6 years. What drives me is my friends. One of the latest projects I've started to work on is a free alternative to a mobile app called UDisc. They hit us with the ol' switcheroo by offering the service for free for several years and now force you to pay if you want to maintain your previous disc golf rounds (beyond 10 rounds).

I've tried to build things only I want and I usually lose steam or interest. For me, building things for, and with, other people keeps me motivated.

The Pixel 3 is a good phone. I bought one new and used it for ~5 years. The battery was still going strong and my only issue was the USB-C port stopped working.

One person's intentional choice is another's inconsistent mistake. I like to think that's what makes software wonderful yet endlessly frustrating.

> I still can't see what's the point of it. Why would I want to do it?

It depends on how you like to build projects. If you like the current state of client-side rendering there is no point to using HTMX. If you like server-side rendering (my personal preference) then HTMX fills the gap of doing partial DOM updates without needing to reload the entire page. Some people will argue about perf metrics until they're blue in the face. I mostly rely on personal preferences.

> The corresponding property in CSS is color, not font-color.

So why not color-{color}-{shade}?

I believe so. At least this is my understanding of HATEOAS.

It's the minor inconsistencies that prevented me from using Tailwind on any serious projects. I've never been able to get past their choice to use text-{color} instead of font-{color}.

Tailwind 1.0 was great. Give me a few utility classes to style borders, fonts, backgrounds, and box shadows. Tailwind has descended into madness as they endlessly increase the scope.

> poorly explains what it is

Seems clear to me but I've been watching this project grow for a few years now. If you read the brief introduction, motivation, and quick start on the homepage what do you think the project does?

> why would you want to use something like this

I would agree that part wasn't clear to me either, at least not right away. When compared to something like a SPA the state has to persist on the server while an ephemeral state exists on the client. With HTMX the state only needs to exist on the server. If this sounds like the MPAs of yesteryear, it is. You render the HTML using the frameworks/tools/languages you fancy. HTMX provides custom attributes you can use to update content within a page without having to reload the entire page.

Interesting. I guess I've been going off of RFC 7231

> The PUT method requests that the state of the target resource be created or replaced with the state defined by the representation enclosed in the request message payload.

https://www.ietf.org/rfc/rfc7231.txt

> POST - Asks the server to create a new resource

> PUT - Asks the server to edit/update an existing resource

Maybe I've been doing it wrong all these years but it seems to me that the guides flip-flops the responsibility of POST and PUT. My understanding is that POST should edit/modify while PUT creates/replaces a resource.

We use the following:

Nit: This is a minor thing. Technically you should do it, but it won’t hugely impact things.

Optional: I think this may be a good idea, but it’s not strictly required.

FYI: I don’t expect you to do this in this PR, but you may find this interesting to think about for the future.

None of these block a merge and anything beyond these type of comments will be a in-person discussion.

If they're generated on the client you would need to keep clock drift[0] in mind since the leading bits are time based.

[0]: https://youtu.be/mAyW-4LeXZo (Clock Synchronization in Distributed Systems by Martin Kleppmann)

I will concede that saying "titles are just food for our egos" is a bit blunt and that there's usually a difference in expectations between Jr Devs and Sr Devs at most companies.