the-pigeon
Joined 8 years ago
Joined 8 years ago
Maybe it's a reasonable cover your ass move but comes off very slimy.
Yes, it may be that your solution only worked because you believed it would work. But take the win!
Certainly solutions backed by double blind controlled studied are way better. But those often aren't an option, so use what is.
And increasingly they are losing the quality content that they didn't produce themselves.
On the flip-side. Since I've had 3 or 4 years of experience on my resume, I've gotten interviews for about 1 in 10 applications I sent out. And been made offers for about 1 in 4 companies that I've started an interviewing process with. With me ending the interview process about half of the time with those due to the company being a bad cultural fit for me (excessive overtime, unorganized group, or low pay).
I have also specifically targeted companies that used the tech stack I had a lot of experience with. And I would say that I typically interview well
To be really certain you'd have to test your soil.
I don't think you could test seeds without destroying them. But if your soil was clean then you could grow a plant from potentially contaminated seeds and that plants seeds would be far less contaminated.
Personally I don't care about stocks on a job posting. I consider stocks to be worth 0 when considering offers unless it's a public company with all the information available for me to evaluate the company.
This is because statistically the startup will fail. And there's no way to make a fact based evaluation if it will fail or not until after you are working for them. If you are one of the initial hires it's basically blindly gambling on the founders. The exception being if the founders have previously founded successful startups, in which case you are betting on their experience.
This seems to be aimed at investors more than anyone else.
Gathering more data on a problem you don't know how to solve won't give you a solution to solving it. We don't have any evidence to support that current AI is capable of the advanced problem solving the city driving requires.
I don't think I've ever heard of a politician even talking about that though.
Writing an app that going to do like 3 things? Keep it barebones.
Writing an app that will eventually be 100k lines of code that runs a business. Spend a lot of time organizing and abstracting! Mistakes in your architecture will be expensive to correct but balance avoiding those with premature optimization.
And beyond just the purpose of the app, remember who is going to build and maintain it. A project with 100 engineers and a project with 1 engineer should use very different architectures and project management regardless of the problem they are solving.
In my experience DDG is fine for general information but Google is better for very specific information.
But DDG supports !Bang. So you can do "!g" in your search bar for you specific query and it uses Google. Or "!w" to go directly to wikipedia or "!a" to search Amazon.
There's over 10,000 of them https://duckduckgo.com/bang so it's great for whatever sites you frequently look for information on.
And can even do things like complex math equations with "!wa" (Wolfram Alpha).
Point being, using DuckDuckGo as your default search engine doesn't mean you are limited to its' results. Personally I get the best of a lot of worlds by using it.
It made actual researchers and scientists shut up to not hurt their reputations. And made internet conspiracy conspiracies go crazy in all directions.
I believe the more we censor vaccine information, true or not, the more hardened people will get in their beliefs. What I'd love to see is YouTube change their algorithms to promote quality content over engaging content so good information rises to the top.
Forcing this stuff out into the light helps the system get fixed. This is a pattern I've seen in internal tools development for businesses over and over. When my solution increases visibility into a problem, suddenly people start solving the problem without my help.
Everybody is very slow to update their outage pages because of SLAs. It's in a company's financial interest to deny outages and when they are undeniable to make them appear as short as possible. Status pages updating slowly is definitely by design.
There's no large dev platform I've used that this wasn't true of their status pages.