I remember Google being more popular with tech savvy users than Yahoo or Alta-Vista. IMO this is the writing on the wall.
HN user
robert-wallis
[ my public key: https://keybase.io/robertwallis; my proof: https://keybase.io/robertwallis/sigs/SEAZmzEwIyh_-7KzLeJQBnBCBNV_ZVVkct1wgZK5ho4 ]
How about COO - Close Object Obligation? And you could sound like a pigeon saying "coo" during talks explaining it.
I'd really like to see an LLM use Wolfram Alpha APIs like the new Toolformer paper does https://paperswithcode.com/paper/toolformer-language-models-...
I recently learned:
It has been claimed that Euler's identity appears in his monumental work of mathematical analysis published in 1748, Introductio in analysin infinitorum. However, it is questionable whether this particular concept can be attributed to Euler himself, as he may never have expressed it. https://en.m.wikipedia.org/wiki/Euler's_identity
But it is still cool.
Intel and AMD should provide GCC maintainers hardware. It could easily come out of the marketing budget, because benchmarks compiled using gcc would be affected, and they use benchmark numbers in advertising.
One of Elm’s main focuses is code that is not possible to crash. Once I groked that, native modules going away in favor of ports made much more sense.
What if the miners deny check-in transactions to force the killcord to execute?
We have had our entire kube go down because the image size was huge and the master node only had 20gb disk and docker wasn’t cleaning up old named images. Smaller just extends the problem to the future, but it gives us time to re-build our cluster with a new kube version.
It seems like using Google Sheets or the online Excel is the answer. Single source of truth, collaboration, and keep the same fundemental tools.
Here's a list of Java CVEs: https://www.cvedetails.com/vulnerability-list/vendor_id-93/p...
To be clear, I am not a security researcher, and I haven't verified the severity of these issues. But in 2016 alone there are 16 CVEs which is 4 per month.
This sounds like a witch hunt. Java has horrible security bugs even today.
Bugs can be found in code written in all languages.
The manga guide to Calculus is a great book. It helps me reason on a topic that is hard for me to grasp. Someone must think SQL is a difficult topic too.
TACOP is extremely dense and put me to sleep every time I tried to read it. I recently donated my copy of 0-4 to my work library, where nobody was interested in reading it.
The fact that we both have opposite views of your example books shows that this is a difficult process for librarians.
I was thinking about how fast it would be to find matches, so I wrote a little C program that runs in about 1/7th a second: https://gist.github.com/robert-wallis/b7faf94976b153923fde
It generates a random number, then tries 8^8 times to generate a new random number and find a match.
The hostname also needs to be verified somewhere in there.
In the case of terminal illness. Absolutely. In fact, they should be sending the charts to a specialist teaching a week long personalized class to help them understand the data.
Maybe there should be a secondary option to allow a site to use the mic in the background.
One of the great things about open-source, is when you discover a weakness in some tool you like, you can modify that tool and submit a patch. Or you can learn from the source of one tool and add another tool to the marketplace. When the marketplace is saturated, patching or modifying the popular tools is preferable to me.
Also, I would prefer developers spend more time making general applications and less time making tools for other developers. I'm not saying people shouldn't make great dev tools, I'm saying more people should make great applications, and less people should make great dev tools.
I'm suppose I'm in the minority of developers that _don't_ think we need to learn more build tools.
make, configure, automake, autoconf, MSBuild, Apache Ant, rake, gradle, jake, grunt, gulp, fez
Sorry, I'm sure your system is nice and organized. But now you've introduced one more build dependency that will make projects based on Fez just a little more difficult to on-board.
It's great how they presented their company, especially with the silly disk warnings, the FAQ, the list of employees, and the list of locations. Their poking fun at the standard model of business branding makes them stand out.
Apple has a patent on the Dock. https://www.google.com/patents/US7434177
And clickable pull-down menus in the menu bar. https://www.google.com/patents/USD629412
The legal system strikes again.
So glad you posted this, I was doing something similar and gave up on the idea because I noticed Amazon doesn't even want you keeping their ASINs in a database. But I kept thinking maybe I'm just being paranoid and they wouldn't care.
Glad you made some money off the dev time you put in!
Nice work getting things done!
I see your Minecraft and Mario games are "unavailable". I'm sure you'll keep creating your own IP in the future, like you did with the other 22 games instead of dealing with copyright and trademark infringement. Especially if you want to generate some revenue.
I am not a lawyer. But it will be much better for you to keep doing your own thing (like you did with most of your games), than to be taken down by lawyers working for people who's characters, names, or art you "re-purposed".
Unix communicates via text, stdin stdout stderr. That's pretty much a standard.
Windows PowerShell communicates with typed objects. COM components and .NET components are a Windows standard way of communicating between software parts. COM has been around for a long time.
Between computers, TCP/IP is a standard way of communicating. But without good documentation of the protocol adding an HTTP layer on top makes it easier to understand. But without good documentation of the protocol RESTful APIs makes it easier to understand. But without good documentation of the protocol WADL...
However I do agree about HTTP. Because I imagine there are more devs that understand HTTP than higher or lower protocols.
I guess it's the threshold of when complaining is justified.
The things I complain about aren't CamelCase. It's more on the scale of, using MongoDB as the main store for transactional financial information. (Not a real example.)
And in that case, I feel justified at not only letting people know I think its a bad idea, but also telling his manager I don't think he should be the lead.
I do what I'm told, and I get it done on time. But I also explain why I think it's the wrong decision, and I usually provide links to articles backing me up. I even try to include links to counter-examples. I have little patience for people that don't listening to experts. If you don't listen to me, then listen to these other engineers that are better than me. If you don't listen to them, then it's going to be really hard for me to respect your decisions.
I'd rather have a manager with just 10 years experience, than be a manager myself. I like working on products more than management.
I was feeling pretty good that I wasn't a stereotype, until I got to the Agitator.
I'm just really tired of people putting junior devs as team lead over me. I'd really like a lead that has tried different tech stacks, project management methods, and programming language paradigms. It's hard to respect someone making a novice decision based on their limited experience.
I don't think I am curable. I don't see how telling my manager and team lead why they are wrong, is something I should change.
Don't worry, it's just linkbait. The article is two full pages of wild guesses on what they think is blocking it.
Exactly. The author exaggerates the amount of time in flow. I wish I could be in flow longer than a day. Design discussions, feedback, and engagements can happen every day and you can block out some time to hopefully get in flow every day.
The big misconception the author has is that flow means blocking out weeks of time.
Maybe change your perspective. Google is trying to integrate everything into one Google account.
Imagine if Github created the Wiki product with a separate login, and then wanted to integrated Wikis into the rest of Github, but then lots of Wiki haters got mad because they wanted the old Github and didn't want to sign-up for all that Wiki stuff.
The point is, if you sign up for Google, you get Drive, Docs, Spreadsheets, YouTube, and G+. They are different services that are all part of having a Google account.
The real thing you should be complaining about is that G+ notifications are annoying, and you just want to turn it off because you don't use G+.
That would be like if every time you logged into Amazon.com to watch an instant movie you got notifications from S3 saying your bill for the month is $0.00, or your workmate you gave access to your EC2 account just bought a new TV.
It's the notifications that are problem, not the integration.
Certainly the string library, of all places, should be using secure code.
I'm sure there are sooo many people running Linux on pre-OSX Mac harddrives formatted with HFS that could be hacked with a buffer overflow.
Are you seriously arguing that buffer overflows in the kernel are not a big deal?