coward123

Their people pop up in every hiring thread on HN, it isn't just warent and it isn't the first time.

My experience was the same as tedvim above - it was utterly dehumanizing and there's no way I want that either for myself or for the people I hire. The interviewers were smug little shits who didn't take feedback to ask questions relevant to the position.

Further - you guys lurk all over HN commenting like this every time there's an interview thread. It's submarining and it's gross.

Karat embodies everything wrong with the tech industry, and Triplebyte wasn't much better. I've interviewed - and hired - hundreds of people in my career. This robotic approach with a focus on either standardized test type material and/or the leetcode interviews where how we interview doesn't match the work itself - it's just all so broken. I don't know the fix, but I know this isn't it.

Lemme share still another perspective that hasn't gotten any media time... my accountant at the time recommended we apply for EIDL instead of PPP, for various reasons. So here we sit now several years later with PPP as free money, having to start paying on our EIDL loans, all because we legit needed the money but chose the wrong option. So yeah - very, very frustrating to see the ways that so many people who clearly didn't need the money got a free government handout while those that did need the money just ended up with debt.

I'm a white dude, and had an incident a number of years ago in which a group of Indian contractors basically didn't want to work with me because I was a white dude. Used a number of slang racist terms in my direction. I didn't make a stink about it because I was a consultant just there on a short-term project, but it was memorable. As another commenter suggested, even the whole "white people" branding that happens in social media is comical, given centuries of one white group looking down on another white group. I'm glad to see this kind of social dialog about racism / classism in all of its forms and think it is very worthwhile to realize that it isn't just about the stereotype of white (males) hating on everyone else as is generally portrayed.

Hobby beekeeper here... I kinda disagree with her final summary... I get her point, but there are benefits to encouraging more people to keep them:

-- Additional pollinators.

-- Awareness. I've witnessed for myself in my own backyard the effects of our unusual weather this spring (ahem: climate change) through observing how my bees are interacting with my garden and trees.

-- Overall benefit: Personally, tending them makes for great therapy and my neighbors love the honey.

-- Advocacy. When you are in-tune with the impact of climate change, pesticides, herbicides, and overall aware of the ecology around you, you are more likely to make political and consumer choices based on those learned / observed experiences.

Perhaps its a coincidence, but I noticed more native bees in my garden now too. I don't think I've done anything net-new in terms of flowers or trees since I started keeping honey bees, but maybe I'm just more aware of the native bees now? Disappointed I've not been able to attract Mason bees, but I've got at least three other varieties buzzing around regularly and I've identified the hive of at least one of those types.

There are many that would say Heller was an activist court making up law and completely overlooked precedent in Miller, in the same way the current court is overturning decades of precedent in another issue.

um... why do you think these conservative judges were named to the court? They know exactly what they are doing and have every intention of ending contraception, sending women's rights back to the dark ages, and screwing over anyone not straight, Christian, and white. That's the job they were nominated to do.

Consider this a bit of code switching. Many of us absolutely are concerned about what this means for women, but we also know that this forum skews male and a particular kind of male. So we are making the argument here that resonates with this forum.

You are right though that more people overall - even those who skew conservative and pro-individual rights, should realize that if you take away rights from women, and then homosexuals, and then people who want to be married to someone of a different race... where does it end in terms of stripping away individual rights? I'd argue that if you view women's health care as a matter of individual freedom and rights, then is that not the same argument being made in interpreting the 2nd amendment as not about militias (IE: a standing army) but the rights of the individual? If I can tell women they can't have a set of health care services, what's stopping the government from telling men that they can't have a different set of health care services?

Oh for Pete's sake go back to your mom's basement you troll. Have you looked through your comments on this thread and others? You aren't adding to the dialog here, you are just being a jerk. No, I don't find the opinions of these writers challenging rather I get tired of having to go find sources that show just how munch bunk gets published. My beef is that I expect better from what are supposed to be journalistic leaders.

Am I the only person who has never even heard of half these products, let alone used them? If Apple can do something better than they can or their products weren't compelling enough for Apple (or similar) to buy them up, well... that's how the world spins.

My point is log analysis is noise to the signal. A poor way to discern what went wrong or to proactively monitor to avoid an incident in the first place. There are loads of tools out there, some of which have been mentioned in this thread, that monitor from network to user to app layer and are superior for triage. If someone is down in the bowels of logs, it's gonna be a bad time. I spent a decade triaging high-profile incidents around the world and teaching organizations how to do this stuff.

FWIW: In my career doing this kind of work, I found logs to be archeologically interesting, but seldom of value. Products that claimed to do things with logs gave me skepticism, because they were often like trying to do brain surgery through your foot - better to just go straight to the head. That is to say, if you could replicate the problem, better to watch it via full-stack monitoring tools in real-time than wading through gigabytes (terabytes?) of log data after the fact, often which had a randomness to their shape (IE: consisted of whatever garbage some developer thought was useful long ago and far away).

I give you credit for working in this space and trying to create a more automated approach... I spent many years in the app performance world both as a consultant and working on products, so again - good on you.

For what it's worth, my immediate reaction is that you might work on different terminology in how you present what your product does. I get that you are trying to create a contrived example in order to demo the product and show value, and that can be a very difficult thing to do. That said, in my line of thinking, an HTTP 500 isn't actually the root cause, it's a symptom of the cause. The password being set incorrectly isn't the root cause either. The real root cause is something in the deployment pipeline, the configuration control, the change management, the architecture, etc, etc. that got us to this point.

I guess I'm struggling here a bit too because I think of how many times I would have been the manual version of this, where I would show information like this to a client's technical team, and I had to absolutely spoon feed them on how to remedy. I remember a team that was supposed to be crack guys from a vendor, an app team, etc who had been working on a problem for months that I fixed in a matter of hours because they just didn't understand what the line in the log meant. So it isn't clear to me how your product is actually creating better visibility + interpretation of the problem toward a solution.

In the ten or so years I did that kind of work, what really stood out to me was that the seemingly obvious tech issues were not obvious because of a lack of education / experience /training on the part of the client personnel, but more often than not the real problems were much much larger architectural issues way beyond just the message in the log. Those are much harder to both identify and correct, but products like yours and the ones you integrate with are almost just a band-aid on the problem.

So, take that for what it's worth - again, good work trying to improve the state of the art in this area.

The WSJ deserves its own special place in hell. Once upon a time 20ish+ years ago, it was solid business and economic news. Then they decided to do a redesign to be more general news, and then Murdoch came along and turned them into the comics.

I don't give The Economist a pass either. I started reading it in high school decades ago. Over time, they've moved away from deep journalism towards more of a weekly recap. If I want to know what happened this week, frankly I can get that from Twitter or Apple News for free. What is lacking is the kind of forward, somewhat out there perspective. There are still little bits of this with The Economist, but its a shell of its former self. I'd also remark that they have an angle on the world that I find at time ethically questionable.