SOP - Semicolon is OP

SOAP - sleep-oriented-advanced-programmer :D

aka tinder developer :D

REST

Getting enough sleep should be Standard Operating Procedure (SOP)

Can you explain nr2

9 minutes saved, thanks :)

keep note pad next to bed to write ideas down when you wake with them.

@@mikeCavalle problem is when you have the best ideas in the shower

@@dakrontu in the shower you have a whole foggy glass door to write notes on. :-)

Night

Ctrl+home and ctrl+end work on literally any text editor (even Microsoft Word)

@Gabriel Beauchemin he showcased some equivalent Vim shortcuts. My point is you can do that in any text editor without any setup required.

That's why I mentioned these two shortcuts SPECIFICALLY. Ofc there are many others that are not so common and readily available, I just thought it weird to mention something that is everywhere else as a Vim perk.

@@macurvello nah vim shortcuts are just op stop comparing them to these shitty cuts

@@macurvello obviously vim can do a lot more

You Sir, are a true developer !...Just like me

@Yog Sothothologist that's incorrect, I also never had any uses of algorithms. If you're a web developer or SE algorithms/data structures won't be much of use for you. You don't need to know the language syntax inside and out that's what documentation is for. You just need to know how to apply the knowledge itself and when to use what where.

@Yog Sothothologist SE means software engineering. github.com/Serenity1337 here's my github.

@Yog Sothothologist hey man I can answer some questions for you if you want my Reddit username is Heavy_Hole, pm me there

​@@CapeSkill There are tons of work for people that can only do basic programming, where you do not need any real knowledge of algorithms and datastructures. That work also tend to be low level work that you can hire just about anyone for that has spent some time with the specific technology you want to have them programming for, which means those jobs would tend to be entry level jobs. If you need to solve some bit harder problems, then you will have a hard time finding an elegant solution or even a solution at all. If you want to transition from writing "meh" or "okay" code to "good" or "great" code, then you need to understand a good deal of algorithms, have a good understanding of the underlaying systems, get familiar with the many different ways to write code and practise enough to know when to apply each of those tools. How do I know this? My work includes rewriting code written by decent programmers, who have their focus on the real life problems their programs are about, and are less focused on the higher end of programming, and getting it to run much faster is not unusal, heck I have even had a 100000 times speedup before.

lol he kinda looks like him tho 😂😂

ROFL

this is a satire even if it wasnt meant to be one. I had so many great attributes of you in mind only from watching your videos, but you chose two poorly argumented and one obvious advantages and putting them in a click baity title made this the worst video about programming I've seen this year

i agree. but those are really important to enjoy programing.

I'm fast with a mouse. Fuck Vim.

@@JonnyBeoulve not.badass.dude

It really depends on what you are building

Could you elaborate?

@@0x6e95 Some examples: 1) proper variable names that are understandable without comments 2) modularization, aka separating it out into multiple files/namespaces etc. 3) write stuff so that it is testable, e.g interfaces, dependency injection etc. 4) exception handling; TLDR: writing something fast encourages you to take shortcuts

@@samuelschwager Those are all valid points but I sincerely doubt any developer worth their salt would ever code in a competitive programming style for production software. You would usually only delve into CP after you've dealt with writing good production ready code so I don't really see how CP would encourage you to employ lazy coding practices for writing prod ready software. I can see that being a problem if a beginner's first foray into code was through CP but that's rarely the case.

@@0x6e95 It depends. The exercises in CP are usually quite small compared to large legacy production software. So I guess there are people that get started in CP (the easier problems) and might get hired into a 1 person team with no one who reviews their code ;)

@@0x6e95 Can we call it competitive programming and not CP...

"Actually when i was younger I was thinking the same that keyboard shortcuts are that u are expert, but today, I thinking good developers are those who can name variables very well, reuse existing code, and write their code like writing a poem, without bothering with too much comments." Both are important. And yeah, comments should never be used to explain what the code does, only why it does it. Function names are there to explain what is being done, so use those. "And yes one more thing, thinking with tests in mind, this will make u more better and valuable developer, all other things will came into place." Make sure to write your unit tests *BEFORE* you write your code. It will make you think about all the different edge cases that need to be covered and allow you to streamline your development process, as you'll always know what you are working towards.

Although I am very young, I agree or even think you have understated a lot. I think SOLID and designing maintainable codebases are far more important the data structures or algorithms, and that's coming from someone applying for DS/Algo centric PhD programs and jobs. Most code has zero need for novelty and should be built to be easy to understand and extend, rather than to be efficient or elegant. I used to do carpentry and this is somewhat akin to my observations there, 99% of the cuts and joints made on a job are simple, and should be done consistently and accessibly. For the 1% of complex work, you can have a reliable person who knows how to do that perfectly. In CS this seems to be akin to just about any library vs the work built from the library. I recently ran into problems with this in an open source lab product that I am building. Every student I attempt to incorporate has a fantastic understanding of algorithms and data structures, but no idea how to name things, organize code for reusability, or work with version control with large projects. TDD would be a huge plus if my peers could even stick to SOLID and a basic project architecture (what is a model and what is a view? - good luck finding a kid who can answer that). In this project about 600 LOC rely on things learned from data structures or algos, around 10,000 rely on SOLID and a basic, easy to understand architecture.

lol

LMFAO

yup, other 90% of time we watch videos on youtube :)

Yeah. Vim is fun and all, but it is _definitely_ not a significant contributor to developer performance. Lol. Only a beginner would think that.

@@jason_v12345 Yeap :) I remember watching some amateur reviewing some kind and one of his points was that writing bool==false instead of !bool is a sign of bad programmer. This Vim argument is on the same level :D

Then how to solve a problem in 30 minutes in an interview?

@@mubba1992 solve problems, more you solve, faster you do it.

@Dave B Well I agree with that for most common problems you just apply existing patterns. What I was refering to is the design of a completely new solution (Service, application, system, whatever). Most of the time I think about architecture, how to split into modules and components, which interactions will I need between them, how will my DB schema look like. Once I have this figured out, writing out code is not an issue. My point is, when developing a solution, writing code is like 1/3 of my time. And I have almost 7 years of professional job experience as a software engineer. I'm not refering to simple things like add another endpoint to some REST API to fetch some entity from DB, this is almost trivial in most cases. I was refering to designing and implementing a new piece of software, a complete solution from scratch. I have never found that the speed of typing code is the limiting factor, at all. For example, recently I had to implement MVP solution at my company, I spent 4 hours in front of a whiteboard, together with my teammates, brainstorming about design. Once we had all figured out, I coded entire service including flyway schema management, dockerized database for testing, full business logic in 20+ components with all relevant entities available over REST API CRUD. All of this in about 2h of coding. It's the least of my problems. I'm using Intellij Idea for my job, I'm programming backend apps in Java. If you were wondering.

@Dave B Not what to build, but how to design it. When you have a system with hundreds of microservices in a giant platform, most important part of the job is to figure out how this piece of a puzzle fits into the bigger picture. I only speak for myself I can't give you any numbers how other dev teams inside my company are doing. But me persoanlly I can give you 2 scenarios: 1.) New feature (small), optimization, bugfix, dependency upgrade: 10% thinking, 90% coding, but overall it's not a lot of time. 2.) Designing a new system/service/product: 60% planning, brainstorming, gathering data, meetings, rough design overview, and maybe 40% actually implementing it. In any case, speed of typing code is not a big factor, most of the time I spend testing my code, waiting for test to be done while thinking about the next case (TDD). I have never felt that my IDE is the bottleneck. That is my personal experience and honest opinion.

@@janklatka1967 you realize that Vim is by no means the only editor with those abilities, right? I can do all that in VS and more from the keyboard

I agree and disagree. Speed is not the most important criteria to look for in a programmer. However, if a programmer can't keep up with a certain project in a competitive environment it might not be good, also certain projects have a short deadline. After all this depends on where and what you are working for.

@@hamoodrex But what do you mean by speed? I agree that programmer must be fast in finishing projects, and IMHO 90% of that is thinking without writing anything, then 10% writing the actual code, tests, docs, etc... And also, when you need to debug something or refactor, there is nothing that can beat heavy IDE. Yes, they are slow and often bloated, take a long time to start and index files... But If I had to refactor a 1k+ files java project using VIM, I would rather drink poison.

IdeaVim is way better IMO

@@slimestoneexpert9804 but that's for jetbrains ides

just use the terminal :\

I haven't gotten into them yet, but I agree I'll probably love them

This applies to any IDE or editor. I't like saying VSCode is great because: "Once you get used to the keys typing becomes really efficient and satisfying.". Pick your favorite, it's not that important. The best IDE is the one *you* know the best.

How does design pattern help when you code in JS?

@@larrycoleman8149 go study software engineering dude.

yeah I recently got into vim and its so amazing. Say you are working on HTML or XML or whatever and you are in middle of div tag and you want to change that tag to section tag or something, you just press a shortcut and boom it changes. You don't even have to move your cursor. And ctrl+alt+shift selection is what I used to use a lot before getting into vim, but that's one extra step. Like if you want to select entire line, you press home key and then press shift+end key and then you can cut, copy, delete etc. But with vim, you just press dd or yy or cc to delete or copy or change the entire line altogether. Vim also has a ton of awesome plugins that allow you to change things like snakeCase to camelCase etc. I use it a lot while writing JPA code in java. And the best thing is that vim is ubiquitous. I can take these shortcuts with me everywhere. Today I might be programming in java using Intellij. 2mrw I might get a new job where I need to work with python using Pycharm or use react with vscode or C# with Visual Studio etc. But I don't have to relearn ide specific shortcuts, as long as I have vim(or vim extensions in those IDEs). And regular expressions are also very productive. I sometimes have to take DDL and create POJO(java classes) out of it. And some of these DDLs have 100-200 columns. If I had to type it would take a long time. With regex find and replace it takes less than 5 minutes. I can convert between DDL to Pojo and vice-versa very easily.

@Dr1ver key maps can be changed... 😑

The war's not over yet

VSCode has a feature built in to show keypresses. Cmd+Shift+P > Developer: Toggle Screencast Mode

tomorrows video is for you!

kombucha dissolve my organs

what the heck is motorola 68k?

@@blasttrash they probably mean motorola 68k assembly idk

Same. But I woke up at 2 am. Went to sleep at 6pm.

just sleep until 11:30 :)

I agree and It is fun and satisfying to use. that's about it

for me i just hate using the mouse for anything

True. I love vim but it's for some reason easier with sublime keybinding

possible solution: don't have kids, screen out positions that do not prioritize your life?

So don't have kids then.

@@omar9987 thats a stupid solution, kids are our future. A better solution is: staying at home and raising your children right while the man provides.

@@daonlyowner6631 The future is the sun devouring the earth.

@@omar9987 Oh thats settled then. Feel free to lead by example and take yourself out.

Vim knowledge is not "necessary," but neither is a color display or a comfortable keyboard. But vim knowledge will probably make you much more productive. Vim keybindings are not "shortcuts," it is ita own language of interfacing with a text editor.

@@ruhnet Vim is not to vscode what a color display is to a black and white display, that's a gross exaggeration. You can do almost everything without vim. That means you don't have to spend the time it takes to learn vim and still be super productive

​@@doctormanhattan7408 You can be "productive" with Notepad or Nano. Vim, properly configured and used, is more efficient than any other editor that I know of (including VSCode). VSCode is of course extremely capable, and so are many other editors (Emacs blows anything out of the water though), but VSCode is bloated and not fast (comparatively of course--in most situations it's "fast enough"). So yes, while you can do anything with VSCode, (some things better than Vim) it's just not the best or most productive/efficient editor. And if you read my comment again, you can see I didn't pick color/bw display as an exact strict proportional representation lol (I also mentioned "comfortable keyboard"); it was just an analogy. So relax... and use VSCode if you want to haha :-D

no, just dive into algos

Yes, I take breaks and think a lot too but when I'm manipulating and refactoring code vim is great

I use cmd+p to navigate files gist.github.com/benawad/1e9dd01994f78489306fbfd6f7b01cd3

The key binding is ctrl +curly braces. Also you can use ctrl+f and ctrl+b.

What's the difference between that and just putting a debugger inside an if statement?

@@doctormanhattan7408 there is none, except that you can do it in runtime.

YES, It's the vim way to do it. Never leave the homerow.

benawad.com/vim

@@bawad which coursera course is best for learning algorithms? My college teaches me nothing or I just forgot them right after my tests, please tell me, thank you so much

and there's Ctrl + Left/Right arrow to move between spaces in a line

Some world changing features that are not present in every editor.

yeah it's a markus, I like it

lets hear your advantages then. I am really curious.

That is normal, you have to concentrate in what you think that makes you slow and find a solution, maybe creating some commands or installing plugins. For example I found vertical jumping to be very slow until I found plugins like easymotion or lights peed if you use neovim. Other personal example is creating directories. it was as slow as with a GUI editor, and even tough there are plugins for this, my personal solution was to use the terminal. Find what bother you and change it, Atom motto is "the hackable text edito for the 21th century" I believe they put "...for the 21th century" because of emacs and vim, these are very customizable editors

tmux is great

copy-mode-vi for life

I'd be missing a ton of features that i have in VSCode or with it's extensions that are either kinda hard or clunky to get working, or just don't exist like LiveShare for example.

kzfaq.info/get/bejne/qp-bhrea1s65lps.html

docs

Tried that a few times and every time woke up 4 hours later with a headache xD

That's the whole point of this vid, there's an easily readable irony... Like watching TechLead but actually funny.

@Blaxer XO alright thanks! Yea I have consolas already I use that everyday it looks so nice and clean to look at!

kmecu Depends on the type of work you want to do. If you want to build big systems quickly with existing tools or with a team, design patterns. If you want to build new systems and products, DS/Algo. I personally put both of these things in an architectural knowledge category along with memory management and process optimization. Knowing all of these things is "important", but they don't necessarily make you a better programmer. Knowing good programming practices like SOLID is probably more important than any architectural knowledge, as you will be a good programmer by default in any language or architecture. It will help you implement big projects that you are proud to show off a lot more than algos or patterns.

das keyboard