Just remember that many popular stacks are due to marketing; often the marketing pushes you in ways that are highly profitable for whoeve...
Just remember that many popular stacks are due to marketing; often the marketing pushes you in ways that are highly profitable for whoever sells you the stack. Unfortunately, if you follow their instructions to the T, you will spend more money, and may make architectural mistakes that hold you back. (IE, be careful before you drink the kool-aide on "cloud" or whatever comes next.) Also, many blog posts are by people trying to make themselves feel important, pad their resumes, or otherwise self-promote. Tone management in a blog post can make an awful architecture sound wonderful. Other wonderful architectures may be the wrong fit for what you're trying to do. Finally: Avoid many layers of abstraction. It just adds unneeded complexity to your code and makes it too hard to onboard new hires. Carefully review all 3rd party libraries before you commit to using them. Sometimes introducing a 3rd party library to "save an hour today" will quickly "burn a day, week, or month" later.
Posted by gwbas1c on Aug 3, 2022, 2:57 PM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
ux (Marketing)
> when it's much easier to just build a nice website using JavaScript I'm currently building a web-based tool that uses dynamic forms fo...
Going forward with the TileMap editor
Just remember that many popular stacks are due to marketing; often the marketing pushes you in ways that are highly profitable for whoeve...
Just remember that many popular stacks are due to marketing; often the marketing pushes you in ways that are highly profitable for whoeve...
Just remember that many popular stacks are due to marketing; often the marketing pushes you in ways that are highly profitable for whoever sells you the stack. Unfortunately, if you follow their instructions to the T, you will spend more money, and may make architectural mistakes that hold you back. (IE, be careful before you drink the kool-aide on "cloud" or whatever comes next.) Also, many blog posts are by people trying to make themselves feel important, pad their resumes, or otherwise self-promote. Tone management in a blog post can make an awful architecture sound wonderful. Other wonderful architectures may be the wrong fit for what you're trying to do. Finally: Avoid many layers of abstraction. It just adds unneeded complexity to your code and makes it too hard to onboard new hires. Carefully review all 3rd party libraries before you commit to using them. Sometimes introducing a 3rd party library to "save an hour today" will quickly "burn a day, week, or month" later.
Comments (0)
No comments yet. Start the discussion.