Hello

I want to tell you about a very interesting Utopia project, in addition to making this topic a project topic, so that anyone can ask a question and talk.

About utopia

The utopian ecosystem is the culmination of many years of effort by a group of technology enthusiasts dedicated to freedom of expression and privacy. We call ourselves the 1984 band. Among us there are first-class professionals in almost all areas of IT, such as cryptographers, programmers, network engineers, and many others. It was a long and difficult journey. After all, this has never been done before! Finally, we present an ecosystem that will change the way the World communicates and processes financial transactions.

Read more in more detail:

In English

In Russian

Sooo, I finally got my beta to uizard.io a thingy that let's you transform paper sketches into UI prototypes in like a second (or two).

I tried other similar tools before, didn't work out 🤷‍♂

Don't even remember when I saw their video and registered for it, but that was quite some time ago now 😂

I only managed to play around, but it looks and works quite well so far. I am literally waiting till the next prototyping need to use it fully!

For those who is like "wtf is that" check it out https://youtu.be/C4ytTUu0RcQ
The YouTube is also a channel I think I've recommended before.

Ooo, I actually found when I registered for beta 😂 - Jan last year

Shortcuts

You probably not gonna find any new combinations, but it is still pretty cool

https://youtu.be/hi6TH5Gz_ms

Live vscode editor in github

https://github.com/features/codespaces/

Choosing the right class name

This one can drive you mad sometimes especially if you work in large teams.

Suppose you are creating a new component with similar elements, which are already styled. Should you just extend previous styles? Should you create another isolated styles for it in case it need to be a bit different? How to organise it properly?

I found this BEM cheatesheet pretty helpful. Also if you've never heard of BEM - it's worth checking it.

https://9elements.com/bem-cheat-sheet/

PS and yeah, I love cheatsheets. Frees up my brain's Ram sometimes

A few useful links to use as a respond

dontasktoask.com - when you get a question like "can I ask you smth?" as its generally waste of time. Just ask. This got used in our discuss channel, which I found quite useful

pleaseno.me - if you want to act like a smart ass when someone asks you e.g. Should I use php? 😂 Just kidding, php is not dead yet, so it depends.

lmgtfy.com - my favourite. It teaches people how to Google stuff. Best for questions like "guys, how do I install visual studio??"

Update:

https://iffuci.com - when people. Just say "hi/hello", if you bother well why not at least introducing yourself or starting a topic on smth

https://xyproblem.info - when someone gives you not enough context on what they are currently working on without specifying the actual problem they solve

Thanks to @tWiTfAcE for suggestions

So this UX actually triggered a few questions both in discussion group and personal messages. Let me welcome additional UX solutions that are kinda there but not quite yet.

The first bit is for the doors. A thingy that let you open doors without actually touching the handle

Opening the door with a push is already solved I think. You don't need to be karate master to do this.

And most importantly, that is even more relevant to the linked post with floor buttons. The question was smth like - what's the point if you gonna touch the floor buttons inside the lift anyways.

First, you could have foot buttons there too or even have something like on this video

Just registered for https://uxcitedkyiv.com/en - online conference around UX and design handled by people from Facebook, Jira etc

Should be interesting

I like how this whole covid situation push companies to do this things online. If not quarantine, I probably would never join this conference as it would require me travelling

Got this screenshot from another channel.

I like how at first I saw React.js 6 years and thought "sure, the first version got released 6 years ago and you should have started using it right away. Yeah, that's what everyone does isn't it? Saw new tech, fully jump on it"

But then I read "react - 4 years" and it kinda got clearer - they just don't have a single fucking clue. No questions then.

I would honestly just go to the interview and say

- you know what, I want to be clear and honest right from the start. I only have 3 years React.js experience and 5 years of React, would that be OK?

Good news.

Seems that you were all also impressed by the job spec I posted.

For those wondering - no, there is no difference between React and React.js apart from spelling. It's the same framework.

But the good news is that I managed to get you a full job description here. Its apparently a US company Tech Era Inc.

What to do with this info now?

I dunno. But I would encourage you to apply. Worst case scenario - you ll get a well paid job and probably become a "Tech Lead CTO React backend engineer" or smth 🤷‍♂️

Now, since I am getting you into this, I also figured out it makes sense to help you a bit and created a list of statements that you should definitely make when interviewing with them.

1. I am pretty comfortable with React.js, but have barely worked with React. Is it OK?

2. I do fill 5 years of front end dev requirement, is it fine if I also had 6 years of React experience (not like you can do much React backend though)

3. I believe I fit this job, as I had 10 years of React experience. Which is what you need for react.js and react combined.

4. I was actually the guy who created React

5. Could you clarify how can one have 4 years of React and 6 years of JavaScript? Isn't React based on JS?

This should get you up and running.

PS on a serious note, many companies are looking for devs without actually understanding who are they looking for. That's how you end up with this nonsense job descriptions. This should be a red flag for anyone looking for job as you are likely to end up doing everything dev-wise including DB migrations, SEO and devops, which is fine if you like exposure.

The moral of the story is simple: go for smth like this only when desperate for money, if you are looking for something constructed look elsewhere.

I wrote an article

Do you know why I don't do this often?

Because even the simplest, shortest article gets bombarded with hyperlinks. I keep referring to stuff when I write a post 😂

Some like it, some don't, but as a result you end up reading it forever (at least I do).

This one should be fairly quick though. Let's say.. Hmm.

🤓 Read Time: 7 minutes

Its on those extreme cases when you want to scroll and filter something in React without touching parent component and using too many external packages.

I counted only 11 external links. Doing a good job here.

PS I know, too much text recently, I'll throw a few design UI UX stuff soon

Was just reviewing some code, this one liner destructuring can be helpful to some. Mind readability though, sometimes it's still better to destruct it separately when it's.. well too nested.

const {foo, bar: {bar1, bar2:{bar3}}} = this.props

Then you can access bar3 right away cuz it's declared already.

This helps you to avoid:
... = this.props
const {bar3} = this.props.bar.bar1.bar2

Also, if anyone thinks on vs code theme update, here is some inspiration

https://mobile.twitter.com/dan_abramov/status/1259287272148611074

I think you can't go any further in smoothing your responsiveness today.