HN user
Agreed. I think with the pace of change happening more frequently it might require more disciplined focus on training, constraining systems, and number of products.
Seems like a narrow view of developer tools. Isn't this the bread and butter of GitLab/Microsoft and others? I work in a dull industry and the perception isn't we need new tools to understand our abstractions. The main challenges I run into are that we need more staff to run and maintain new ways to work with our APIs. How do we keep track and find our APIs? Who owns the database? Am I allowed to connect to this database? My main job is to figure out how to make an on-rails experience so that when a developer leaves after two years new ones aren't relearning the flavor of the month pattern or tech someone wanted to try. It's a broad enough problem I'm sure it can be productized if you keep it general enough.
It is a microservice chassis https://microservices.io/patterns/microservice-chassis.html At scale you have lots of teams writing their own boiler plate and getting it right or wrong. This solves that at the application level. Steel toe is another option by pivotal. You can see an example of how cross cutting concerns can be solved in this mindmap https://www.alanmbarr.com/blog/images/cross_cutting_concerns...
There's some level of friction in working with databases. Not insurmountable but painful.
I loved the ML based emphasis. I'm a big fan of f# unfortunately as the article details .net has a shadow of the libraries that Java has. Clojure and Scala have much broader access to popular libraries. I've found most developers are ok with the hum drum c based languages thus c#, java, golang are good enough for most people with no interest to jump the chasm to an ML inspired language.
Any plans on open sourcing this or making the code available?
Do you support on-premises kubernetes?
yes good product management is key even though your customers may not have a choice
There's a good blog on scaling a platform team and how to keep up with growth. https://medium.com/adobetech/why-do-organizations-need-a-pla...
Great book highly recommended
Nice job! I had a good experience as part of the applied machine learning data science coursera specialization. The cloudant support was great to have.
It's a great testing resource. Way more concrete than 'well just test all the different strings'
Never Split the Difference is really good highly recommended and based in science.
More information can be found here http://fsharp.org/mentorship/index.html
You can run c# directly by using add-type in powershell
F# has hit a huge sweet spot for me in productivity, strong typing, inferred typing, multi-paradigm and syntactic sugar. The tooling just gets better and better. I struggle to think of a language that's so well rounded.
I love all of Edmond Lau's stuff. I accidentally found one of his Google talks while trying to find something for my team when we started on fixing a massively underscaled tech stack. I bought the book read it and shared it with a few other engineers. Super valuable and a lesson I keep trying to teach to our organization is how worth it is to build better tooling.
I hope you all can style the notebook to look as good as the way kaggle does their version. I understand if you leave it alone too.
Why not novice instead of your girlfriend? You don't even mention her in the articles so why cling to a distracting title?