Forem: oshell

There Is No Shortage Of Developers

oshell — Sun, 19 Apr 2020 20:09:41 +0000

It is just that the hiring process in most areas and for most companies suck.

I originally posted this thread on Twitter, but thought it would be worth sharing here too.

Original Tweet

SeriousWebDev

@seriouswebdev

The hiring process for most developer positions in most companies are ridiculous.

A thread about my experiences. twitter.com/bekahhw/status…

19:19 PM - 19 Apr 2020

Bekah Hawrot Weigel @bekahhw
I mean, I want to have a job, but I refuse to do a 6-8hr coding challenge without pay.

0 3

The Thread

/1 I was once asked to write a form with validation and error handling. Some fields should be validated async. API + design should be included. All should be tested and documented. They tell me this should be done in around 3 hours.

/2 I am working on the field for several years and have build many complex spa projects with high traffic. However, given the task I would already assume this would at least take me 8 hours. Even if I could do it in 3 hours, using a whole day would end up with a better result

/3 since noone can check how much time I actually spend on the task, people who spend more time, will have an advantage. This is why you are basically forced to spend more time on the task

/4 the companies normally give you a time limit. They themselves however, do not commit to anything. They do not have to answer or if they decline, they do not give you feedback. If you do not get the job you basically spent 8 hours on a useless generic software

/5 let's say you apply to 10 companies. This means with tasks like that, you would have to spend 80 hours, programming bull shit tasks. For free.

/6 some companies give you tasks, which could even be real tickets from their asana board. Big red flags, but I see it often. So more generic tasks are better, because you can be sure, they do not steal your code, but you are still wasting your time

/7 you do all of this and MAYBE you get invited to an interview, where you meet the product manager. If he does not like you, you can go home already. Especially in smaller business, chemistry is really important. So asking somebody to do a 8h task before talking to him is stupid

/8 that's the halo effect. Within seconds the person will have an opinion about you and this will greatly influence their decision. This also means it would make more sense to have a short meeting first and then give the task. But then again, the company does not value your time

/9 even after the talk went great and I could answer all of the questions on the white board, I get declined. The companies normally only tell you, they are sorry, but do not tell you why. Because they cannot tell you "you know, we don't like your face"

/10 once you passed that stage, you are invited to another meeting with the CEO. Maybe you are lucky and he agrees with the interviewer before.

/11 of course the salary range is 40-80k and they will only tell you what they can pay you, once they setup the final contact. So maybe after 30h of your time you finally have a contact, you have to decline, because they do not pay you enough.

/12 and I have to go through all of this processes while I have several years of experience, recommendations from previous companies, a github profile with several thousand commits in the last year and while being in the top 5% for all related topics on stackoverflow

/13 meanwhile you read in the news that there is a shortage of professional developers. Companies are just too stupid to make it attractive for developers to apply. Stop wasting our times.

/14 here is how it should work:

definite EXACTLY what you need and what is REQUIRED
define how you seperate junior, intermediate and senior or have a short call where you evaluate
define EXACTLY what you pay for each level
have a short MEETING FIRST to check chemistry

/15 now people who apply are already better fits. Now check through existing projects and publications and if possible: skip the stupid task

/16 normally the contacts include a very short notice period for the first months. So why even bother to ask for an extra task? If you still want me to do extra work to prove myself, I expect the company to give me a longer notice period in return.

Have you had similar experiences? What's your point of view? Let me know in the comments.

Follow me on Twitter if you like my content. I will share tech related articles and videos over there.

Top 7 free iOS Apps to boost your quality of life

oshell — Fri, 10 Apr 2020 21:36:00 +0000

Many developers jump into iOS developing because it promises up to 85% more roi than android apps. Apple user are just willing to pay more. So for most of iOS users it is more normal and natural to pay for apps upfront or for in-app purchases.

Nevertheless iOS has some pretty damn good free apps (or apps with fair free tiers) too. Here is a list of 7 apps I am using on a day to day basis, which make my life easier and which do not even cost me a penny.

1#: Note Taking with Bear

Your quality of life improves as soon as you have your thoughts, ideas and plans organised and made them searchable. I have tested quite some note taking apps and the simplicity and elegance of Bear is what I was looking for, for quite some time.

The Editor

You basically have a Markdown Editor, which transforms your text while writing. Dev.to should seriously implement that.

The Structure

You can then use hashtags in your notes and each hash tag becomes its own category. This way your notes are easily organised and it is not that linear. You do not have to set up folders and then on each note, think about which folder your note belongs to or if this might change in the future. It is much more related to our way of thinking.

The Search

It also has a good global full text search feature. So if you are looking for a beautifully and clever designed note taking app, which makes it easy to make your notes organised and searchable: Bear is the way to go.

2#: Cloud Storage with Mega

Bear is good for organising your thoughts, but where to put all the photos, documents and sensible data? You just feel better, if you know your data is safe and accessible from anywhere.

Our boy Kim Dotcom got your back. He published a cloud storage provider called Mega.nz. If you do not trust Google, Apple and Microsoft to hold your data, Mega is your best bet. Not only that - the user interface is the best I have come across. Moreover apple blocks out services like Google Drive for some features like multi upload, likely to promote their own storage service. Mega however does not seem to be affected by this. If you haven't already, you should definitely give it a try.

3#: Money Management with Spendee

Quality of life also means you have your finances under control. I like to have an app, where I simply deduct all my fixed cost at the first of the month, even if this cost might only come up at the end of the month or even only once a year. This way there are no bad surprises.

I don't want to connect my bank account with any of my apps for security and privacy reasons. So I just made it a habit of mine to manually enter all my spendings after the fixed costs are taken from my main balance in Spendee. This also makes me more mindful of what I am spending money on. Plus Spendee gives you an good overview of what you spend your money for. It works completely offline and the free version works just fine for me. The Total Number I have in Spendee is the only source of truth, of how much money I have available.

4#: Track your Habit(s)

Simplicity is key. Habit is a really simple habit tracking app. Add your habits and how often you want to perform them and simply check them every time you performed them. The underlying bar will get filled, the more often you performed the task. Getting it to 100% is quite challenging tho. After reading Atomic Habits, which I highly recommend anybody, I have the belief that your success and overall quality of life mainly depends on your set of habits. Things that improve your mental health, physical health or influence your longterm success should be somewhat automated things that you do each and every day without thinking about it. Start as small as possible (make it easy) and increase the difficulty of the task a bit every time. Just so it still feels like a no brainer. But most importantly: Do it! And track it with this app.

5#: Track your Workouts with Gymbook

As I just mentioned your physical health also plays a big role in your overall quality of life. It is most important that you do any sports in the first place. But if you hit the gym on a regular basis it makes a lot of sense to keep track of at least your biggest exercises to see where you stand. If you reach a plateau, you probably have to change your training routine, change number of reps or weight, the angle or even whole exercises. Using a app like Gymbook helps you to have more analytical approach to your workouts.

You can build your own workout plan with this app and set a timer for how long you have between sets. Many people do not even take the lengths of their pauses into consideration, but it plays a big role in your workout.

Another important aspect, which most people do not recognise, is the overall volume of your training (how much weight lifted in whole workout).
Gymbook gives you a summary at the end of each workout with all this information and statistics on how much you improved compared to your last workout.

6#: Meditate with Smiling Mind

People go to the gym and train their physical health, but still most people do not do anything to improve their mental health. But it is just as important. Mediation is probably the most common way to improve your mental health. Many people play it down and say it does not work for them, but you have to stick to it for a while to notice the results. After listening to Tim Ferris for some time it feels like 90% of all his very successful guests describe meditation as one of the most important skills, if not THE most important skill, to learn. So it is time to put the prejudices aside and start practicing meditation.

There are some really famous meditation apps like Calm, headspace and waking up. But they all have quite expensive premium plans, which probably stops many people from using it. While these apps are good and have some special strengths, especially when it comes to different voices and updates, meditation does not have to cost you anything. Smiling Mind is non-profit and 100% free. They have lessons for body scan, better sleep, general mindfulness and even lessons which you could listen to while on you way to work. So there is basically no excuse anymore to at least give it a try. I am not saying you will have immediate improvements in your quality of life, but if you stick to it for a while, you will notice you will become more calm, more rational, more grateful and it will be easier for you to set your mind into the state you currently desire.

7#: Stay Up to Date with Feedly

Last but not least: Quality of life also means that I have an easy and comfortable way of staying up to date. I do not want to browse 20 different news pages, blogs and other media to get the information I want.

Feedly is basically like our good old friend RSS feeds, but with a more modern approach. Good bye information overload: Just follow the topics and publishers you are interested in and display the latest news in the format you prefer: Text only, Cards, Magazine, compact or with more space - you name it.

Anything missing in my list? Let me know in the comments.

Like this kind of content? Like and follow to help me escape the search algorithms.

How I Ended Up Writing My Own Presentation Software and What I Learned Along the Way

oshell — Fri, 27 Mar 2020 17:25:51 +0000

This article gives you an idea of what it looks like to build a production ready software - from the initial idea and concept, to the first prototype and finally the finished product. If you only care about the "lessons learned part" feel free to jump to Most Common Mistakes for Side Projects!. Also you will find a TL;DR section at the end of the article.

Prolog - Motivation to Build the Software

I am working as a professional software developer for more than 6 years now. Yet, I was not able to create a production ready application on my own. It always starts out with a great idea or a new technology, you want to tinker around with. But sooner or later you stumble across the first problems. Things become difficult and because you are just a lazy person with great ideas, you add the project to the ever growing list of unfinished attempts of building the next big thing.

Enough!

I have worked in multi billion dollar companies and was working on high traffic projects for years now. I worked with databases, backend, frontend, design, CI and automation. Everything has prepared me for this very moment: Bringing my first application to production! Oh boy, I am pumped!

And....you know there is this corona thing going on. So in a silent moment of inspiration I thought to myself: "Do I stay home, playing video games all day and be the lazy piece of shit, I have been for the last 30 years? Or do I use the time and finally prove to myself, that I can finish things."

Maybe you are thinking to yourself: "Hey this guy hasn't produced a single production ready software? Why should I care what he thinks?" Well, yeah...you have a point. But don't fall for the Survivorship Fallacy. We tend to look up to very successful people telling their success stories. But while it is really hard to tell what the real reason for their success was, it is often really easy to tell what the reason for a failed product was. By just avoiding these things, you naturally increase you chances of success. So let me tell you: I know how to fail! So you better listen.

Concept Phase - What Should I Write?

Now I have the time! I have the skills! I have the motivation!

But wtf am I going to write? One thing I learned from The Techlead is that your idea does not have to be super original, unless you want to go from Zero to One. But most of the products out there don't do that. I mean, just look at gaming industry. The most successful game at the moment (Fortnite), basically just copied the Battle Royale game PUBG, gave it cartoony style and some building elements, to appeal to a younger audience, and here we are! What I am saying is: It is often safer to copy an existing product and add your own touch, because you can be sure there is a market for it. Your product just needs to be more appealing for a certain segment of the existing market.

So I remember back in university, a teacher told me "If you call yourself a programmer, you don't use PowerPoint, you program your presentation using web technologies". He had a point. Using CSS and javascript gives you all the flexibility you could wish for. Moreover you can easily share the presentation with the rest of the world. But as the lazy piece of shit I was, the first thing I did was looking for existing frameworks to do all the hard work for me. Just after a little bit of googling I stumbled across impress.js. The guy made a sample presentation to showcase the library. I saw it and was amazed. Back in the time we already had tools like Prezi. However with this library I had no limitations and was not forced into a subscription, to present in offline mode. (Really, Prezi?) I don't want to enter a subscription for one feature. And while Prezi presentations seem to be really dynamic, they are nevertheless really linear and creating them takes ages. There is much space for improvement. And these guys had several funding rounds collecting millions of dollars. However, you can easily prototype something like Prezi in a few weeks, is what I thought.

Impress.js is amazing, but creating presentations with it is just a pain in the ass. Took way too long. So my first idea was to simply fork this library and add an editor to it. But lots of the codebase was spaghetti code and documentation was just as bad. The main logic was contained in a file with maybe 300 lines. So I decided it is probably easier for me to simply look into the DOM to see what's happening and reverse-engineer the presentation logic and go from there. However, the project was created in 2011 and when I first started this, SPA where in really early stages. So I tried my best building something usable with jQuery, but the code simply became unmaintainable too fast. On the one hand I was not experienced enough and on the other hand keeping the DOM and objects in sync was really difficult and hard to debug. As you might have guessed, I stopped working on it and added it to my list of unfinished projects.

I just could not handle the scope of the project. It was only years later, I felt experienced enough to pick this project up again.

Prototype - Let's Build It!

Now after working with SPAs in professional environments for some years I feel quite confident I could finish the project now. So after a couple days of coding I had a prototype looking something like this:

This already looked quite promising. I used React and Redux to do this, because at the time it was the hot topic. State-management became quite complex real quick, because each slide should be an object and elements within a slide should also be objects. So I end up with deeply nested state, which is a mess to update, or I have to flatten the state and use ID references. I used redux to make it manageable at all, but I almost stopped working on it just because I really do not like redux. I tried switching to Mobx, because it appeared much more natural to me, but since my project was bootstrapped with react-create-app, I ran into issues with decorators. Mobx basically needs adjustments to the webpack config and I would have to eject the project, which I wanted to avoid. While not using decorators would have been fine with me, the documentation back then was mainly based around decorators. Overall it just made me sick, I would have to read through documentations of 3-4 different libraries. I just wanted to have a deeply integrated state management solution and wanted to have a "one fits everything" framework, which helps me getting this done. At this point I almost stopped, because the development experience was just too frustrating. I decided to re-write my app using Vuejs. While I would normally not recommend re-writing anything, the project was still in early stages and I knew that Vue has a deeply integrated state management solution (Vuex) and several other benefits. It came to the market later and was able to learn from all the mistakes angular and react did. And all the things like state management, routing, cli, typescript ect. are developed by the core team and are opt-in. So you can integrate them as soon as you need to. I do not regret this decision. It feels so much more natural to me to develop applications in Vue and my code-base is now highly maintainable, even when coming back to it after months.

After roughly 50 hours development time the prototype looks already quite promising. Although this was almost what I intended it to be, there were so many things missing: Register/Login, Uploading Images, Embedding Videos, Charts. But then I noticed I am just blowing up the scope. I could wrap the application as it is in an electron wrapper, to run it offline. I won't need servers, I won't need authentication, I won't need image hosting. And the idea is to run presentations offline anyway. You do not want to be dependent on high speed internet, when giving a really important talk. Also I do not need videos or charts for my prototype. As long as I can add text, images and some symbols, it's fine. So after moving my application into electron and skipping some features, this is what it looked like:

The tool is already production ready and I am currently working on a release. However, I struggled a lot along the way and had many moments, when I just stopped working on it or wanted to give up, but over the course of many years and many failed projects I learned some valuable lessons, which finally helped me to get this project done. Moreover, there are still few things, I wish I put more attention to. Here is a list of the most common mistakes you should avoid doing.

Most Common Mistakes for Side Projects!

Massive Scope

I just could not handle the scope of the project

Let's begin with the number one Mistake for side projects. Scope is too big. As mentioned earlier, I started the project and was just overwhelmed by the complexity of keeping DOM and objects in sync. I was not prepared at this point. I was able to pick up the project again years later, but you are better off choosing a project where you already know, you are capable of finishing it.

Play with fancy technology and add fancy features

This is kind of related to the first Mistake. In the beginning you should keep it simple. Most people don't really get what MVP means. In this case it helped me to reverse my thinking like this: You will not have the perfect product, when there is nothing more to add, but when there is nothing left to remove.

I do not need videos or charts for my prototype. As long as I can add text, images and some symbols, it's fine.

Think about what your product/software should do and then remove everything that is not absolutely necessary for it to work.

Too often you end up just trying out some new and fancy tool, just for the purpose of doing so. This is just wasting your time, when you really want to get to production ready state.

Also it is very tempting to add more and more features during development phase, because you have this shiny nice looking product in your head. But once you throw your product on the market, you probably realise, that the users are only using 10-20% of your features or the problem is you do not find users in the first place.

Focusing on only what is really essential to your product not only means you are more likely to finish your project - it also means you will get user feedback much faster and can start iterating on that feedback.

I used React and Redux to do this, because at the time it was the hot topic

Last but not least, you should stick to technology you already know. You coded 3 years with javascript? Maybe use Ionic for your app, instead of learning swift and being stuck in the tutorial hell. I used react and redux, because it was the hot topic at this point. But Vue and Vuex just feels more natural to me, so it is much more likely I finish the project using it.

Coding on the couch or on the go

Things become difficult [..] you are just a lazy person with great ideas.

Don't try to develop on your couch or laying in your bed. Even worse... for a long time I thought I could work while traveling. I failed hard trying this. Maybe it works for some persons, but I cannot imagine anyone working really effectively on the go. You have to create an environment, where it is obvious you have to work. Optimal case is a quiet place, with a desk, a really good chair and at least one additional 22 - 27 inch screen connected to your PC/Laptop.

Coding it, because it sounds cool

You will most likely have to invest many many hours into the project. "Cool" just won't be enough. You need to be really passionate about the thing you are building. Otherwise there is just no way you will put in the hours needed.

Not having a USP

USP stands for unique selling point. As I mentioned it is fine to just copy a product and add your own touch. But you also need to separate yourself from other products on the market with something that really creates value. Just another design won't be enough.

I don't want to enter a subscription for one feature.

For me it was just seeing that existing options force you into a subscription model. So my USP can be as simple as: No subscription.

While Prezi presentations seem to be really dynamic, they are nevertheless really linear and creating them takes ages.

Another thing I noticed is that all the presentation tools have a linear way of presentation. Slide 1 to Slide 2 to Slide 3. However with my software I wanted to have a more interactive approach to presentations, where you can talk to your audience and then decide in which direction you want to go. Moreover presentations are theme based. You can switch between themes with a single click.

TL;DR

Only seek for what is necessary (MVP)
Create an environment which makes it easy to be productive
Stick to technology you know and you are comfortable with
Write tools for things you are passionate about
Create your product around a marketing strategy (USPs) and communities

Hope you enjoyed the read.

How is you experience with side projects? What are your tips to finally get shit done? Let me know in the comments.

React State Management: When To Use Redux And What Are The Alternatives

oshell — Thu, 19 Mar 2020 18:21:54 +0000

When writing applications with react you will soon reach a point where you pass down callback functions as props two or three levels, to change the parents state. For most projects you will need a third party solution for global state management, so you can directly access and modify state from any component in your app, without passing callbacks down the DOM.

Redux has somewhat become the industry standard. However, it includes quite some boilerplate for every simple state change. Although I have to admit the situation feels better now with the introduction of hooks, it is still hard for beginners to wrap their head around the concepts. During the learning experience the question comes up: Why would we do it like this? Isn't there a simpler way? There actually is. More on that later.

I don't want to bash redux here. It is industry leader for a reason and has its strengths. But once you have worked with Vue and Vuex, most people realise it just feels much more intuitive. This is just one of the reasons why vue is growing so rapidly and just recently got more stars than react on github.

So before we go over some of the alternatives, let's first take a step back and have a look at what redux does and what it is good for.

When To Use Redux

Redux is a global state management solution for frontend applications based around the idea of reducers. Reducers are pure functions, which take the previous state and action object, containing a type and an payload, to mutate the state. The action objects are also pure functions. This is already one thing, where many newcomers are scratching their heads.

Without going more into detail here, this approach has two main advantages.

First: Global State Becomes Testable

You can now test your state completely isolated from your components. You import the reducer and the action into your test file. Since they are pure functions they have no dependencies whatsoever. You can than define a initial state object and pass it to the reducer, together with an action object. This way you can verify that a certain action mutates the state correctly without ever mounting a component. Since the state logic is tested already, all you have to do in the components, is to ensure that certain actions trigger the dispatch function with the correct action object. The dispatch function does not really have to executed and can be mocked.

Second: Global State Becomes Easy To Debug

Since all your state mutations pass through a reducer and the passed action object contains information about what has to be changed and how, it is easy to track state changes. If you would mutate state directly and at some point wonder, why the state looks like it looks, you will have a hard time debugging, since the change could come from anywhere. With redux, you can move the debugger or logger into the reducer and observe each and every action of the state.

So redux definitely has it's advantages and especially shines in large scale projects where many programmers work on the same codebase and where we have big, deeply nested states.

When Not To Use Redux

Still, having to add an action function, modify the reducer and then connecting the component to toggle a boolean value, just does not feel natural and especially for small scale projects and prototypes probably is just overkill. But also for large scale projects there are alternatives. Let's have a look.

Alternative: Reactn

ReactN is a extension of React that includes global state management. It treats global state as if it were built into React itself -- without the boilerplate of third party libraries.

Damn that sounds amazing. Initializing the global state works as follows:

With reactn you can simply refer to this.global instead of this.state and this.setGlobal instead of this.setState and you are done. setGlobal can even handle async data.

Using hooks? No Problem.

For most people this approach should be much easier to handle, since it mirrors reacts default behaviour.

With reactn you can even use redux developer tools. Depending on your state, your app probably re-renders too often. But even then you can make use of withGlobals HOC and fallback to a redux like approach, similar to mapStateToProps. But you can do it where and when it is needed.

Alternative: Pullstate

Pullstate has similar syntax. However, it has no support for class components. It only delivers a third party hook for global state management.

Initializing Global State

You can define as many stores as you want and they would be completely seperate.

Reading Global State

To access values from the state, you call useState on your imported store and pass a reducer function as callback. The s here is the complete store and you simply return the value, you want to access.

Mutate Global State

Alternative Mobx

How could I not mention Mobx here? The previous libraries where quite small and you do not know for sure for how long they are maintained. However, they also have quite small footprint and for most projects they will speed up initial development time a lot. However, if you want an actively maintained third party state management library, which is ready for large scale production apps and still want to avoid using redux, mobx is one of very few options.

So with Mobx you basically depend on other third party libs, like mobx-react-lite, similar to 'react-redux'. You have to wrap your components in a observer function and use useObservable to initialise. Afterwards you can modify the store directly to trigger re-renders. To make it global you would have to define the store outside of the components and pass it into it via props.

Boost Your Productivity in VSCode with 16 shortcuts

oshell — Sat, 14 Mar 2020 21:19:22 +0000

When you code on a regular basis or even code for a living, it makes a lot of sense to get familiar with your IDE, and its shortcuts. Even better: customise your IDE to your needs.

Essential Shortcuts

To work effectively with any IDE, there are a few things you want to be able to do, without leaving the keyboard. In this article we will go over the most essential shortcuts for search, navigation and editing files.

Since default shortcuts are different on Windows and Mac, I will give you the Command name and my recommended shortcut in a nice formatted table, which you can use as cheat sheet. modifier in this context just means you could use anything like alt, ctrl, opt. You can search the commands under Settings > Keyboard Shortcuts and assign new Keybinding by double clicking. Furthermore I made some sample gifs, showing how it looks in action linked under each table.

You can also watch this short video and use the tables for later reference.

Search

Command	Recommended Shortcut	How to remember
Go to File...	`modifier`+`p`	search project file
Search: Find in Files	`modifier`+`shift`+`f`	search files in project
Find	`modifier`+ `f`	search in file
Go to Symbol in File...	`modifier`+ `s`	Go to symbol

The commands above help you quickly find a certain function in your code. If you know which file it is in, use modifier + p and jump to the file, then use symbol search modifier+s to jump to the function. If you do not know the file, search the whole project with modifier+shift+f.

See VSCode Search in Action

Navigation

Command	Recommended Shortcut	How to remember
View: Quick Open View	`modifier`+`1`	Open View in 1st Panel
View: Open Previous Editor	`modifier`+`q`	sidestepping left with WASD controls
View: Open Next Editor	`modifier`+`e`	sidestepping right with WASD controls
View: Close Editor	`modifier`+`r`	remove current editor
View: Move Editor into `directon` Group	`modifier`+`m` `arrow key`	move current editor
View: Focus Editor into `directon` Group	`modifier`+`f` `arrow key`	focus editor
View: Toggle Integrated Terminal	`modifier`+`t`	focus terminal
Go to Line...	`modifier`+`L`	Go to Line
cursorWordEndRight/cursorWordStartLeft	`modifier`+`Arrow Key`	-

See VSCode Navigation in Action

With the above commands you can quickly focus any of the side bars with modifier+1 and jump back to editing by opening a file or using modifier+f Arrow Key to focus one of the Editor Groups again. You split the editor view by using modifier+m Arrow Key and move focus between editors using modifier+f Arrow Key. Within each editor you can jump between open files using modifier+q and modifier+e. You can then use previously mentioned symbol search or modifier+L to jump to a certain line. Within any line you move the cursor using cursorWordEndRight/cursorWordStartLeft. Using modifier+t you can focus the terminal to run your application or run any test commands.

Editing

Command	Recommended Shortcut	How to remember
Add Selection To Next Find Match	`modifier`+`n`	select next occurrence
Move Line Down/Up	`modifier`+`Arrow Key`	-
Expand/Shrink Selection	`modifier`+ `shift` `Arrow Key`	-

See VSCode Editing in Action

The modifier+n helps you with refactoring and multi-cursor editing. With Move Line Down/Up you can move certain lines or complete code blocks. The Expand/Shrink Selection is quite smart and helps you selecting complete codes of block, before moving/replacing them.

Testing Function Components with Hooks Using Enzyme

oshell — Tue, 19 Nov 2019 19:23:18 +0000

https://link.medium.com/AHwXRtiAK1

Fast, maintainable and scalable frontends

oshell — Thu, 10 Oct 2019 22:08:06 +0000

A few month ago I wrote an article about this topic, the things you have to think about and possible options to consider. Gives you guidance on what tech to choose and why.

https://link.medium.com/zacbePznG0