HN user
[ my public key: https://keybase.io/jesseobrien; my proof: https://keybase.io/jesseobrien/sigs/ymKwbHY0snML3KcryJ5J4UNhFlWdOEDCRoWRS-7T0Hc ]
Hey everyone, I've been doing AI related development, training and building at a mid-to-large enterprise company for the last year. I wrote this article to offer my perspective on the ever changing landscape in AI currently. I'm interested in having more discussions about where we're headed as an industry and how this is impacting everyone.
No, we wouldn't magically have developed modern computer-controlled battery packs of lithium ion batteries in 1920 if we just wanted it hard enough.
That's not what the commenter said. Don't put your interpretation of the words into theirs.
It is very feasible that the investment of 100-some-odd years of battery research and a marked non-future invested as deeply into oil and gas as we have now would have rendered our entire world vastly different. This is not a claim that the future would have happened sooner, but rather the events that unfolded and the research would have been different.
You can't be a one man band, but if the organisation supports it, you can achieve both. In my experience, it doesn't need to be a trade off. We can get close to the users and program to your hearts content. We need the right company and environment to want to invest in that for us. There's a great loop we can get into by doing things like offering demos of new features to clients weekly or bi-weekly. What I've seen happen is that we don't need to code as much because we know the specific problems that need to be solved, rather than loads of guesswork and trying to write blanket solutions for misunderstood problems.
Can you explain any of the technical details around this perchance? I'm super curious. I know that SO_REUSEPORT[1] exists but is that the only little trick to make this work? From what I've read with SO_REUSEPORT it can open up that port to hijacking by rogue processes, so is that fine to rely on?
This article doesn't add up the points to anything that solves for the given problem. Owning identity isn't solved by saying "don't trust ${third party}! Come trust ${my preferred third party}, it's better!" Any blockchain is still a third party that all parties involved with need to place trust in. It isn't somehow more or less trustworthy just because it exists.
Many people, including myself, believe that the individual should be able to own their own identity.
Yes, this is nice wishful thinking, but on a global scale it's not really possible or feasible.
OAuth2 should be used for what it was intended to, which is for a web service to provide another web service with a user’s data given that user’s consent. It should not be used as a global digital identifier because that’s too important to be owned by anyone but the individual themselves.
So, instead of OAuth being in the hands of FAANG[1] it's in the hands of ${blockchain-of-the-year}? How does moving the trust from a centralized company to a centralized blockchain change MY ownership? If I move everything away from FAANG to someone's blockchain, I have no assurance that chain will continue existing. If there's a flaw found in it and everyone moves to another chain, now what? Sure, we can make the same claim about FAANG not continuing to exist, but the point is there's no inherent advantage here, they're equal. FAANG are supported by millions of individuals and companies that are all, together invested in their success. There's no unilateral agreement on blockchains and I doubt there ever will be.
With social recovery, instead of having to trust Google, you can choose who you trust, and instead trust a given set of friends, family, and services.
Again with the trust this and not that. All of my friends, family and other services need to then agree that they're all going to trust ${chain} instead of FAANG. It doesn't fix the problem. "the blockchain" isn't just one thing. Who's chain do we all shift trust to and from and based on what security? At least with Google I can rely on their security because if they end up with a breach of trust it's going to have a massive, real impact on share prices and consumer trust around the globe. That's incentive enough for me to rely on it day-to-day.
This article has some interesting tidbits but overall seems like just a baseless rally against FAANG by someone who knows very little about complex authentication or trust and security in the real world.
I don't mind the article, but one of the main points links a study from 2017 on school safety. Schools have become less safe since 2017. Since 2017, school shootings in the USA have skyrocketed [1].
[1] https://www.statista.com/statistics/971473/number-k-12-schoo...
Would be looking for this as well. I love using NATS, would like to see a comparison of both.
I don't think it's a problem. It's another symptom of the min/maxing culture this article is taking aim at. There's a culture shift that's taken place in the last few years which says no one's allowed to complain unless they have a better solution. Seen it rearing it's head more recently in very rigid ways. From my observations, it kills creativity in it's tracks and instead of making everyone carefully consider what they complain about and solve problems better, it quashes anyone's ambition to say anything for fear of becoming a target. I've seen the targeting happen in such childish ways too. "If YOU think it's so shit, then YOU fix it."
Sounds like you need to use the reflog more often. git reflog keeps track of all changed references (branch tips, etc) being changed in your repository. You can effectively check back out into any state you want, whenever you want.
I've always looked at it this way as well. Echoing some other commenters here, I don't understand why he's polarizing. I haven't heard he himself present a lot of polarizing views on things. His guests on the other hand, some are absolutely off the charts in terms of how polar their views are.
The reason his podcast is popular is because his guests are almost always interesting and contrary to a LOT of media in our era, he lets them speak. I think the viewpoint that somehow there's a cult of Joe Rogan followers who listen in only to hear Joe's POV on things is really tonedeaf.
I don't disagree that they're a major contributor to Linux itself, however RHEL usage is plummeting over the last 5 years as stated in the article. Being a contributor and owning RHEL is really no advantage at this point.
I didn't go out of my way, I clicked his profile here, which has a link to his website, which has all of his social media on it.
I made an honest attempt to understand someone before engaging with them, next time I'll just spew some uninformed BS if that's better?
Agreed. I think the worst part is that I'm a long ways from SF, but it leaks all over the tech communities everywhere. I know enough people who've lived there, pass through, visit friends, etc and even I understand from the other side of the country having never been.
"I really want Redis to be a set of orthogonal data structures that the user can put together, and not a set of tools that are ready to use."
This is why I fell in love with Redis right from the beginning. Having a data store that gets out of the way and just gives you the structures (a lot like programming data structures) to do what you need feels awesome. Picking up the commands and putting them to use feels as natural as reaching for any vector/list/whatever structures I use anyway in my programs.
Thanks so much for everything you're doing antirez.
I have the same issues. Combined with that I'm hypothyroid, which can then compound the PVC symptoms when my dosage of thyroxine is off.
I'm sitting here reading this article thinking "My gods, I wouldn't wish this on anyone, forget about your heartbeat before it drags you into panic attacks!"
Indeed! At minimum we would need the Mars Dragon or Orion with a long range trunk attached to carry supplies and repair pieces. It would be really interesting to see an orbital pairing (a-la the Lunar Module/Command Module) for an L2 repair mission.
I'm unsure why this is being downvoted. I think it's a completely fair assessment given what happened with Hubble. At that time we had the Shuttle to head up and actually fix things that were broken. I have doubts that SLS is going to be as quick as they want it to be, and crewed Dragon isn't operational yet either. By the time this thing launches we might see trials of both, but certainly there won't be something readily available for service operations on the JWT at the time it launches.
There's an interesting video I've seen before showing it being recreated in a lab. I do not, however, know the origin or reasoning behind why it happens.
we are still a long way from reaching the depths that Apple can go to before Apple fans will seriously consider an alternative.
You're literally proving the point here. There's much, much more transparency on the Android side of things. Custom ROMs and the stock Google Android images have been combed over for almost the last decade by loads of different individuals and groups around the world. Now, we surely don't control the Samsung-esque bloatware that they slap on top of stock Android, but there's absolutely no way there's throttling code that lives in Android that we don't know about yet.
Anecdotal evidence of my own: I have a Nexus 5 that's nearly 5 years old now that my kids use daily. It's using a stock Lineage ROM. The battery certainly isn't the best anymore, but the phone doesn't feel different than the day I bought it, and it doesn't crash.
Came here to make a plug for `rg` as well. I've put it through it's paces the last few months and it's awesome.
Surprised no one here has mentioned Twist. https://twistapp.com/ We're currently evaluating it in lieu of Slack on our team of ~10 people because of the vast array of issues Slack has. I don't know if it's something that could be considered for larger organizations, but the way it puts together channels and threads is very intuitive, and cuts out a lot of noise for individuals.
In terms of Slack's misgivings, I don't think I've used a more incredibly bloated, buggy, slow electron app. Multiple team logins with no centralized account is _insane_ to mange across teams, this single point frustrates me and most people I talk to a lot. Not to mention the more teams you have, the more your electron app slows to an absolute crawl. The notifications leave a lot to be desired in terms of granularity per channel. They've done a really terrible job on "threads", the UI around it is messy and confusing, and the concept doesn't inline well. Those are just the most apparent daily gripes.
Another good one is Safe is Not an Option by Rand E Simberg, with a forward by Ed Lu. It gets into the nitty gritty of why exploring space is dangerous and why we as humans should care little about that, and more about exploring it. No different than the explorers who sailed across the seas. Some humans died, knowing that they signed up for that before embarking. Exploring space should be seen no differently, however NASA and the government are only concerned with safety. Getting the opinion of ex astronauts on these issues is great perspective.
If you're curious on more than a surface level, this book is an excellent resource from an ex-astronaught on why things are lagging. "Safe Is Not An Option"
https://www.amazon.com/Safe-Not-Option-Rand-Simberg/dp/09891...
The issue with the last few was that the barge was over the horizon from the high bandwidth stations receiving the data from it. The vibration is certainly a factor, but it causes more of what you saw on this launch, artifacting, rather than a full disconnection of the feed.
I read a great article a few months ago talking about how success as a developer could be looked at from a more wholistic POV which I agree with quite a lot these days.
It breaks down the "title" mentality into smaller responsibilities across three areas: Technical Skills, Leadership and Community Involvement. You can fairly easily isolate what your company values from employees in these three groups and measure any individuals performance inside each group to weigh them accordingly. I think it would work very well with peer-review processes as well.
http://frontside.io/blog/2016/07/07/the-conjoined-triangles-...
This is clickbait. The entire article talks about how fast the SSD is and nothing else.
Even better would be to get something that can run in a docker container that you can just download and press go!
React actually does a fabulous job of spitting out very readable error messages. It removes so many debug cycles from development that it alone is worth switching.
They're working on it. There's no tried and true formula for succeeding as a business, we all know that. I'm not sure why the expectation from everyone is "well, they have BILLIONS, they should just be able to churn out more success shouldn't they?".
http://www.investopedia.com/articles/markets/030416/googles-...
I'm not a rocket scientist, but I would say likely that's when the launch window opened, or it was inside the window to be able to get the craft on the right trajectory to Mars. Launch windows take into account where the target's orbit is (in this case Mars) and where Earth is inside that window. In this case, the launch window was likely quite large due to Mars' orbit being quite a distance from Earth (and quite stable) which leaves quite a bit of time for correction burns in case the rocket is off course at all.