HN user
I am guilty of that as well.
I somehow value my time more than the money. I think that I have some kind of stake/interest in things I dedicated my time to.
Though I am always thankful (as Eric is in this post) for the people and the income. I can't help but feel regretful as the product of my time and dedication is discarded.
If you would like to put that advice to practice, this book will help.
(The Art of impossible) https://www.amazon.com/Art-Impossible-Peak-Performance-Prime...
It guides you through discovering your mix of passions and strengths to land on what you might make you uniquely extraordinary.
What works for me is "accepting myself".
Accepting myself meant accepting the universe. Even the parts I hated. The suffering. I didn't have to love it all, I just had to accept the balance.
This has helped me be at peace. Once I am at peace, I can be creative.
During a global chip shortage?
They are: https://github.com/tailscale/tailscale
A fair bit of the client code is also on the repo. Things like role based access control that require a backing store on tailscale side aren't open.
Good stuff. Thanks for sharing.
Wow! This product is making my day. Great job.
I am still hacking around on it. I would like to sign-up as a team, though I only have need for 3 seats.
I too "cultivate my own garden".
Like the "Turk" in Vaoltaire's Candide, working on my product (garden) insulates me from the wants and worries projected by todays internet.
Here is my garden: https://www.gorelo.io/
Publish your apps without .net core (--no-self-contained) and install/manage runtimes as you usually would.
If you have thousand apps, you probably also have a CI/CD system and you can gain fine grained control on your runtime management needs with .net build/publish.
MS does quite a few things poorly but they have done a solid job of operating in large enterprises.
You are trying to something slightly complex. I don't see how one could make it any easier from a language design perspective and staying idiomatic to the language.
Go: Goroutines make you wire the "stop" scenario on your own (channel close). Rust: Hold on to your future and drop() it. C#: Pass a cancellation token and call Cancel()
All seem reasonable and stay within what they think their developers will be able to pick up and run with.
Solo Founder.
I have done Meditation, gratitude journals and focused transitions. It all helps.
However, for me the activity that helps the most is hard workouts early in the morning. Once I get going, I am fighting against gravity and fatigue. I am no longer thinking about my past, future or even the day. Just focused on the moment.
I am in a similar boat as you OP. I am very happy on a daily basis, building the product. I am also pretty financially stretched so that adds a level of stress. I hope your product is a giant success.
That sizable minority are the only ones who have anything to lose from the looting and property destruction. Those that are impacted by racism and police violence, people without homes or jobs, likely don't want any Military involvement.
Here is a pretty powerful message: https://www.youtube.com/watch?v=EoDeVpvuEzI
Thanks for all the hints. So it seems it's the device itself and not the update.
I like that the updates are offered. I wonder how usable these older devices are after updates.
I have an iPhone 8 which hasn't been usable since the last update. Most functions work but the performance has taken a nose dive. Some apps crash randomly.
I would not use that device as my daily phone.
This is a good walk through for the Dell XPS 15 9650:
WinUI 3 supports .NET 5 : https://youtu.be/tasbSc3771A?t=186
I get your concern of government bungling the financial aspects. However, are we all OK with 68K people dying every year due to lack of coverage? Do we have evidence that medicare recipients ration insulin?
Why push the website usage as a middleman? Why not just say "If you are able to read this email, you can't ever sue us." /s
Yes, it does read like that.
In the context of a start-up, cost is a big factor and then perhaps (hopefully) handling growth. You could start small and refactor apps/infrastructure as you grow but I am unsure how one could afford to do that efficiently while also managing a growing startup.
On the selling soul to cloud provider, I don't see it like that. I have a start-up to bootstrap and I want to see it grow before making altruistic decisions that would sustain the business model.
Once you are past the initial growth stage, there are many options for serverless, gateway, caches, proxies that can be orchestrated in K8 on commodity VMs in the datacenter. Though this is where you would need some decent financial backing.
(I am not associated with Amazon, Google or Azure. I do run my start-up on Azure.)
We can now achieve pretty high scalability from day 1 with a tiny bit of "engineering cost" up front. Serverless on AWS is pretty cheap and can scale quickly.
App load: |User| <-> |Cloudfront| <-> |S3 hosted React/Vue app|
App operations: |App| <-> |Api Gateway| <-> |Lambda| <-> |Dynamo DB|
Add in Route53 for DNS, ACM to manage certs, Secrets Manager to store secrets, SES for Email and Cognito for users.
All this will not cost a whole lot until you grow. At that point, you can make additional engineering decisions to manage costs.
I am hoping to get some guidance on this side project. I have made a ton of mistakes along the way so I am hoping I can reduce them as I go forward.
The product is an IT ticketing system that has an integrated Asset Management and a Remote Management system (RMM). It has a mobile app, customizable dashboard, reporting and a decent search experience.
The webapp is written in vuejs. The mobile app is Xamarin. The backend is .net core. All deployed on Azure.
If you guys have any suggestions on the product overall (technical or otherwise), it would be very welcome.
Majority of our issues with Azure revolve around some of their services, which are still slow to evolve, due to their pre-cloud underpinnings.
An example of such service is their Azure AD B2C service, which is their competitor to AWS cognito. We have been using it and as a baseline login service, and it works fine. However, the service doesn't see much upgrades. Their "user flow" templates, which control the logon process, have been in preview for years.
Yes, Identity Server 4 exists but it would be nice to have decent competitors to Spot Fleets, ECS, Cognito, etc.
"I am calling from Microsoft" calls were bad enough. Now they will know some details to a past case and sound slightly more legit.
I will try to attempt to address some of your concerns...
"First they focused on making .NET Core all about ASP.NET with a clear focus on MVC and making everything super granular. Then they didn't like how granular it was and started to put lots of featurs into smaller pacakges again."
.Net core was a ground-up re-write and was the vehicle used to opensource all .Net. It was always meant to grow into a full-scale offering and eventually bring along all the features users demanded. I personally love reading all the fun library code: https://github.com/dotnet/runtime/tree/master/src/libraries
" First introduce Newtonsoft Json into the default .NET Core stack. Then rewrite everything."
Newtonsoft itself is bloated and there is no turning back for that library. MS is providing an option to use a lightweight JSON library that uses the new SPAN ref struct.
"The ASP.NET Core team now is realising that people hate MVC and they are splitting out more features from MVC into more basic ASP.NET Core features, which is why routing has completely changed again with endpoint routing."
Endpoint mapping wasn't born out of hate for MVC, it facilitates the separation of framework/transport/protocol without introducing config files (or handler code) for each. https://github.com/aspnet/AspNetCore/issues/4772
"The reason for all of this is old MSFT thinking. It's not bloody rocket science, people have been saying it for years that they don't want to be forced into MVC, they want things to be more lightweight, bla bla bla."
Maybe I am old but I remember when MS was almost forced to adopt MVC. They kept webforms alive for a long time. They introduced razor pages when SPA world demanded an easier solution. I am not sure if there was going to be a way to satisfy everyone here.
Piggy backing on this a bit..
You can now publish a .net core 3.0 app that is: 1- Ready to Run: Part AOT compiled app for the platform. 2- Trimmed: Tree shaken down to only necessary bits from the framework. 3- Single File: Self contained app.
This combination of features provides a really decent balance between size, performance and distribution.
Even though these are compile/build time requirements, their size ends up slowing down CI/CD process.
Our ondemand cloud build servers download the code, restore nuget packages and download node modules. Most of the build time is spent downloading. Compiling generally takes an order of magnitude less time compared to those 2 steps.
This especially effects scenarios where end-to-end testing can only be done in a staging environment due to complexity of the product.
The Hanging Chad 2.0
Right on queue, Azure is currently having some pretty massive issues. All our deployments are having issues.
I am curious to see your findings (if possible). We are betting big on Azure and have found it to be pretty compatible with our needs. However we may have some blind spots.
"It's always day 1" philosophy is very different at Facebook.