Not sure I'd call this a book. It's a colossal link dump.
There could be a sibling publication containing links to 1000 MOOC courses calling itself "The Renaissance Man Handbook".
Front-End Developer Handbook
51–60 of 73 posts
Re: Front-End Developer Handbook
#52The title should be Web Front-End Developer Handbook. Native desktop, mobile, TV and infotainment systems are also front-end.
This is why I prefer the title UI Developer. It abstracts away the particular technology of the moment, and recognizes the commonality of all human-computer interface development.
Re: Front-End Developer Handbook
#53Earlier quoted context omitted.
> "Some sell out completely to Typescript and the Microsoft way of doing things" > "this trend is subjective dogma not objective value" Ironically, the author own phrasing is not objective and somewhat hypocritical. S/He described the use of Typescript as "selling out and the Microsoft way of doing things". S/He's trying to leverage anti-Microsoft sentiment to boost her/his argument. Feels more like a smear campaign…
To be fair, the anti-Microsoft sentiment didn't just pop up out of nowhere. I've been burned by Microsoft's bullshit so many times that I will go out of my way to deny them any semblance of power, lest they try to leverage it for some new anti-consumer vendor lock-in scheme. How's that old saying go? Fool me once, shame on you. Fool me 47 times, shame on me.
To be fair?!
I was addressing the phrasing and lack of objectivity of the Typescript statement. At no point did I discuss the merits of anti MS sentiment.
Yes I agree with you that MS has burnt people in the past. At the same time it's not binary so 100% of MS != evil.
Re: Front-End Developer Handbook
#54"A whole lot of developers adopt static type checking for mostly subjective reasons or band wagon emotions. Some sell out completely to Typescript and the Microsoft way of doing things while others take on a slower approach with Flow. One thing is for sure, most developers don't need types, they are simply complicating already complex problems and solutions. Like most things, most of this trend is subjective dogma no…
I had an epiphany recently when I realized that I had spent about 40-50% of my time on a recent project writing type checking conditionals and unit tests that would have been obviated by using a type system. I am considering typescript for my next project.
Re: Front-End Developer Handbook
#55"A whole lot of developers adopt static type checking for mostly subjective reasons or band wagon emotions. Some sell out completely to Typescript and the Microsoft way of doing things while others take on a slower approach with Flow. One thing is for sure, most developers don't need types, they are simply complicating already complex problems and solutions. Like most things, most of this trend is subjective dogma no…
Agreed.
There are trade-offs between choosing typed and non-typed languages. It’s not wrong to prefer one or the other. But to accuse the other side of selling out or not having objective reasons for the choice is naïve.
Don’t assume that everyone who disagrees with you is stupid. It only demonstrates that you lack an important skill of critical thinking: the ability to consider others’ perspectives and understand them.
Re: Front-End Developer Handbook
#56Earlier quoted context omitted.
To be fair, the anti-Microsoft sentiment didn't just pop up out of nowhere. I've been burned by Microsoft's bullshit so many times that I will go out of my way to deny them any semblance of power, lest they try to leverage it for some new anti-consumer vendor lock-in scheme. How's that old saying go? Fool me once, shame on you. Fool me 47 times, shame on me.
won't get fooled again :)
Completely OT:
Unfortunately I can't hear that song anymore without picturing the opening scenes of CSI Miami.
Re: Front-End Developer Handbook
#57Earlier quoted context omitted.
> "Some sell out completely to Typescript and the Microsoft way of doing things" > "this trend is subjective dogma not objective value" Ironically, the author own phrasing is not objective and somewhat hypocritical. S/He described the use of Typescript as "selling out and the Microsoft way of doing things". S/He's trying to leverage anti-Microsoft sentiment to boost her/his argument. Feels more like a smear campaign…
To be fair, the anti-Microsoft sentiment didn't just pop up out of nowhere. I've been burned by Microsoft's bullshit so many times that I will go out of my way to deny them any semblance of power, lest they try to leverage it for some new anti-consumer vendor lock-in scheme. How's that old saying go? Fool me once, shame on you. Fool me 47 times, shame on me.
I'm not a Microsoft hater but I also haven't needed their software for my job in quite some time. I am however a Microsoft Project hater (don't ever try the auto-level resources function). But someone was demonstrating (Terraform I think) using Visual Studio Code and I fell in love with the editor. It's now my primary IDE, it's Microsoft and it's completely OSS.
Re: Front-End Developer Handbook
#58Do other devs tend to agree with the idea of full stack being a myth? "A developer who can code the front-end, back-end, API, and database isn't as absurd as it once was (excluding visual design, interaction design, and CSS). Still mythical in my opinion, but not as uncommon as it once was." I've been FS for most of my career, mostly the result of working in smaller dev teams where you had to own product from top to…
I'm with you, what do you call someone who can build and ship the back and front end of a working application, if not a full stack developer? Because its pretty obvious a bunch of these people exist,
Most small/middle companies hire people with a CS degree who can create a data model, some APIs in any language and then build a JS web app calling those APIs. Well, at least that’s how companies work in France. Not sure what’s mythical about these profiles, they are the most commons from my experience.
Re: Front-End Developer Handbook
#59"A whole lot of developers adopt static type checking for mostly subjective reasons or band wagon emotions. Some sell out completely to Typescript and the Microsoft way of doing things while others take on a slower approach with Flow. One thing is for sure, most developers don't need types, they are simply complicating already complex problems and solutions. Like most things, most of this trend is subjective dogma no…
> "Some sell out completely to Typescript and the Microsoft way of doing things" > "this trend is subjective dogma not objective value" Ironically, the author own phrasing is not objective and somewhat hypocritical. S/He described the use of Typescript as "selling out and the Microsoft way of doing things". S/He's trying to leverage anti-Microsoft sentiment to boost her/his argument. Feels more like a smear campaign…
He/Him. The author has a clear preference[1], please use it.
Re: Front-End Developer Handbook
#60"A developer who can code the front-end, back-end, API, and database isn't as absurd as it once was (excluding visual design, interaction design, and CSS). Still mythical in my opinion, but not as uncommon as it once was." I see this attitude expressed a lot among people who identify as "front end" developers and it seems like psychological projection to me. I would count myself and a number of close friends and asso…
Agreed - almost every developer I know can code full stack. They are typically better at some parts than other, so they choose to specialize, but the full ability is there. I see it even more often outside of the startup world - in Enterprise IT, you normally not only know the full stack, but multiple products at each level to support all the products that end up running inside a large company. Again, you are not an…
[deleted]