Germany will shut down its three remaining nuclear reactors by April 16, ending nuclear power generation in Europe's largest economy. Germany's move, which marks the end of a decades-long fight by environmentalists, makes it an outlier in much of the industrialised world, including Britain, France, Finland, and Poland, which are expanding their nuclear energy programs as part of their plans to reach ambitious climate targets. The decision comes at a time when Europe is grappling with the question of how to secure enough energy to drive its economies and keep homes warm while also reducing greenhouse gas emissions. Some scientists and Nobel Prize laureates from across the globe have urged Germany to reconsider its decision to phase out nuclear power, citing it as a valuable alternative to power plants spewing greenhouse gases. However, Robert Habeck, the economy minister, insists that Germany can manage the nuclear exit, stating that the country's energy system will be structured differently, relying on 80% renewable energies by 2030.
There is nothing wrong about any approach: like everything in life, it's a balancing act.
If you want something maintainable in the long run (5-10 years), it's probably not the best idea to start with that approach. But then again, you probably have no idea what direction you should be heading for the next 5-10 years, so it's not a big deal.
I know it's a bit conflicting advice, but that's the point. When you know exactly what you are building (which is seldom the case with web apps), you want to do it right from the get go. When you don't really know, it does not matter since a few years down the line, if successful as a product, you'll be refactoring heavily and probably doing it the right way at that point (iow, full tests come last).
I naturally think about (Or pencil.) what elements should be in a page, and how they should behave. That is easier to translate to browser tests.
Also, even if I write feature or unit tests to invoke some class methods, there's no guarantee that they'd be executed when a user performs some action in the page. To do that, I'd either have to manually check it (Bad, because its not repeatable.), or write browser tests anyway.
If the framework is correct in design and implementation then you can change something superficial and the odds are good that the change is superficial and it works.
If you are starting from the outside and working in it might seem easy to get started but you will fall behind in productivity compared to people who do the opposite.
I have frequently worked with testers and frequently those testers have chosen to automate their work and I am all for that; a dev doing the same might catch some errors that way but they may also encode conceptual mistakes.
4. Ignored Reports: Regular Reminders. Prioritizing content that multiple people reported.
5. Acceptable Content: The community owners decide standards. Not this system. The owners can merely use this as a tool for reports to come in.
---
Negative Points System: Everyone starts with a X number of points. Each report decreases X. If a report is constructive, they get back decreased points, plus earn some. If the report is well intended, but doesn't justify a report, they get back points, but earns none. If the report is malicious, they lose their points, and some more. The pluses and minuses can indicate a user's behavior, and the owners can remove that user's right to report.
[Show HN] A Service that Deploys Your Applications to The Cloud and Maintains It: A2Way
Hello HN!
Me and my wife thought long and hard about starting our own business, however small it may be, and we found something to offer.
We both develop web applications in a company. I am self-taught and have 9+ years of experience in the field, while she has a degree in Computing and Information Technology with 2 published research papers* and experience of 2+ years in the field.
We found a way to turn our free hours into money, by deploying and maintaining your or your client's web applications.
Obviously there are more advanced services that you can choose, and get automated deployments and more. However, that is not the market we are targetting. We are targetting the group of people who knows they need to have something (Appliation, website, anything.) online, but they do not have time or knowledge to do that. I hope there is room for small fish in the sea.
We have set-up a landing page for it, and added a contact form, for interested parties to contact us.
We'd be delighted to hear your thoughts on this, and will be so much thankful for any leads.
Germany will shut down its three remaining nuclear reactors by April 16, ending nuclear power generation in Europe's largest economy. Germany's move, which marks the end of a decades-long fight by environmentalists, makes it an outlier in much of the industrialised world, including Britain, France, Finland, and Poland, which are expanding their nuclear energy programs as part of their plans to reach ambitious climate targets. The decision comes at a time when Europe is grappling with the question of how to secure enough energy to drive its economies and keep homes warm while also reducing greenhouse gas emissions. Some scientists and Nobel Prize laureates from across the globe have urged Germany to reconsider its decision to phase out nuclear power, citing it as a valuable alternative to power plants spewing greenhouse gases. However, Robert Habeck, the economy minister, insists that Germany can manage the nuclear exit, stating that the country's energy system will be structured differently, relying on 80% renewable energies by 2030.