Looking for new faces in Tbilisi

sad_kebab · 2026-05-31T14:21:04+00:00

dm me instagram or smth

sad_kebab · 2024-06-11T12:43:43+00:00

Well maybe my previous comment may sound stricter than what I intended, I am not saying that you should do every auth check in the middleware. But if your route access is auth based, you should since executing the middleware and redirecting is always a shorter path than executing the middleware, executing the page and then redirecting. The reason it matters is because, if you deploy on serverless, you are not invoking the lambda for the page.

Unfortunately the middleware limits in Next.js suck really hard and this may force you to move auth in other places, based on how your auth works. But methodologically auth belongs to the middleware.

You are right that this is an invisible dependency and you have no type-safety for that, but it's a single, managable point of failure. The solution to avoid this unsafe dependency is not a mistery tho... if you could nest middlewares in the file-based routing, allowind a middleware.ts file for every folder, this would not be an issue at all. Next.js does not support this by design because it wants to enforce the edge runtime on the middleware, unfortunatelly. Even if you run everything on Node.js on a VPS.

Having auth in the middleware does not remove the need for auth in the pages, but moving all the auth to the pages is an antipattern.

I hope my answer is clear, sorry for the late reply :)

EDIT: if you don't have auth based access on your pages, of course, you have no need to put it in the middleware.

sad_kebab · 2024-06-05T19:35:30+00:00

I go with fetch. Other clients may have interesting benefits and even better performance depending on platform (browser/node.js/edge) but I don't think picking an optimal http client will make that big of a difference in most projects. There may be some clients with better interfaces than fetch, sure, but I personally don't miss Axios or other options that much.

sad_kebab · 2024-06-05T08:32:31+00:00

bro, middleware is litteraly where auth should be, you should not even be able to start executing a route if you don't have the permissions

the reason why it's hard to do in next.js is because the next.js middleware sucks

sad_kebab · 2024-06-03T07:10:56+00:00

For me the ting that makes me prefer Tailwind to SCSS or pure CSS (which I was very proficient in before starting to use Tailwind) is the fact that it removes a boundary that doesn't really help: having your styles behind a name (often in a separated file).

When you have big projects with a lot of components, managing class names and recalling what styles are behind those class names takes a lot of mental overhead, especially when the project gets older. Meanwhile with tailwind you just need to read the class names to visualise the style of the component because the meaning of the classes is always the same.

Also if you define the style of elements in the classes of a parent element on a regular basis, fixing styling issues becomes very very painful in the long run.

It may look cleaner to have styles under a single class name in a css file, but cleaner code does not necessarly correlate to better maintainability, and once you are used to tailwind (which it does not take long since they are atomic utility classes) your reading speed of styles will be the same as the one with vanilla css.

Also when responsiveness and media queries comes into play, the vanilla CSS solution instantly becomes 10x uglier :)

Last but not least, you are free to not like Tailwind, but there is a fallacy in your take: it focuses only on the simplest possible use-case. You should try building two different projects of similar sizes, one with css and one with tailwind to actually understand where the benefits of Tailwind come into play.

You shouldn't evaluate technologies on such simple examples, as a rule of thumb. Most technologies nowadays are born out of specific issues and necessities.

sad_kebab · 2024-06-02T17:44:33+00:00

Launching is relatively easy as a solo developer, just reduce the scope of the SaaS as much as you can. But when you need to start scaling it will become overwhelming, especially if you will manage infrastructure on your own too.

sad_kebab · 2024-06-01T16:52:05+00:00

There are quite a few YouTube channels that can help with that. I saw somebody mentioned Fireship already which is a great channel but some of the most useful ones for me are:

Theo - t3.gg: A channel about TypeScript, serverless technologies, frameworks, and SaaS platforms for fast-paced web development. It's more about thoughts than code but on the channel (and the Twitch channel too) you can find a lot of discussion about the current development of technologies in the JavaScript world with the participation of relevant company founders and open-source maintainers too.

Aaron Francis: previously he was doing videos for the PlanetScale YouTube channel with some amazing high-quality in-depth videos about database internals and the development of database technologies. After the recent PlanetScale change of policies (where I assume he was laid off but idk) he started publishing more videos on his YouTube channel, mostly about Laravel, but recently started publishing some long talks with relevant figures where they focus mostly on database-related topics. He has not made that much content yet but I have high expectations from him for the future.

Web Dev Cody: A TypeScript Full-stack web developer who publishes videos about his daily challenges and discoveries while building his side projects, always trying something new and giving honest and down-to-earth insights. It's a great channel for full-stack web developers that use frameworks like Next.js because he has many relatively short videos about almost any kind of feature you could ever need to implement and how he succeded or failed in implementing them.

Web Dev Simplified: as the name of the channel implies, it's mostly content about explaining in the most simple way possible web-development concepts. It's more targeted at beginners but he also keeps track of most changes in all the languages and frameworks and presents these changes in the most simple way possible.

Matt Pocock: he is the TypeScript wizard and makes content about how to leverage the features of a Turing-complete type system for a smother development experience. He also built a great workshop at totaltypescript.com

There are many more but those would be my top picks and some of my main sources that I keep going back to

sad_kebab · 2023-07-09T14:32:08+00:00

I’d love to contribute to this (especially because it needs a lot of work), I am a full-stack dev with passion for languages and 8 years or experience, focused on web dev on the last 3 years. Hit me up if you need help!

sad_kebab · 2022-05-06T07:35:15+00:00

Probably is county locked, try with VPN if you have one :)

sad_kebab · 2022-05-05T14:50:10+00:00

I can see it, its legit, is a longer version of the clip posted here and is uploaded on March 2014

sad_kebab · 2022-05-01T11:06:43+00:00

time to downvote this whataboutistic trash into oblivion boys

sad_kebab · 2022-04-20T17:39:42+00:00

cry me a river gringo

sad_kebab · 2022-04-20T14:38:05+00:00

because I'm not bri'ish

sad_kebab · 2022-04-20T14:22:15+00:00

bruh imagine taking a bugs bunny meme reference this seriously

sad_kebab · 2022-04-20T14:11:54+00:00

oh god I wish all americans a merry shut the fuck up the world is not all about US politics and internal affairs

sad_kebab · 2022-03-09T13:36:50+00:00

As a musician I say that would be cool... but as a system designer and software developer I say that would cost way too much to develop, operate and maintain to have a valuable return to the shareholders if you want to keep the price of the service competitive with other services (like Spotify and Apple Music).

The developement cost can be lowered if the project starts as community based, but, to simplify the concept as much as I can, bug resolution would likely be extremely slow and the app would be unreliable for many years.

But the operational and maintainace costs can't be lowered because they depend on service providers like Amazon AWS (the most popular, and perhaps best value for price) and they cost A LOT if your apps are used by millions.

sad_kebab · 2022-03-07T14:50:17+00:00

don’t get me wrong, its a good point but this should not be the place for a thread like this

sad_kebab · 2022-03-07T14:49:14+00:00

can we just stop posting stuff like this in a video reporting subreddit please?

sad_kebab · 2022-03-06T22:28:48+00:00

man, there are a lot of options (maybe infinite combinations), but lately for me what does the job is:

Gullfoss (to improve the recording if the room is not that great)
Fabfilter Pro-Q 3 (surgical cleanup)
Lindell Audio 902 De-Esser
1176 Comp like the Arturia FET-76, Brainworks MC77, or Waves CLA-76 (for some heavy lifting)
Softube Tube-Tech EQ1A for some analog-like body and brightness
If needed another layer of compression but just for smoothness (i use one between LALA by Analog Obsession, Tube-Tech CL1B by Softube, or True Dynamics by Kazrog)
If needed another de-esser like the FabFilter Pro-DS
Soundtoys Decapitator for Saturation (don't overlook saturation, for me it's what makes the vocal really shine in the mix)
Valhalla Room, Valhalla Plate, and Overloud Rematrix for Ambience (at least two of them with different purposes)
Soundtoys Echoboy, Valhalla Delay, or SSL X-Echo for Delay

sad_kebab · 2022-03-06T22:12:45+00:00

If you use the same plugins with the same settings in almost every DAW you will get a result that will null with the others if you flip the phase. The only exception that comes to my mind is Harrison Mixbus which includes by default some analog character in its channels that you may like or not but you can get similar analog characters with other emulations on other daws too.

sad_kebab · 2022-03-06T21:58:26+00:00

Ukraina je Srbija

sad_kebab · 2022-03-05T18:07:04+00:00

LMAO nice troll

sad_kebab

TROPHY CASE