2
virtualdev
141d

sigh, I guess I have to learn javascript.
u know, as a devop/prod/backend engineer, i thought i would be exempt, but world wide web of "one more thing a dev should do" won't let me have it :(
so, any of you have a quick and dirty guide to catch up with the latest essential components of javascript as an experienced dev who absolutely knows nothing about js?

Comments
  • 3
  • 1
    my condolences
  • 2
    always hoped i never had to use this weird language seriously in my lifetime.
    Ended up getting payed working with it

    ¯\_(ツ)_/¯
  • 2
    w3schools

    it's not that bad tbh, better to know what your team is dealing with anyway
  • 1
    I would also look into TypeScript once you’ve got the basics down. Typescript is a superset that allows defining static types that get checked ahead of time. I wouldn’t touch JS with a 10 foot pole for a large-scale project if Typescript didn’t exist
  • 1
    I used all your suggestions and I have an action plan. Thank you all, even your empathetic words help, tbh :) <3
  • 0
    @thebiochemic What was your experience like? If you don't mind sharing.
  • 0
    @darksideofyay thank you for bringing that up, I'm a team lead so this is an insanely valuable angle :)
  • 1
    @virtualdev it was fairly simple:
    Incomplete, misleading and straight up wrong documentation and a fucked ecosystem.

    I always found it hilarious, that a lot of js packages wanted you to do some stuff with npm, but all of them together failed to tell me, wtf npm even was, and where to get it, you know... how to install it... in installation instructions.

    To the language itself (and i dont mean TS), you have to constantly find out, what the structure is of whatever youre working with is, because JS has no strict typing. So you basically end up guessing and/reverse engineering with the browser, wtf the stuff looks like. Docs usually were like Skyrim Quests.

    Once you found out, what npm is, and realized, that the version, you installed from your package manager is outdated, therefore downloaded the newest version yourself from some random github, you will have your mind blown about how many packages exist, and how quickly they will fill up your drive through node_modules.
  • 1
    @thebiochemic this is probably the most terrifying confirmation of my expectations LOL, thank you for sharing. I'll brace myself :/ the reverse engineering thing is why I avoided picking it up for so long .... I thought I was just visually challenged lol
  • 1
    @virtualdev to be fair, writing a little script here and there is fine (and initially was it's use case), but actually developing web/other software with it is pain.

    On the bright side, the internet is full of tutorials and help, one might argue, too full.

    But yeah, i wish you good luck with learning JS ✌️
  • 2
    Your company might mandate that you learn JS, but the industry certainly doesn't. I've not had to touch it in any backend roles I've had.

    Granted most devs should probably know the bare minimum in it just from a "common knowledge" standpoint, but if my employer made me do any serious work in it I'd be looking somewhere else.
  • 0
    @bigmonsterlover I abandoned the fork of the project that requires this of me, and decided to learn using your sources on my 4 weeks off to find a new job LOL. :D

    Our fe stack is angular and react, and I learned the bare minimum to argue with our management to revise their decision w/ the platform team, so.. just as I expected: they all knew nothing, to the point where a simple understanding and a guess got them to lay off me for a whole week... man.
Add Comment