halpme

I work there and today's been utter chaos. Lots of meetings with upper management and people wandering around confused. I came in to work in a new position in a new team with a new manager. They probably shifted all the people they didn't care about into roles where they would be unhappy and eventually quit, as opposed to outright laying people off. Meg's mentality is that basically any unit of HPE has a pricetag. I'm probably going to stick around for a few months and quit if I can't transfer back to my old team.

Sunnyvale, CA

Off-topic: but I'm really happy to see an increase in reverse engineering threads here on HN.

Why do you say that?

How do you identify people who "can't code their way out of a paper bag"? What is it about their skill level that makes them seemingly incompetent?

There's a lot of video content on a lot of topics, but their content is shallow. If you want to get a deep understanding of something, reading textbooks and official documentation is likely the way to go.

I have the best of both worlds: Eclipse IDE with a vim plugin (vrapper). Not sure why people choose strictly one of the two.

What makes you say that Apple is dying?

Software Engineer @ big old enterprise company doing security work.

Side projects: None. I believe in having a life outside of programming. I don't touch code after 5PM. Currently training to run a half-marathon and getting more serious about powerlifting.

Reproduce the bug. Reproduction steps/environments are usually provided by support engineers or QA. Look through log files for any specific error messages, and use grep to find where in the code the error is coming from if it's not specified in the exception stack trace or something like that. Look at the code and form a hypothesis about where the bug might be located (use a "binary chop algorithm" discussed in books such as Code Complete and Debug It). Create breakpoints and step through the code with a debugger and record your observations. If you still haven't found the bug, use the data you just collected to form a stronger hypothesis and repeat the process until you've identified the source of the bug. Then apply the fix, and run some unit (or integration?) tests to verify you didn't introduce a regression or that you actually treated the symptom instead of fixing the root of the problem.

This might not be the best approach, but it generally works for me. I highly suggest reading the following books: Debugging, Debug It! and parts of Code Complete.

To echo what everyone else has said, my feed is utter garbage and a lot of friends post stuff that makes me cringe. I've unsubscribed from the majority of my friends so now all I see are ads and sponsored posts.

Here's the thing, I get to see what events my friends are going to, which usually end up being really fun and not something I would have found out about otherwise. So nowadays I only use facebook to find and management events to attend.