Hacker News Reader

Comment by tobltobs | Hacker News Reader

"I feel like people who say "just use the dom" don't actually have enough experience to know why that is such a bad idea."

"You people really are kidding yourselves. I feel bad for whoever is paying your salaries."

"Honestly, it just sounds like you are bad at managing your own software projects"

"I'm really glad I don't have to work with people who think like this."

"Both are signs of inexperience."

"I guess I won't be hiring you then."

------

If your coding skills are as big as your mouth you must be a kind of coding god.

View on HN

I am very good at what I do.

I have had lots of these conversations with other people who think they are good at what they do.

This line of thinking kills companies, because the prototyper they hired for their "MVP" doesn't like frameworks. A year later he/she is gone and I'm rebuilding their app as an angular app.

You don't have to agree with me, but I am right. Millions of of dollars in contracts and a resume full of happy returning clients says so.

I'm not going to engage you on what you do, but you need to re-read some of the comments you've made. A lot of it is too hostile / oddly opinionated to be taken seriously, regardless of message. Whatever it is, it's not good communication.

I am not an evangelist, I'm not trying to win a popularity contest in this thread.

If people choose not to listen to what I have to say it has no impact on me at all. I will continue making a living off their mistakes.

> a resume full of happy returning clients

You mean the people you refereed to as lacking technical expertise that you profit from? "Happy client" does not equal "superior code". Often clients will be happy just seeing the page load.

You implied earlier that a be-spoke js app by definition is spaghetti, poorly documented and generally inferior. I can't subscribe to that idea. I've seen the reverse as true also.

Risk of failure is what everyone wants to avoid. Another risk to avoid... Mediocrity. MVP is mediocre by definition, and the quickest way there is to slap a few frameworks on top of each other. Bells and whistles yet more.

I suppose striking the balance is what matters, and "right tool" and all that. But the right tool could indeed be a be-spoke app.

> You don't have to agree with me, but I am right. Millions of of dollars in contracts and a resume full of happy returning clients says so.

They tell me that you can cover the tracks of your desasters long enough to move on, so that problems surfacing later are attributed to the maintenance programmers and not you, even if your "great" choice of frameworks were the real reason.

Reply on news.ycombinator.com