4 ms·
Not just JS. JS is an enormous ecosystem, so it shows this issue, but pretty much all tech (and other industries, as well), have the same problems. We can have
by ChrisMarshallNY 6y ago
Not just JS. JS is an enormous ecosystem, so it shows this issue, but pretty much all tech (and other industries, as well), have the same problems.
We can have problems when folks start suddenly painting "The New Thing™" over classic designs and architectures.
In my experience, that's even worse than rewriting everything.
Also, it can become a requirement for hiring, because some manager, or their "top tech," have suddenly latched onto a technique/technology they encountered at a conference.
I remember applying at a company, and they gave me a "take-home" test.
Fair 'nuff. I like these better than the silly "draw spunky" tests that are so en vogue, these days.
They said I needed to use a certain third-party library, and use MVVM, or PM. That made no sense to me. It would result in the dependency being "married" to the application.
In my response, I used dependency injection to add the third-party library they wanted me to use. I wrote the app in about three hours, and incorporated the library (which is a great library, but one I had never used before). I delivered an app that met their specs -very quickly-, and of remarkably high quality. It also featured the ability to easily "swap out" the dependency (which is a huge reason for using dependency injection).
Dependency Injection is not a new thing. I think the name may be a bit new, but it's a fairly classic pattern that is a great way to encapsulate dependencies (which is something I always do).
It Freaked. Them. Out. I have no idea why. They literally shredded my résumé, at that point.
I have my suspicions why. I think they found out something else about me during the process (my age), and that may have been a contributing factor.
- memexy 6y agoI once worked with a group of people that were afraid of makefiles. I doubt it was your age. People are always afraid of things that are unfamiliar. This applies to snakes and spiders just as much as it applies to programming languages and associated technologies.
- ChrisMarshallNY 6y ago> I doubt it was your age. Wish I could share your confidence, but I have run face-first into this phenomenon. [...removed some stuff that I don't feel like backing up...] We are an unpopular bunch. It used to get me quite upset, but I’ve learned to make it quite clear that I am no youngster; right up front. Avoids stuff like what I mentioned.
- memexy 6y agoReally? Do you have specific examples. In my experience hacker news tends to be much more friendly and sympathetic towards older programmers.
- ChrisMarshallNY 6y agoI'll withdraw the post (rather than spend a bunch of time, hunting down comments that just get me depressed), but the tide may be turning. Now that the VC money may not be as easy to get as it once was, there may be a bit of a demand for software that ships, as opposed to glossy slide decks. Us old farts ain't so bad at that.
- memexy 6y agoIndeed. Focus on fundamentals never hurts.
- ptx 6y ago> and use MVVM, or PM. PM?
- ChrisMarshallNY 6y agoPresentation Manager. Sorry. That was the term I learned, many moons ago. I learned it as a Microsoft pattern, and I used it to create Web-focused SDKs. The more familiar one is MVP. Really, if you are talking about creating a UIKit or AppKit app, you should use good old MVC, even though it’s “square.” That’s because it is the pattern the toolkit was specifically designed to implement, and other models actually introduce dangerous departures from the norm. SwiftUI and React are much better for MVVM or MVP.