Discussion on "Full Stack Developer 101"

Marco Alka · 2016-08-29T13:46:48.639Z

Hey everyone out there! Hope you all have a good time! Maybe some of you know that some two to three weeks ago @georginagrey asked Hashnode: What do you think are the most important skills/tools that every full-stack software developer should maste...

I have gone back and read everything in detail now. It reminds me of how I have found learning in IT for the last 40 years, "I now know more things that I don't know and need to learn" 😀

If you don't mind I would love to know your answers on the following questions (and appreciate the time you have already given):

What editor do you use
What are the key Editor packages that you use
What do you use to store "patterns" and "code snippets" and boilerplate templates etc
Are you subscribed to any learning repositories, e.g. egghead.io etc
What task builder do you use, e.g. Grunt, Gulp, etc
What do you use to do live browser refreshing when coding
What online Git repository(s) do you use, e.g. Github
.. and a lot more questions on design tools but will leave for now

Thanks again for your time and posts.....

Yeah, it is good to know that you do not know a lot of stuff, but it's even better to know what you do not know :) I am still learning, too, so I really hope people point out stuff I am missing haha

Either Kate or Notepad++. I prefer the IDE "Webstorm" to any "pure" editor
Just the default stuff. However, I enable ES6 with enforced strict-mode
I just use my brain and I keep reading stuff again from time to time. If that does not help you, why not make your own GitHub repository with patterns :)
No. I learned everything I know from the docs and from working on projects. That's what I feel most comfortable with. Maybe that's also why I started to impose very strict rules on my code. Because I made many (bad) experiences first-hand
I am working on my own application host which should do everything automatically for me. It's a long way from being complete, but if you want to, you can take a look at it. It's called SHPS (I am currently working on the GitHub Wiki. Documenting a project is so booooring). If I had to choose one established task runner, I would go for Gulp.
I do not use live browser refreshing. I just work on code, then test it. If there is a bug, I use Chrome's dev-tools to edit the code in-browser until it works correctly, then I copy it back to my files. One might say that is sub-optimal :)
GitHub. I have a premium account, so I can hide my private stuff
Really, I do not use a whole lot of tools. I use SHPS and then edit the DB with phpMyAdmin. I use Chrome's dev tools for testing. That's about it. Hmm. I sometimes use a pen and some paper or a whiteboard. Most of the time it's just the code and me

You are welcome to ask more questions!

Wow. Thanks for enlarging on your original answer! I'm only a newbie on the path to "full stack development heaven" and posts like this both motivate and inspire me to continue on the journey.

Hey @maruru Thanks for answering my extended list of questions. I will no doubt have many more as time goes on. I've gone backwards and forwards with using an IDE but have been sticking with Atom for quite awhile now and love it. I need to learn a lot more about dev-tools and learn to use it properly as what you are doing sounds a very efficient way to do it. All the best.

Thank you for expanding on this subject, I'll most likely keep coming back to this for some time :)

There's something else that troubles me a bit and that is Dev Ops, have you dealt with this before? I know in large teams that not much of an issue, but I'm talking from a perspective where one or two developers that want to build - for example a multi-tenancy app.

Sorry, I have never dealt with Dev Ops. I am working mostly alone in my current team at work, too. But from what I learned about Dev Ops, it is not something you would implement for small teams (1-2 devs). In that kind of situation I would rather (and this is purely my personal opinion with not much knowlegde about your situation) use an agile Kanban task board with an extended backlog in order to assign tasks to other people which they might work on out-of-order. In addition, using sprints with defined milestones to sync with the other developers will help you tremendously. You might want to take a look at "zero bug development" to order you milestone items. Use the skateboard principle (MVP) to build your application and get feedback.

So you might set up a git repository, make a master branch and a stable branch. You make one new personal branch per feature and, when you are done with your feature, merge it into master. At the end of the sprint, you make sure whatever you got in master works as planned and you do not have any more bugs on your list. Move master into stable and then give it to your client for feedback while you work your next milestone.

As for the extended backlog, that's the place where you assign tests and collaborate, when you find out you have topics you need to work on with someone else (the other dev).

Since you haven't yet, I recommend creating a question to the community. I am pretty sure among all these amazing people someone has a better understanding than me :)

I study your post carefully. It is an amazing post. It is very usefull post for all students. your describing style is also better. thanks for help me. students can learn programming on <a href="programmingtutorial.org" >programming tutorial </a>

Discussion

Full Stack Developer 101

Responses(3)

Recent in Forum

Search Hashnode

Full Stack Developer 101

Responses(3)

Recent in Forum