@adam_rocska@Kiptanui_boazo Yes, the key driving factor should always be:
🎯 The decision makers’ goals
📦 The funders’ material opportunities.
All too often we see instead the products that pay for salaries into a playground of cool tech.
@adam_rocska@Kiptanui_boazo Yes, the key driving factor should always be:
🎯 The decision makers’ goals
📦 The funders’ material opportunities.
All too often we see instead the products that pay for salaries into a playground of cool tech.
@adam_rocska@Kiptanui_boazo Yes, the key driving factor should always be:
🎯 The decision makers’ goals
📦 The funders’ material opportunities.
All too often we see instead the products that pay for salaries into a playground of cool tech.
Hey, I think we can somewhat be open with our weapons of choice. These aren’t silver bullets just usually for the typical software product development & consulting cases:
For Apple stack it’s usually native Swift and SwiftUI
For Android stack it’s usually Kotlin and JetPack Compose
For Websites, WebApps, etc. it‘s usually NextJS with Vercel and things.
For Microservices and other non-web-ui interfaced programs it’s Server-Side Swift.
Of-course we have a whole bunch of other stuff, just in the middle of re-engaging with a Java Spring Boot stuff, with embedded clients & some web interfaces.
But sure, for the cases when it makes sense, the listed stack is ok.
Usually that’s for the cases when the budget is heavily constrained and human quality perception is compromized. As in the golden triangle: optimize-compromize-restrain, so not as a derogative term here.
@Kiptanui_boazo Picking the right tools for the right job is not an easy task for example.
The bad rep for most of these stacks is due to janky decisions and executions.
@PING_21Gram Indeed, @adam_rocska’s decision to break the ‘the boxes won’t touch’ rule proved strategic. In entrepreneurship, rules matter, yet discernment on when to bypass them defines astute business leadership.
It's nasty stuff. But it can be covered with union types and a codec library that has support for union types.
We have a codec solution within @21GramConsult which supports craziness ¯\_(ツ)_/¯ you never know what beast you gotta integrate with.
Its open-source edition is still a bit skinny, but in the coming weeks it'll get beefed up with the internal smart we have.
– It's hard to untangle the legal aspects of source code ownership sometimes, but it's getting there.
@adam_rocska@BelloneDavide Yes. It's hard to imagine for freelancers how painstaking can compliance be.
But! It's worth the effort.
In the current state of typescript world the time is just right to put these jewels on the table.