hey, whatâ€™s up, john sonmez from simpleprogrammer.com. i have a question for you about web developmentor software development. let us choose. this question is fromâ€”oh, this is a veryinteresting name. i think itâ€™s lyubomir. thatâ€™s pretty cool. sounds like he could probably on lord of therings or something, sounds like an elfish name lyubomir or maybe a dwarf. anyway, he says, â€œhello john!â€
exclamation, i like that. start with an umph! â€œi really like your videos and the advicesthat you are giving. wish you the best and a lot of success toyour productive channel.â€ thank you. â€œi am a 19 year old male, who is about tostart university in 3 months with major in informatics. i saw the curriculum of it and i am goingto study a lot of c++ and java. the problem is that i want to become a webdeveloper (probably backend), but i also love
software programming, using algorithms andloops. i had little experience in c++ programmingin the past for about 3-4 months and i find it really cool and fun. on the other hand i like web development too,but i suck at design. my first question is what should i choose:web development or software development? can you go in depth about their pros and cons? can i learn c++, java, etc. and few web languagesor do i have to specialize in one area? and can i be a frontend developer withoutdoing design and working with softwares like adobe photoshop?â€
i already answered the second question. as far as web developer iâ€™m not going toreanswer that but you can definitely checkout the video that i have about can you be a webdeveloper without design skills. the answer is yes, you can. but now, to choose between software developmentor web development. itâ€™s kind of a nitpicky phrase. is there really a difference there? i think what heâ€™s talking about is reallydoing kind of backend type of development versus frontend.
i did a video on backend versus frontend. you can check that out here just to get somemore context. but between choosing the 2, it doesnâ€™t reallymatter all that much. what matters is the specialty that you pickand this kind of addresses the bigger question here is what are you going to specialize inand what are you going to choose? because even if you just said web developmentyouâ€™re not just going to become a generic web developer, youâ€™re not just going tobecome a generic software developer. you need to have a specialty. again, iâ€™ll point you to my playlist onspecialties which you can check out here.
itâ€™s ever growing as more and more of thistopic is discussed, but thereâ€™s a lot of good information about there. if i had to choose today between going theweb route or more the backend route itâ€™s a tough one. i personally think, this is just my personalopinion here at this point. i think itâ€™s a lot more fun and interestingto work on algorithms and to work on the backend stuff. in my career, i did software development for15 years, more than 15 years. i had a lot more fun working on like comingup with the algorithms and designing the architecture,
the stuff that you didnâ€™t see because ifelt like it required more brain and more thought and moreâ€”it was more challengingto me. iâ€™ve always liked that type of challengethatâ€™s presented by that, to come up with the design of the architecture, to build thethings, to unit test them and make sure that that works. to me thatâ€™s always had the bigger appealbuilding these kind of things that are not visible but are still critical to an application. thatâ€™s my personal opinion. i think thatâ€™s more fun.
when iâ€™ve done web development i actuallydid a video on i hate web development. i was talking about this a little bit. a lot of web development justâ€”again, someof you are going to argue with this. thatâ€™s fine. thatâ€™s cool. this is just my opinion. but in my opinion what iâ€™ve seen as a lotof web development is doing crud type of stuff where youâ€™re basically wiring up stuff toa user interface and then making it work and then doing the design components and fiddlingwith why does this button not work or why
i know with react and angular stuff, thereâ€™smore architecture built into the frontend. weâ€™re kind of blurring the lines there. in that case, i could see that. i havenâ€™t actually worked a lot with reactso i canâ€™t really talk to that, but in general, i find that web development is more of themaking the things work and translating directly from the requirements, i need to build a pagewith this button that does this thing to the code and the markup that makes that happen. whereas the backend stuff that you might dothat is not visible to a ui is going to be more like, okay, youâ€™ve got these big requirementsand ideas and now you have to come up with
this architecture and stuff. that may appeal to you more. again, it depends on you. if youâ€™re creative and you like design anddevelopment type of stuff, maybe that creativity will be sparked in web development. but if youâ€™re a different kind of creativeand you like the problem solving, deep algorithm type of stuff then the backend stuff is probablygoing to be more appealing to you. thatâ€™s what was more appealing to me, although,like i said, iâ€™ve done both and iâ€™ve enjoyed both in my career.
i just would prefer, if i had a choice, ifsomeone said, â€œokay, you can only do 1 kind of development for the rest of your lifeâ€iâ€™m going to skip the web and all of the problems and complexities of that and i wantto work on the pure backend stuff. thatâ€™s just me. what about you? leave a comment below nad let me know whatdo you prefer. letâ€™s take a vote here: web developmentor nonweb development, software development. i donâ€™t know if we should divide it thatway. we can say frontend or backend.
what are you, a frontend or backend? what do you prefer? also, out of curiosity, what are you doingnow? are you doing what you prefer? because iâ€™m curious of how many of you arenot doing what you actually would prefer to do. leave a comment below to let me know. if you like this video, click the subscribebutton. youâ€™ll get more videos like this, 2 to 3a day, and i will talk to you next time.