6

Who are you going to hire in web dev position?
1. Algorithm master but new to web development.
2. Full fledged with cutting edge web dev technologies but don’t know much about algorithms

Comments
  • 6
    2 for new projects.

    1 for currently online projects.

    2 can build shits happen in quickest time.

    1 can analyse and improve on currently alive shits.
  • 8
    both, let them crossbreed
  • 1
    Web dev as in front end or back end? There are different kinds of web developers.
  • 0
    @irene in each case :)
  • 3
    @creativeJay for front end knowledge of algorithms is unnecessary and knowledge about obfuscated JS frameworks is much more in need, IMO
  • 1
    @irene knowledge of algorithms unnecessary for front-end? That is a joke I hope? All code written in a programming language are algorithms! Not knowing how to write efficient algorithms results in developers repeating themselves over and over again. Like $('.some-selector').someFunction();
    $('.some-selector').someOtherFunction(); etc. So damn inefficient. I see crap like that way too much. And it is also horrible to maintain.
  • 0
    @CodeMasterAlex Hi, Thank you for opinion. So you think for web development we need both balanced? Or do you think algorithms is more important?
  • 1
    @irene thank you for opinion :)
  • 1
    @heyheni thank you for the clear solution :)
  • 1
    @CodeMasterAlex what performance tight functions are used in frontend (aside from tons of bloat)?
  • 1
    @creativeJay I think algorithms is less important in this case. However, one needs to do proper code reviews so that when inefficient code is created the web dev can be taught how to do it properly.
  • 1
    @irene That completely depends on the application domain. In common business applications without any exciting visual interactions performance probably won't be an issue. But one should always try to write efficient algorithms, regardless of the actual application domain. One should not, by default, micro optimize all code because of performance, only do that when it is necessary, or known up front that performance is critical. However, software will suffer from continous change, what performs well today might not perform so well anymore tomorrow. Writing decent, maintainable code should always be done. And that includes efficient code as well.
  • 1
    @CodeMasterAlex if you write something performance tight in frontend you're doing something wrong.
  • 1
    @irene again, that completely depends, as always. Today there are so many single page applications and hybrid web apps. There are so many things that are perfectly valid to do on front end. Like 3d games, web based digital audio/video workstations, interactive charts, etc etc. Look around how many advanced applications provide a fully featured web based UI nowadays.
  • 1
    @CodeMasterAlex single page app is the wrong way to do things. That's the thing.

    I don't use such applications as they are sluggish. They don't belong in web page.
  • 1
    @irene I'm not a big fan of spa's but the demand in the market for that is quite high. But I don't think that many companies and experts are wrong. And such applications don't need to be sluggish at all, if they are properly designed and coded, using efficient algorithms.
  • 2
    @CodeMasterAlex thousands of flies cannot be wrong!
  • 2
    @irene I hope to meet you some day on the job. I'm sure we can have nice discussions!
  • 2
    @CodeMasterAlex I don't do front end fortunately ­čśü
Your Job Suck?
Get a Better Job
Add Comment