496 karma · joined March 10, 2017
Has this changed at all?
Are you relying on a correct and comprehensive project/workspace setup within the IDE?
The distinction is similar to a property developer and a civil engineer. Both create buildings, but one does it at scale by offloading functions to known entities and prepackaged solutions, while the other understands one domain in depth.
Both are needed in any team or organization, because not every solution needs to be "engineered" (a Dockerized Redis instance without SSL or auth behind a corporate firewall may survive untouched for a decade), but sometimes you have to engineer something that withstands gale-force winds at 1000 ft height.
Will see if I can contribute to this project.
Metrocards can lead back to the payment card used for the purchase, and buses (which also record passenger ingress/egress) can remember all swiped Metrocards.
In these cases, you will never recoup your NRE.
Sometimes, you have used your own code way too much to judge effectiveness.
Having a no-agenda meeting with users is also a great idea, but it is important to set scope on feature requests before it snowballs into a request for the moon.
This seems a reasonable balance.
This is such an inspiring and humbling sentiment!
Thank you for all your hard work on this impressive project.
How does one market themselves in this specialization?