furstenheim

11 ms·

91.
by furstenheim 5y ago
Specially since it can only done in Eclipse xd
92.
by furstenheim 5y ago
This article is not very good in convincing that prototype pollution is a problem. There was a write up about the kibana rce that really shows it's a problem: https://research.securitum.com/prototype-pollution-rce-kiban
93.
by furstenheim 5y ago
I don't mean lombok as a library, which works. I mean developing lombok itself
94.
by furstenheim 5y ago
100% lombok can only be developed on eclipse. They have an open issue to make it compile on intellij...
95.
by furstenheim 5y ago
I'm surprised it didn't mention the more extreme case of Mike Merrill https://www.wired.com/2013/03/ipo-man/
96.
by furstenheim 6y ago
This looks really useful. Paradoxically, I find that the terminal is the place where I end up using the mouse the most.
97.
by furstenheim 6y ago
Lots of red flags there: - Dev installation guides with credentials to prod. - Tests that delete everything, not just what they create. - The obvious of giving access to delete production on the first day. - Where they lacking backups?
98.
Show HN: Unit Test AWS Step Functions(github.com)
1 points by furstenheim 6y ago|0 comments
99.
by furstenheim 6y ago
I find value in part of it. Dailies I find very beneficial. You get to hear what other people are having problems with, and maybe you already faced something similar. Or the other way around, when you face it you remember that someone solve
100.
by furstenheim 6y ago
Totally, and if you mix it with yarns plug and play you should get best of both worlds
101.
by furstenheim 6y ago
Yeah, maybe "deal breaker" is to strong. But I've had consumers of a library not being able to use it because a critical dependency (html parser) was not the same version as they had
102.
by furstenheim 6y ago
Coming from node world, global dependencies like in java and python are a total deal breaker. In node same library in two different versions can coexist in different parts of the dependency tree and that's totally fine (there are some
103.
by furstenheim 6y ago
Npm ecosystem already has the solution. Use namespaces @yelp/infra-js where @yelp is the npm user. It's not possible for an attacker to publish on that name in the public npm
104.
by furstenheim 6y ago
There are such stories. Roald dahl has a very nice short story about it https://www.roalddahlfans.com/dahls-work/short-stories/the-g... .
105.
by furstenheim 6y ago
Good point
106.
by furstenheim 6y ago
I like to think of it in algorithmical terms. Maintaining the code is O(n) on the size of the code
107.
by furstenheim 6y ago
It's different calling someone out of the blue, than calling someone you're meeting in 30 minutes.
108.
by furstenheim 6y ago
Not specially hard. And you're comparing different stuff. I'm not using a different phone because it's easier, but because having a smartphone is distracting. It's noticeable, but in case you need a link. https:/&#
109.
by furstenheim 6y ago
What I do is tell the other person to reach me on a call if there's any change of plans. That's been enough. Also in case we don't see each other.
110.
by furstenheim 6y ago
What I do is to tell the other person that I'll be using this other number and to call me if there's any change of plans. Edit: I actually have two phone numbers. So the new phone is still at home receiving everything
111.
by furstenheim 6y ago
Something that I've found useful when meeting someone in real life, I take an old phone that's only capable of making calls. That way I avoid any possible communication issues, but I don't get distracted at all.
112.
Ask HN: Best Alarm Clock
2 points by furstenheim 6y ago|1 comments
113.
Show HN: Infinite Tiling of Art Images(github.com)
2 points by furstenheim 6y ago|0 comments
114.
by furstenheim 6y ago
This comes to prove the basic and probably only lottery strategy. If you choose (which you shouldn't) to play the lottery, then avoid common sequences like 5,6,7,8,9,10 or dates. In very unlikely case that you win, you'll most pro
115.
by furstenheim 6y ago
Datadog is providing tracing at least at a function level, so it should be possible
116.
by furstenheim 6y ago
Something that I've thought sometimes. A tracing mechanism in all branches. And you check in production which lines are never executed. Of course, some things are tricky. For example, handling of cases that should never happen, but may
117.
by furstenheim 6y ago
This has really struck home.I'm missing another one. Your dataset is tilted 90° and in some other part of the globe: you probably swapped latitude and longitude. Tip: latitude sounds like "altitude" so it has to be the y coor
118.
by furstenheim 6y ago
As they say, warmest October among the past years, coldest October among the ones coming...
119.
by furstenheim 6y ago
Shameless plug, sometime ago I ported webscraper to work with node and puppeteer https://www.npmjs.com/package/web-scraper-headless . That way one can build the scraper with the ui in the browser from the extension htt
120.
by furstenheim 6y ago
> Domino effect: one bug can take down the entire system at once It bothers me that this is always set as a selling point for microservices, when it's actually the opposite. With monoliths (or at least monorepo) it's easier to

More ›