Yes, you must copy and paste content and not having layout page is annoying at times. But the overhead of just doing it yourself is surprisingly small in terms of the time commitment.

Typically, I'll draft a post in MS Word then open the git repo for my site, hosted on github pages, duplicate and rename the template.html page that includes the CSS, footer, and header for my site and then copy my content into it. When I'm happy with everything, I'll make my commit and then a minute later it's live at my custom domain. Seeing that it takes only 11KBs and 26ms to load my landing page strangely delightful.

To make this simple they introduced async Main[2] a few years ago.

[1]: https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/b...

[2]: https://github.com/dotnet/csharplang/blob/main/proposals/csh...

As proof: https://github.com/AccelerateNetworks/NumberSearch

I've built on many stacks and although I agree that iteration speed is important; It has more to do with how you organize your project and the quality of your tooling than with the specific language/framework.

If you don't like the OOPy style, don't write in it. Pattern matching in C# is quite nice, and you can always mark you functions as static. As a bonus, simple functions are easier to test to.

https://waparcels.tax/

Shapefiles are sort of a rare format. Hoping to ingest all the data into a SQLite/SpatiaLite database to make it a more general purpose data source.

ASP.NET is quite fun, if you can keep your work up to date. Opening up a project that needs bug fixes, but doesn't have access to the latest tooling in VS2019 or language syntax because it still on the old .NET Framework is a bummer.

Any company that was willing to update their .NET apps regularly, and treat development of the app as a service rather than a one time project would make me jump ship.

[1] - https://devblogs.microsoft.com/dotnet/announcing-net-5-0/

Sadly, the vendor provided scanned copies of JIRA user-stories as documentation of their app's API. Despite much struggling, the vendor wouldn't implement even the most basic auto-generated documentation for their API (Swagger). Bugs filed against their product regularly had a 3 month turn around time.

If there were an open source product in this space I could have forked it, made the changes I needed, submitted a pull request and then escalated it with management to get it mainlined by the vendor.

We were their only client for this product and they needed us to implement their system as an example of success so they could make further sales. But their secrecy made good-faith efforts at building integrations with their product extremely difficult. This might have been survivable if the vendor was good at communicating.

Alas this project just got delayed for another year after it was discovered by one of my old coworkers that the new system wasn't calculating property taxes correctly. If we had taken the vendor at their word this would have not been discovered and incorrect taxes may have gone out. Nobody loves taxes, but people rightfully hate it when their local government makes preventable mistakes.

Open source software in this space would reduce the rate of errors made in these scenarios and allow the public to verify the correctness of the system that taxes their property. As a bonus the cost of developing these systems could be spread across multiple local governments who each employ their own developers, rather than each group struggling through this process on their own once a decade.

This will never be VC backable because the market is small and each local government has special needs and unique requirements. The cost per customer is high and there's a hard cap on the TAM.

The big upside of this whole thing is we were able to swap the database from Oracle 11g to MS-SQL with no impact on users. Something that just wasn't possible with the legacy tech.

I borrowed a coworker's iPad at lunch and fixed this bug.

As best as I can tell Safari wasn't respecting the text-align: right; CSS rule. I've switched to a flexbox layout for those elements.

It defaults to the light version and then switches to the dark them on request.

This is so people who don't care or aren't good with computers get the light version and those that can set the system theme have the option of getting the dark version.

https://thomasryan.xyz/

Better yet the content of the post is 20,000 chars on a single line inside of a 558 line HTML doc. :/