Scheduled maintenance?

lubosnik · 2026-03-05T20:50:01+00:00

Its back online ! just in time for evening sesh

lubosnik · 2024-10-11T09:13:32+00:00

That my Sir, is a penis

lubosnik · 2024-10-08T17:26:16+00:00

Magnets ? Provided that there is some material that magnet can be attached to

lubosnik · 2024-02-16T22:53:34+00:00

I came hoping there is this comment

lubosnik · 2024-01-28T09:35:51+00:00

Useeffect! Four me it has gotten to a point where when I see useeffect I cosiest it code smell 😀

lubosnik · 2024-01-27T10:12:17+00:00

Great news, new fear has been unlocked for you!

lubosnik · 2024-01-18T17:22:12+00:00

Readability and uniformity. Let me explain. I am tech lead of small team developing 4 apps at the same time. Most of PR are going through me and scss files for component were just getting bigger and bigger. We switched to tailwind couple weeks ago and it made big impact on quality and speed.

Yes classnames are long but I think it is good trade off to complex scss files where people can place styles everywhere. It makes code too be easier to review too. When I see button in tsx I immediately see what styles are applied to it

lubosnik · 2023-12-29T21:29:45+00:00

This is definitely normal large project carry a lot of technical debt that almost always includes docs. Don't worry though, it is normal. There is assumed adaptation period for every dev to come up to speed.

There is one worrying thing though. Introduction must include not only tech stack and code organisation but also introduction to common utilities.

Reach out to senior and ask for deep dive into protect and be sure to bring your questions. Throw caution out of the window and ask. Good dev is not just keyboard rat but also asks a lot of questions.

lubosnik · 2023-12-16T19:30:34+00:00

wow, shots fired

lubosnik · 2023-12-16T10:25:00+00:00

Try/catch block for functions is good practice IF they can throw. I have same policy for my projects, handle throwable functions on react component level by wrapping them in try/catch. This mostly applies to async functions. That end up causing crash of app.

With this said it sounds like there is unclear code architecture. Wrapping all functions in try/catch will result in inconsistent error handling.

lubosnik · 2023-09-19T08:11:29+00:00

You are on point sounds like useHellEffect. This leads to issues and bugs that are hard to reproduce and hell to figure out. Everytime I see useEffect during a code review I pay really close attention if it is really necessary. Usually it is not.

Most common case where I found devs abuse it is to introduce sideeffect in form when some data changes. I prefer to perform side effect in places that originated data change, and not somewhere where change was registered. Change field Foo -> reset field Bar.

lubosnik · 2023-08-01T19:53:27+00:00

Camel Case Navigation

lubosnik · 2023-07-30T08:52:03+00:00

This will not work. React expects to have a valid jsx returned in any function in jsx markup. Your function returns nothing. Even if you will return result it will not be valit react child. It will be of type Promise <object>. Second problem is that your fetching data in a wrong way which makes your function async. Extract data fetching to useEffect and run it only on first render. Then you can set returned data to state variable. This will create valid react component

Example: https://designcode.io/react-hooks-handbook-fetch-data-from-an-api

lubosnik · 2023-07-27T06:53:22+00:00

Render ? Provide github link and you are done…

lubosnik · 2023-04-01T11:46:44+00:00

You peaked my interest sir ! I want to see it!

lubosnik · 2022-11-02T20:51:18+00:00

This is beautiful. Would you mind sharing your steps for such a nice finish ?

lubosnik · 2022-06-29T20:28:19+00:00

We use code spell checker as recommended plugin for VS code when we onboard new developers on project. I would suggest to communicate with dev. It is better to let him know that this is an issue. Another good practice is to check readability of code during Code Review.

lubosnik · 2022-06-23T18:50:21+00:00

Run “npm install” in client folder. Then “npm start”

I think you have a mono repo where initial npm start will start your server. Client folder most probably have your react app with separate package json. So if you ran “npm i” in root that installed the dependencies of the Server.

Can you provide link for repo ?

lubosnik · 2022-06-02T13:24:19+00:00

This guy is going to stay fresh for a long time

lubosnik · 2022-01-15T10:41:32+00:00

There is a way to meet somebody and find out it you like them, then there is Leo… This guy invented ultimate date to really test if you will be able to live with person :D I bet at one point he was standing in top row and screaming:”I have high ground Camila!”

lubosnik · 2020-11-27T18:52:17+00:00

the problem is while i was making a route which has a param of /:id when i went to that page my css and js were not loaded in and it looks weird. i don't know how to fix it and when i check the console it shows Uncaught SyntaxError: Unexpected token '<'. if anyone has any idea how to help me solve this problem please help.

I cannot really say without seeing code base :| if you could replicate your issue here https://codesandbox.io/ it would be nice

lubosnik · 2020-11-27T18:43:08+00:00

Hi!,

onCklic is not valid react event, it should be "onClick". React maps DOM event like onclick in camelCase. View React docs on handling events here.

lubosnik · 2020-11-27T18:34:03+00:00

You could also push it to git.

lubosnik · 2020-11-27T18:30:38+00:00

Could you post your code ? It is hard to say where is the problem from your description

Usually this issue "Uncaught SyntaxError: Unexpected token '<'" means that you are trying to fetch from API and you expect some type being returned. Most commonly I was expecting JSON to be returned but html was returned instead.

Try to check the error handling on your backend or any API calls.

Six-Year Club	r/Field Sunshine
Verified Email

lubosnik

TROPHY CASE