Ask HN: What are some positive things happening around the world?
There is too much bad news to listen to right now. What is some good news I can share with my team going on around the world?
My team has been using swashbuckle in the dotnet API ecosystem which generates an open-api document based on your code, commemts and c# attributes (for the things it can't infer from the former). The documentation and code have a symbiotic relationship.
We have a high level wiki page about each application/micro service we support. Things like - resource locations - job schedules, purposes, inputs/outputs -FAQ's - known dependencies on other micro services, etc
We also have wiki pages for - onboarding - team norms and expectations (pr process, on-call duties, coding conventions, etc)
Inside each application's or micro service's repo the readme should have steps to - get the project running locally. - document feature flags - document conventions unique to that project - document how to trigger a release
Someone here said the code should be the source of truth and other documentation isn't needed. To me it's unclear what they mean by that exactly; I could get behind that if they are documenting via comments on functions/classes/etc. my org tends to not write much comments in the code so it's really hard to tell if the code does what it was intended to do or if there is a bug. What I love to see for "self documenting" code is tests. You write tests to either test for outcomes you expect or test outcomes that you don't expect, don't happen.
Most of the time I've seen that function used it was due to improperly written asynchronous code.
I went into [some detail](https://news.ycombinator.com/item?id=37798121) on another comment on this thread.
You can learn that on blazor and apply it elsewhere.
That being said I have worked with blazor since launch in 2019 and it's one of my least favorite SPA frameworks.
The developer experience with blazor is lacking. Debugging tools aren't up to par with other dotnet SDKs. Hot reload only works when not debugging and only if you don't modify member signatures and a plethora of other conditions. Because of the afore mentioned the feedback loop during development can be slow. The razor editor doesn't support all the helpful actions you're used to with dotnet (e.g. cleaning up unused imports). Sometimes the razor editor gives really bizarre errors and you simply need to close Visual Studio and reopen for the. tk disappear
I dont mind the framework itself but there's a few design decisions that could have been better.
I think there are some good use cases for it though. AOT compilation to wasm is kinda neat for workloads that may benefit from that.
I also think that blazor server might just be the most novice friendly way to get I to web development because it abstracts away much of the web. that being said, the blazor server architecture has a plethora of drawbacks.
it only has something like 30,000 miles on it and is still all original on both the Interior and exterior.
So cool to see as a GTI owner.
Gartner tells you what you probably already knew them sells your information.
Enter stage left my first job as a developer in 2016 and I'm tasked with learning cobol to support customizations to their 25 year old Lawson Implementation.
I'll probably never use it again but reading and writing cobol code opened my eyes to different design patterns not often seen in more modern languages. Seeing clever implementations of features that come out of the box in modern languages was really neat.
Obscurity instead of Security is bad too.
My biggest complaint is how unresponsive they are to fixing bugs. After reported it may be months or a year before you see it fixed.
What I dont know is if that is common in that "ui component" sector?
There is too much bad news to listen to right now. What is some good news I can share with my team going on around the world?
If we apply this article's suggestions to your situation: 2,500 (2 adults, 1 child) * 12 months is 30,000 /year.
Like you said, too many people live paycheck to paycheck and our minimum wage keeps it that way. You can barely survive on it.
obviously not. But anecdotally what I see where I live is that it is a large enough inconvenience that it makes an impact. If you work 8 hours, then have to spend 2-3 hours getting groceries you already have a 10-11 hour day not counting any other commuting you need to do. What if you have kids you need to get off a bus from school?
trying to blanket say anyone not willing to make that trip just isn't trying isn't fair.
It is well documented that low-income areas have less access to good education, healthcare, and other facilities. blaming the residents doesn't help them improve their quality of life. Not everyone will make it out of that.
Edit: essentially, a lot of the time it is expensive to be poor.
I do get results for: firefox, opera, microsoft.
coincidence?
Right now we pay more for healthcare than other countries because our system is so flawed. we pay more for both services and the same exact prescriptions that other countries do. I work for a healthcare system and the amount of charity care and unpaid medicare bills are astronomical. If your'e interested I can share a publicly published report that breaks this down. These are also part of the reason that we pay so much more, the people that actually pay need to make up the cost for those that don't.
on top of that, medical claims processing and billing is overly complicated, time consuming, and expensive due to multiple insurers.
My premiums to have my family covered are almost as much as my rent. ( disclaimer: i live in a state with a very affordable housing market)