skysight-inc/HackerNews huggingface dataset:
Poachers are not largely in poverty. Poachers are primarily large, well-funded criminal syndicates, although they do (sometimes) use impoverished locals for their hunting ability and knowledge of local conditions.

The boom in trade in rhino horn, elephant ivory, etc. has been largely fueled by increasing incomes in China and elsewhere. It is not the result of poverty.
What you're essentially telling your engineers is that A) doing their job has nothing to do with getting better at their job, and B) if they want to advance beyond the junior engineer level, they will have to do so on their own time. I've seen this referred to as "terminal juniority."

Having a development process that does not produce senior engineers is a problem, even if you try to make up for it by providing a conference attendance budget and a Safari books membership. At the very least, such a process unfairly penalizes those with large personal time commitments.
We shoud devise ourselves to collecting as much cell cultures as possible. Then we do not lose information and might as well recreate this diversity in the future.

For example, Siberia will really like to get rhinos, mammoths and other large animals back, and it is possible to breed them from existing warm-climate ones. And there's a lot of space for them to thrive.
Are you really saying "all of society's problems exist because men run everything" whilst also saying "all of society's accomplishments are despite men running everything"?

I don't mean to put words into your mouth but that is how your statements read to me.

OK, having read more of this discussion, I don't think that's what you're saying. But what do you mean by patriarchy? What do you mean by its crimes?
Quantify the value. This is part of an effective sales process. During your investigation identify what they're trying to improve - sales is an obvious one but business value can be assessed to be things other than increasing revenue. Other examples: improving efficiency/operational cost by reducing overhead or making a process more efficient so that resources can be reallocated to other parts of the business, improving margins, expanding the addressable market through product changes or other avenues, etc.

The key is being able to quantify the change/goal. If it can't be quantified it's probably not worth your time or theirs, seek something that is. Once quantified you can price it based on the value you'll deliver. They can make the decision based on whatever they want to use to assess its cost/benefit but it should be obvious and a no-brainer if the investigation was through.

If you're stuck in pricing things based on your costs or dealing with individuals who can't articulate/quantify their pain it might be best to seek other opportunities.
Ask HN: What new developer tips should I make for Dev Tips Daily?
I make these gif-style developer tips on "Dev Tips Daily" (https://umaar.com/dev-tips/). So far, they've all been DevTools related and I'm wondering what else would developers like to see? Some examples:

- Sublime Text / Code editor workflows
- New web platform features like service workers
- Frontend performance

Also I'm using Github as an issue tracker so you can leave feedback on what you'd like to see next: https://github.com/umaar/dev-tips/issues?q=is%3Aopen+is%3Aissue+label%3Aenhancement

Thanks.
It isn't 2001 anymore.
Interesting idea, especially if the site comes with the support of actual Hollywood studios. Anyone have more information about this? Website is pretty sparse...
You raise an interesting point.

I've thought about this with respect to the Oryx, which has been extinct in the wild since the ~1920s, but found a niche on game farms in Texas and Argentina. Now, hunting the Oryx is illegal in the United States and I've wondered how long until the animal goes extinct. At $4000 to $7000 to hunt, it was a lucrative trade.

I would guess that the issue with rhino/elephant would be resource management of a herd that does not hit breeding age for quite a few years. Of course, at these prices, that could work out.

Personally, I think the Asian horn powder market is barbaric.
Top Amazon Webstore Alternatives. Where Do You See Your E-Store in the Future?
I'd say your comment was rightly downvoted because it was inflammatory, unsubstantive, and off topic. One needn't disagree with your views to see how that breaks the site guidelines.
"Mobile First" describes a methodology of starting on smaller screens with less 'estate' such that no important details are left out.

"Desktop First" makes it really easy for your solution to something looking bad to be "just display:none it", which can make the mobile version feel like an afterthought (because it often is).

"Mobile First" just means you take into consideration the mobile aspects and make sure everything important is included - and you scale it to "Desktop sizes" afterwards, since you no longer need to hide anything (only change how it is displayed).

The design, regardless if Mobile or Desktop "first", should look good on any screen. That's what Responsive Design is about.

You can do Mobile-First Responsive Design. The two aren't separated and the article seems to pretend that they are. Responsive Design has always been about making sure the product looks good regardless of screen size.

Because that can be expensive for complicated sites - many web design companies choose common screen sizes like the iPhone, popular Android series (Galaxy/Note), and common Desktop Resolutions. The best designers do away with all of those constraints and design based on "when does this design look bad?" rather than arbitrary break points.
Absolutely... as others here have said, if you don't have people who want to think, then no amount of process can save you. You only have deal with any official bureaucratic process or government department to see that.

From my POV, a minimum amount of process is useful to keep things on the rails when the pressure goes on, so people don't end up doing things wrong. After all, unit tests, git and CI are 'process'...
> and revise your processes accordingly

This. So much this.

Your process is one of the things you change. You hack it. You can try a change for one iteration and evaluate at the end of the iteration.

If you have a Defined Process(TM) - of whatever flavor - you're missing a big part of agile, perhaps even the most important part.

Let your process adapt to your people, your environment, your situation, your project, and your goals. Eliminate everything that isn't useful; shorten to the minimum everything that is useful.

Even if you started with Agile(TM) as defined by a Scrum Master(TM), but you're willing to change the process as you find out what doesn't work or is wasteful, you can still converge on something pretty good. You just have to keep tweaking the process, paying attention to what works and what doesn't.

Or to put it in XP terms: Pay attention to pain, not just in your technical areas but also in your processes and procedures.
You've created a strawman to attack by citing waterfall.

Stop citing waterfall as the reason for agile methodologies. It's like citing the lack of evidence for a christian God as the reason Science exists instead of pointing out how effective science has been in helping us control our environment.

And if you can't describe how effective Agile has been, then have you no reason for your opinion outside of religious views. Which is ok if it works for you, but don't attack a strawman as a way of dismissing other people's experiences.
That's an interesting idea. Thanks. Though, personally, a big part of what appeals to me about rendering with distance fields is the simplicity of it: no triangles and, most everything is in the shader so I don't have to waste time fine tuning how my buffers are pushed around for OpenGL.
Apache Mesos 0.22.1 Released
I don't get it - can you upgrade a Windows 8.1 standard to Win10 Pro?
And where do you work that this is even allowed? Maybe it's only because I work for the Federal government, but there is not a snowball's chance in hell that I would be allowed to attach my personal machine to the non-guest network in any way.
Introducing Alive
I vary my sleep schedule a lot. I'm 40. I've given up on any hope of reducing the amount of sleep I get without bad effects. I do believe you can manage when you sleep to maximize productivity, though.

I have a 6 year old son, and I lie down for a nap when he goes to bed between 8.30 and 9pm - it's convenient timing. I tend to aim for 90 minutes. If the alarm wakes me, it wakes me, and I'll stay up for 2-3 hours and if I feel I have the energy I load up on caffeine and stay up all night. The next couple of nights I'll probably sleep straight through from my nap time and never notice the alarms, or at most wake up briefly.

The end effect for me is that I regularly get 6-8 hour long concentrated periods at night where I feel rested and alert, and still have enough energy to last it through the work day and early evening afterwards.

With the caveat that any deficit accumulates. If I don't "pay for it" immediately I'll feel more and more tired as the days goes by and end up taking a week or so of going to bed early to recover. That part was easier to avoid when I was younger.
The beauty of Agile is: if you question or criticize it, you don't understand it; if it didn't work for you, you didn't apply it properly; if you applied it rigorously and it failed, you didn't have a deep understanding of it. Was it Sartre who said "it is what it is not"?
Sorry, I will keep this in mind in the future.

I thought references to what I was saying would be helpful, to prove that I wasn't talking out my bottom. Hence, I was trying to give references from major newspapers and other media resources that backed up things that I knew from memory. A lot of other assertions in this thread (or indeed in a lot of HN threads) don't do this, so I assumed it was a positive.

> prefabricated lists of links and talking points

As I said in another comment, a lot
of things can't be verified over the Internet, but I will tell you that my list wasn't prefabricated. I wrote that paragraph (or a rough skeleton of it) from the various anti-male things I had seen in the media (not very difficult, IMO); and then took the time to search for the exact details, and added in the references.

I do agree that it is a hodgepodge of various things, which significantly detracts from its quality. I'll try to narrow down my comments in the future as well.
A remote desktop session into the my employer's network from guest wifi works fine within their building. My laptop running the rdp client is faster than the thin client they issued me with!
It means that folks with little to no technical experience (read: authors of WiReD articles) will latch onto the new buzzword and start regurgitating it left and right, eventually tricking other technologically-illiterate people to latch onto it and start pelting me with questions like "OMG DID YOU HEAR ABOUT VENOM???!!!" and "OMG U BUTTR PASH UR SURVURZ OMGOMGLOL!!!!111one" instead of letting me do my job. All because the publishers want to satisfy their attention-seeking desires ("LOOK AT ME I FOUND A SECURITY BUG AND GAVE IT A HIP COOL BUZZWORD I'M SO SPECIAL!!!!").

I personally don't like the trend for the same reason why I dislike terminology like "ninja" or "rockstar" or "badass" or "devops". It cheapens computer science/engineering into resembling something a bunch of hip middle schoolers yammer on about alongside their video games and their skateboards instead of the multi-billion-dollar professional field it actually is.
>Characters who speak other languages

The sections where they spoke Japanese really took me out of the world they created. It was so poorly executed.

Having said that, I LOVED the series as a whole. Very well done.
Minus the cost of marketing, distribution, product engineering, customer support, security engineering and lawyers (e.g. for dealing with the legal and security implications of managing customer wallets).

Additionally, I estimate that it's much more pragmatic for 21 to build a centralized ASIC farm at a location where power is relatively cheap with predictable costs as opposed to a geographically distributed ASIC network that will be subject to regional utility price variance.

Why bother with all that when you could literally just mint money at your leisure?
Nowadays security research looks like a lot of extra work. Having to do the research and also think about a logo, website design, choice of colors, pretty diagrams, a cool name, social media interaction, market research to make sure all that isn't too similar to previous bugs. Eww!
with modern software, it's only hard to do right if they're not at their laptop/workstation. which means they're doing some other shit other than working.

our entire team is remote. it's really obvious when someone isn't at their computer. it's basically the only hard requirement of the job beyond the work product - be at your computer when you say you are going to be at your computer.
Given FUSE is much more widely used, I suggest you explain the benefits of 9P over FUSE.
Unless you're part of the general public who lives in a desirable area, and your rent is increasing because limited housing is being turned into unregulated hotels.

I should say, I've used AirBnB many times and always had a great experience, but this isn't a clear cut "good" vs "evil" issue.
The tax argument aside - my understanding is if the constitution doesn't provide for it, the federal government shouldn't be doing it.

10th amendment: The powers not delegated to the United States by the Constitution, nor prohibited by it to the States, are reserved to the States respectively, or to the people.
A win for people trying to afford homes they actually intend to live in, and for their neighbors who didn't agree to live next to a hotel.
Thanks for this tip, we will fix it!
Fantastic post, and I agree. I've always been in a weird place professionally because I came out of school at a somewhat-above-junior level and so I've been in an interesting position to watch companies try to mold developers. There's that "five years of experience"/"one year of experience, five times" thing people sometimes refer to, and Scrum seems tailored to doing the latter.

Terminal juniority is an amazing term for that. Thanks.
Santa Monica Bans Most Airbnb Rentals
Rhino horns = illegal and dangerous = very expensive = rich buyers.
Hey, I'm one of the founders/developers.

There are definitely plans for an Android app, that's one of the first next things we will work on as we gain users.

Currently, the app text messages people who don't have it installed, including android and winphone users -- basically the same thing GroupMe does.

:) thanks for checking it out, keep the feedback coming!
I live in downtown Los Angeles. In my community of buildings all tenants were served letters that threatened eviction if we put our place up on Airbnb. It is specifically outlined in majority of our leases. Several people I know have been evicted as a result. Regulations aren't even needed some buildings are just taking care of this issue on their own. For my specific building and as a renter, I'm okay with there being no Airbnb places.
Make a web page fast and easy
This kills BYOD, right, at least for now? "Employees can only access corporate applications with a device that is procured and actively managed by the company"
In Guild Wars 2's case, there's a significant portion of the API made available to the public, including the trading post. https://wiki.guildwars2.com/wiki/API:Main

I don't believe this includes "write" operations like buying or selling, but since the in-game trading post communicates through the same web-based, it probably wouldn't be too much of a stretch to piece it together.
My work has required daily VPN use over most of the past 7 years, and I have yet to find one that is reliable. I'm certain this has more to do with properly setting them up then an inherent flaw in the concept, but it still means when I can avoid them, I do.
I'm going to need to see a complete site NOT using jQuery made by the people behind this before I can accept "However, times change and today we would use vanilla JS for the site.". You probably believe that statement 100% but it's an easy statement to make without the work to back it up.

> I actually love jQuery! Yet, plain JS has become pretty cross browser safe and once familiar with it, it isn't harder to develop most sites in vanilla JS.

I fundamentally disagree with this statement and I think it comes from someone who either hasn't done it or has done it on a tiny scale which doesn't really stress your JS chops.

> Also, useful methods previously known only to jQuery get accepted as DOM methods. E.g. DOM4 includes methods like .closest(), .append(), or .prepend(), etc. This makes plain DOM manipulation similarly readable as jQuery. But it's not yet widely supported ...

All the more reason to keep using jQuery in my opinion. jQuery will use the built-in methods if they exist and "polyfill" (yes I know that's not exactly the right usage of that word) the parts the browser doesn't all without bothering the developer.

The thing I keep coming back to is when people go down this PlainJS route here is what undoubtedly happens:

1) Oh yeah! Look how cool I am, I don't need no stinking jQuery!

2) Hmm, this doesn't work the same in both browsers. I'll just created this little helper functions to handle the differences.

3) Repeat #3 1 to Infinite number of times

*) Oh... Well my helper library has grown quite big and does pretty much what jQuery does (not all of it but most) all without being thoroughly tested nor being used by a MASSIVE chunk of the internet.

You almost always end up re-creating jQuery or parts of with the same slowdowns you worked so hard to avoid. All while making your codebase MUCH less readable and making it harder to bring new developers on the team up to speed with not only your PlainJS way but also your completely custom jQuery-clone. People can keep selling them "jQuery is so big and slow" story and I'll keep not buying it... I will GLADLY sacrifice a little speed here and there for the hundreds of hours of QA/Debugging/Bug-fixing I will save and I think most developers would agree. There is a reason that browsers implemented things jQuery does... BECAUSE IT MAKES SENSE, I'd rather be on the cutting edge of what CAN be done instead of waiting for browsers to implement it and users to upgrade. It's close to the same reason we use Babel JS to transpile our ES6 to ES5, I'm not going to wait for those new features when I can be using them today which results in not only speed ups in development time but also future-proofing our code to a degree. With jQuery if there is a faster or better way to do something all I need to do is upgrade jQuery to take advantage of it which cannot be said for your approach which would result in either not using the new stuff or writing your own wrapper to handle the differences between browsers (new functionality may ship fast in evergreen browsers but the first few implementations rarely match cross-browser implementations which is why we have jQuery.
Show HN: A simple Safari extension to filter tweets
It's worth reading the original "BeyondCorp" paper that discusses this:

http://static.googleusercontent.com/media/research.google.co...

As some other folks have pointed out (and contrary to what the headline implies), there's isn't just setting your firewall to allow 0.0.0.0/0. In particular, pay attention to the Device Identity (client cert) and the Access Proxy parts.
When nearly any service, technology, or community hits an eternal September critical mass, there's going to be people who don't adhere to the "don't be a dick" philosophy of whatever bandwagon it is that they are joining. At that point, the timer to the beginning of true disruption and the end of innocence starts ticking down fast.

AirBnB has hit that (several times, in several ways). Uber has hit that. The general tech industry and tech culture in the bay area has hit that. Drones and to a lesser extent, 3D printing, are getting pretty close. On demand services (Instacart, etc...) are close as well.
This is against so many IT security best practices, you're probably breaking a regulation if you're in an industry not dealing with selling jewelry on Etsy.
There's an easy better method: assign variables starting from the lower order digits, greedily check correctness, and skip over all permutations with that prefix if it fails.

Although I don't know how one would go about proving or disproving if this is asymptotically better or just a (substantial) constant-factor speedup.
There are different layers of firewall, and VPN isn't really the issue here.

You can still have location-aware servers that can talk to eachother directly. This should be done over an encrypted channel as much as possible.

As to firewalls, on each server only allowing access from those ports applications run on is probably a good start. Better still would be publicly facing machines that act as reverse-proxies to backing servers that run said applications.

As intimated only approved machines (likely with client certificates and pinning to mac addresses, and probably only a limited number of accounts beyond that) can tighten things farther.

Putting your exposed (internal use) applications facing the internet doesn't mean unlocking all the doors. There are ways to mitigate and reduce the effects of a 0-day vulnerability in practice. The fact is that by making it all available anywhere, makes you think of the risks in a way that is actually better in practice than just believing because you are behind a hard shell it isn't easy enough to get to the soft-gooey center.

A hardened system involves more than firewalls and vpn access. A properly hardened system should be able to run over the internet. TLS channels with certificate/mac pinning alone can go a long way in terms of communications, and is far more than a typical firewall/vpn setup would offer for protection. This goes from SSH to your internal services. For that matter not exposing anything beyond SSH, and requiring tunnels for all communications may be simpler still.

Mix in LDAP for access, with accounts, machines and certificates all tied together and you have a pretty good base recipe for a hardenned system. That said, this isn't the only approach, just me rambling on about the ideas. There is overhead in terms of development, operations and management to setup such a system. Not everyone can implement such a system, given what they may be starting from. A smaller company would have an easier time for many cases than a larger company. It may require the use of a windows terminal server behind a secured channel in order to keep some critical applications (likely wrt finance). Other applications may be excessively costly to migrate, and others still may not have the necessary protections.

Given that most internal applications are web based these days it is slightly easier than at any other time in computing history.
> require mass mobilization and mass education to fix

Except that Crowdstrike is heavily involved in 'threat intelligence' so this isn't really about patching vulnerabilities at the technical level but educating non-technical executives on threats and 'threat actors'. So corporate execs can be handed a dossier of recent events, like they were the US President evaluating their national security policy.

The only problem is that threat intelligence has marginal value, as infosec changes so rapidly and is so diverse, so at the end of the day it is very much simply emotional gratification - that Crowdstrike delivers at a very high price.

In terms of resource utilization, it doesn't seem like a good use of time/money to obsess over each bug as if it were an atypical event in a slow moving enviornment. But hey if it gets a few people at the top to start caring about security, maybe there is some value... I just hope it doesn't result in execs nagging the infosec team for updates on 'venom' and disrupting their work on real security measures for the company by focusing on the latest hot topic.