Hey, Sorry for being slow to get back to you. Been a busy few days.
How are you defining the two? In my mind, a web developer is just a more nuanced type of Software Engineer, focussing on UI/UX and backends. There's certainly a big crossover though.
Algorithms are a funny one - 99% of the time you don't need them, yet people insist on assessing with them.
Hi,
No problem at all, completely understand with the run up to Christmas etc.
I'm at the interviewing stage with companies and my experience so far is that, when going for a web developer role you get some kind of assignment where you are asked to build a basic front-end or add some functionality to an existing front-end. When going for a software engineering role you get asked design patterns, more complicated algorithms and O notation etc (I had a couple leaning towards software engineering recently and I was thinking, what the heck, I haven't covered that yet do I need to??) so it can get a little confusing and demoralising looking at the mountain of things I don't know.
I would like to take a look at your assignment if that's ok, it's all practice and helps me to understand where my gaps are so I can be better prepared next time?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey, Sorry for being slow to get back to you. Been a busy few days.
How are you defining the two? In my mind, a web developer is just a more nuanced type of Software Engineer, focussing on UI/UX and backends. There's certainly a big crossover though.
Algorithms are a funny one - 99% of the time you don't need them, yet people insist on assessing with them.
Hi,
No problem at all, completely understand with the run up to Christmas etc.
I'm at the interviewing stage with companies and my experience so far is that, when going for a web developer role you get some kind of assignment where you are asked to build a basic front-end or add some functionality to an existing front-end. When going for a software engineering role you get asked design patterns, more complicated algorithms and O notation etc (I had a couple leaning towards software engineering recently and I was thinking, what the heck, I haven't covered that yet do I need to??) so it can get a little confusing and demoralising looking at the mountain of things I don't know.
I would like to take a look at your assignment if that's ok, it's all practice and helps me to understand where my gaps are so I can be better prepared next time?