gunshowmo

In what way does the UK have "considerably more rights and freedoms" than the US?

I've used Zapatos and can vouch for its effectiveness. It doesn't bind you into any specific way of setting up your database or defining models, but provides an extremely easy way to integrate with other TS libraries in order to get typed queries.

Thank you for your incredible work on this.

This is an extremely strong set of features in one language. All the best in this project!

Would love to read about some examples / strategies in a blog post some day!

Yes, and since typing is only at compile time, it's also missing some of the extremely convenient pattern matching syntax that I love from Haskell, Rust, Scala, etc....

Despite some downside, I'm a huge fan overall though. I haven't tried ReasonML or ReScript, but compared to bare JS, TypeScript makes frontend programming a lot more enjoyable to me.

Recent updates in TypeScript have also made ADTs much better to use and make expressing business logic in a statically safe way. It's incredible how much mental overhead that good typing systems (and good utilization of them) can save you when navigating complex code bases.

The more time you spend on this site the more you realize that it is not immune to the same problem that other sites have of people acting as if they have something insightful to say when they're just regurgitating common talking points.

The few contrarian opionions typically get buried here, althougn not hidden or lost in a massive sea like Reddit for the most part.

This place is better to glean insight from the more technical threads or the ocassional debates that don't immediately devolve into emotional appeals.

The fact that it's been well over 3 years since the introduction of hooks in React and people still don't understand how to use them makes me very worried for frontend development.

Really looking forward to server components.

This looks really cool. It would be nice to see some benchmarks against something like electron to see how they compare performance-wise for end users.

This is really interesting. Would you mind sharing a bit about how you keep the data that is shared across services in sync? Or is there a hard separation of concerns so that services would only commuincate with the service that owns that data to obtain it?

Fantastic article. This kind of insight into how people break down complicated problems into more manageable pieces is extremely valuable.

This looks fantastic! Looking forward to diving in a bit deeper.

They do based on what I've seen, you're right. I'm speaking more to the consistency of styling across the project, but if the UI library is separated out from the rest of the project then it shouldn't actually be a concern to compose the components with tailwind-styled elements.

Thanks for helping me think through it further!

Thanks for these ideas! The react-aria seems quite interesting to develop a UI library library using Tailwind-styled elements while accounting for accessibility.

Nice - I've seen a recent explosion of good libraries. I've seen Atlassian, Shopify, and others open source subsets of their own libraries as well.

Another less popular one that I have had my eye on for some time is Mantine. It seems very polished and composable.

Looks fantastic. My only concern using this in a full React project is its lack of interoperability with standard libraries. It seems like for the best experience, you either buy Tailwind UI to use with a tailwind project for anything except the most basic UIs, reimplement the Tailwind UI components yourself, or have a weird mix of css-in-js and Tailwind CSS. Although I love the idea of HTML-native inputs all the way through, I tend to immediately run into issues where using a native interface instead of a JS-based implementation harms the user experience.

Props to the team though - I feel like this is something I'll try out for a marketing site.

This is great - love the detail this goes into.

Agreed completely. I'm surprised someone deemed this fit to publish.

The entire post seems to miss the point of UI frameworks and libraries entirely.

GKE in particular has a very high overhead cost per cluster. That's the only reason I bothered learning kOps and Terraform.

Yeah, definitely seems that way from all the feedback I've been getting. The exam is soon enough that I'm going to be getting it over with anyway, but I hope I can find something to do afterwards that isn't in that box.

Thanks for the reply - I would like to be close to the tech side if I can but it's been tough so far without the initial experience. I'll keep revising and sending out my resume to the tech names as well to hopefully at least get an interview.

Thanks a lot for the detailed reply. Honestly I actually enjoy leetcode-type questions for the most part so I don't mind practicing those at all.

I'll take a look at my resume and see how I can restructure it and start sending it out to at least see if I can get an answer back.

Cheers!

Thanks for the advice - are there certain topics I can learn about or some way you think I can work on making my resume stand out in any way after acquiring those skills?

I highly encourage you to look at a picture of the inside of an airplane cockpit.

Sometimes clean looking UI requires complexity.

If I need to let a user sort a list of items, is it more UI/UX friendly to make them press a button multiple times until an item is in the right place, or is it better to let them click and drag the item to the right part of the list?

The latter requires a lot more work but makes the experience a lot smoother.

I definitely understand the frustration towards the growing ecosystem of web app technologies, but I think people really disregard the necessity of the complexity.

There are certain things that basic HTML/CSS simply cannot do, or if it can, does so in a very hacky way. For basic websites, you can absolutely get away with more basic templating, but as soon as you enter the territory of clean looking UI components that are both visibly appealing and functional, you are basically required to implement the complexity somewhere the choice of framework then is just determining how you want to structure that complexity. When you try to make a performant web application with a lot of interconnected, moving parts, the reason for a lot of the "bloat" becomes very apparent.

This man deserves so much respect. He even open-sourced the software he created to generate his videos, allowing more people to create similar helpful content.

I'm sure a lot more kids would be interested in math if they were able to visualize the beauty of it in a more vivid manner than just chalkboard drawings.

I do sessions-based authentication via my API server. You can implement this in quite a few ways, but I think Redis is pretty common for the speed. I think there are libraries in most languages that should implement this in some way or another, but it isn't too hard to do by yourself either.

JWT also works very well if you don't need the ability to immediately revoke access, since in an efficient JWT implementation, you'd only be refreshing the token at specific intervals.

I also have a couple of flows set up to authenticate users via the Facebook and Google OAuth APIs, tying them to my own users' accounts.

Thanks for the advice, that's a really good way of framing things.

I'm currently struggling with this as well. I'm trying to transition into tech from a non-tech role so it feels like my resume gets put in the trash heap first.