1,717 karma · joined July 9, 2014
* Base laser "pushers" on moon, Lagrange points, etc.
* Use moon/earth pushers to push 1st wave lightsail craft(s) towards destination. 1st wave craft are also themselves equipped with laser pushers aimed back towards earth.
* Use moon/earth pushers to push 2nd wave lightsail craft towards destination
* 1/2 way to arrival, 1st wave starts pushing _back_ 2nd wave and moon/earth pushers stop pushing.
* 2nd wave "stops" at destination or slows enough to be captured in destination orbit.
I understand I'm being naive here and ignoring "little" things like funding, profit motives, and basic human nature. But more what I'm suggesting is that there has to be a way to speed up scientific research and application while toning down the hyperbole. This really became apparent to me during Covid. There _have_ to be ways to rethink from first principles how we do and report on science.
As a dev I like to say my job is to translate English into nerd. Non- or semi- technical people should communicate the business problem and then together we’ll work towards the best solution. Sometimes the solution is code.
* Watch the test fail first. Write a test FooMethod_Should_Do_X. Confirm it fails. If it passes, it means you're testing the wrong thing. Once it fails, make it pass. Once it passes, make it pretty while still passing
* The simplest thing you can do is nothing. As a developer, your first job is to talk customers down from that feature request without annoying them too badly. "What bad things happen if the app doesn't do X?", "Explain the business value of X to me. About how much time or money will this save?".
* This applies not just in code. In personal interactions, saying nothing or doing nothing is often better than prematurely doing the wrong thing. There is a time to say and do something, but it is usually later than we think and not on social media.
But I do struggle with how far to take that. I worry I’m getting too deep and need to focus on features.
I’m only partly being snarky here. I think constantly about how I should improve past code, why I shouldn’t have done x, etc. Self criticism is healthy and takes some of the sting from external criticism.
Beyond that, I think “lean into the punch” is an affective strategy. If someone says my code is crap I can either 1) fight them and try to explain, justify etc or 2) say “you’re absolutely right”. 2 takes less energy and deflates most reasonable people’s criticism, esp in person. Of course if the criticism is wrong then that’s harder and maybe not even appropriate. But even then, framing it as “a valid criticism, but Im balancing that against X” helps the person feel heard and likewise more likely to hear your reasoning.
There is a subtle difference here. Microsoft isn’t just producing code based on GitHub data. They are producing a tool that lets others generate code based on GitHub data. I do think consideration of the source data creators intent is important- and there is a case CoPilot hasn’t done that. But if Shutterstock wants to use any images _that they have been given license for and treat creators fairly for_ to build a tool that lets others generate images, they should be allowed.
Also, the op argues only MS has access to train based on all of GitHub. Others might run into rate limiting etc. However we know Amazon and others do have similar models. This would indicate MS may have a competitive edge but not a full market lockout.
I genuinely think there is a huge underserved market for a "world's most boring news and weather site". Almost everybody I talk to on all sides of the aisle recognizes that clickbait news is one root cause of lots of problems and want an alternative. In fact, in some ways, Hacker News is that site for me.
That said, I don't get why an app not a mobile-responsive website.
A guy can dream at least.
[DataTestMethod] [DynamicData(nameof(GetAllHttpTests), DynamicDataSourceType.Method, DynamicDataDisplayName = nameof(GetTestDisplayName))] public async Task RunHttpTests(string endpoint, string method, string data){...}
To be clear, this is integration testing, not unit. Testing that certain HTTP requests work, not necessarily that they are correct.
They make it somewhat easy to do using Yet Another Reverse Proxy (YARP). I’m in the middle of it for a .NET 4 to 6 migration. The challenge for me is that it introduces complexity. Developers have to think “do I fix this bug in v1 code or v2?” We have to host two backends instead of one. They both touch the same db, so that adds complexity- what if v2 does something in data that breaks v1? All solvable problems but just thought I’d share a from the trenches take. I do still think it is the right approach for this scenario.
Similar for ddos protection- you almost have to use somebody.