matthewrhoden1

I never thought about it but I became curious as to what the differences are, here's what I was able to find:

[0] Aircraft grade aluminum alloy's composition roughly includes 5.6–6.1% zinc, 2.1–2.5% magnesium, 1.2–1.6% copper, and less than a half percent of silicon, iron, manganese, titanium, chromium, and other metals.

[1] Aluminum cans are typically 1% magnesium, 1% manganese, 0.4% iron, 0.2% silicon, and 0.15% copper.

There are a lot of metrics that determine the appropriate use of various grades of aircraft level alloys [2]. I guess from the outside some big considerations are how the metal reacts to temperature change and how well a metal cylinder can handle stress while staying light.

[0] https://en.wikipedia.org/wiki/7075_aluminium_alloy [1] http://www.madehow.com/Volume-2/Aluminum-Beverage-Can.html [2] https://en.wikipedia.org/wiki/Aluminium_alloy

Since the article stated that 50% of adults account for cinnamon toast crunch I'm thinking it's because we're realizing that even if we do eat it, we're still hungry within an hour.

After building the habit of eating a solid breakfast, I noticed others followed the same pattern I did; eat two big meals and feel too nauseated in the morning to eat.

edit: the eating two meals part was during my cereal phase.

While you can't edit, you can view for free:

https://www.microsoft.com/en-us/download/details.aspx?id=4 https://www.microsoft.com/en-us/download/details.aspx?id=10

When I started to play around with Node and learning about NoSQL, this was the first thing I thought of. I knew this was going to happen.

Sworkit was supposed to be an example of a complex app for ionic, not sure what else is out there. I've used that app and can say it seems pretty solid (no crashing, locking up my phone, etc.)

http://blog.ionic.io/built-with-ionic-sworkit/

I did a pet project using the vibration feature and it worked pretty well, but haven't tried on an iphone.

I can't speak for pushing the limits of the hardware though.

This is awesome! I spent probably an hour or two yesterday wading through all of it to figure out exactly what each piece does. This make it really clear.

When I was single I was really into fitness and as a result also made sure I got plenty of sleep. I would go to be really early to ensure I got the full 8hrs. Once I caught up on my sleep something funny started to happen. I would only sleep about 4 hours, then wake up for 2 hrs in the middle of the night. Then go back to sleep for a few more. Net result being only about 6 hrs of sleep.

Anymore, I'm of the opinion that your body knows how much sleep you need. That being on a schedule is almost more important than the specific hourly amount.

Despite the fights breaking out over accuracy I still found this article insightful. Eating 170 calories worth of broccoli vs 170 calories of honey does have a strong difference. I'm sure you can still loose weight by counting calories and adding a little exercise, even if you're adding honey to your diet. But this article at least explains why you will progress better by eating stuff that is a lot less processed.

It sounds like they're going to have to go to a credits model. You buy $10 worth of credits and use those to unlock images.

When I saw the segway, I thought it was way weird and didn't like it. When I saw this, I was a little excited about it. Funny how a small change in design makes it seem cooler to me.

To the people worried about the gravel, since this guy is traveling over brick side walks in the video (see 44 seconds in) I think it will do just fine on normal side walks.

I didn't see the article for when it's 2AM and you can't get that one last bolt off.

I've worked in a lot of legacy code bases. Here's my approach: * Skim around to get a general idea of what components are involved. * Try to understand that one module/class that keeps getting used a lot or is really important. * I mentally trace through that code, as if I'm a debugger. * Most importantly, I write down my discoveries/understanding as I go to help me retain this idea. * Re-skim with my new understanding and/or reorganize the code to be more concise or simpler. Depending on how ambitious you are, you might try to keep these changes. But with legacy code, it typically breaks as a result.

Every code base takes time to digest all the information. Sure the information passed your eyes, but is it committed to memory?

You're mouse must use a lot of power. I use a Logitech mouse (http://www.logitech.com/en-us/product/anywhere-mouse-mx-p?cr...) and I forget it even runs on batteries.

If you have enough light in the room a solar keyboard is also pretty awesome, I had one for the longest time. Kept it until I accidentally broke the keys cleaning it. Keyboard selection is very much based on taste though, so I assume you probably saw one and didn't like it.

I wonder if it would be better to have a smart bin that would simply push products down a slide to a conveyor belt instead.

I feel like this is the next episode of game of thrones that I'm waiting on, looking forward to reading it

Northern Virginia, yes they sometimes do. I got more of the language specific questions though. "In C# what's the difference between static and const."

When I interviewed google, they wanted me to code something up for them. In California, again I had mostly language specific questions. I did get more logic questions though. It varies from company to company.

Most engineers I talk with though, don't struggle with the problem solving. It's the soft skills and being able to confidently respond to typical questions that they had a hard time with. Easy fix if you do what I suggested.

I applied to full stack positions for mid to senior level. Some do go into technical questions, that's what the brush up is for, however they usually target exactly what was in their job description.

If you're an engineer I'm assuming you can usually fight your way through a problem they give you. A lot of places I interviewed seemed to do the same thing -> (man I have an interview, better google a few questions to ask them).

The important part is that you look at their job description, you will usually cover 75% of the interview preparing like that.

Most of the questions in your interviews are not actually technical, unless your interviewing google or something. Here was my approach and I got a very large pay bump as a result :)

Sit down and list all your projects you completed at your previous jobs. These will give you a great refresher and are going to be your talking points. Have both good and bad points ready. The bad points are for curve ball of questions like, "whats you're weak point." It will also show you can reflect and improve.

Go crazy lining up interviews, that's one great thing about our industry, no shortage of companies to interview with.

A few hours before each interview, look at the job description for clues. You'll pick your top three things that you feel would make you a great fit for the company based on your past experience. "Need to be able to refactor", hey that's all I did at x company for y time and of course the project was successful based on z metric.

That was mostly it, of course it helps to do a quick refresher of tech specific interview questions from google. This is mostly to boost your confidence and to keep you from feeling too nervous.

Good luck!

I didn't understand what he meant by you get 9 hours of interviews transcribed. Does it mean you're interviewing with the person via Skype and then you get a copy of what was said or you're watching a video of someone else's interview with what they said?

I think technically you could setup a light weight server on your phone and you could get an address for it and expose it to the internet. However, that would only be for that cafe they are sitting in. Since the server would need to stay in a fixed location or keep updating the DNS everytime it moves. This would then take time to propagate, it's not immediate as far as I can remember. I could be wrong, I'm a little weak on my networking, but I believe that's why.

I know there isn't anything to worry about, thanks to that one guy popping his knuckles in one hand for 60 years (quick google: http://geekologie.com/2015/03/taking-one-for-the-team-man-cr...) but the description in this article made me not want to pop mine anymore. :(

It really get's my blood boiling seeing that second post. I can't believe that people like that exist. I've actually had something similar happen me, except I wasn't doing an Air BnB listing. I got a roommate who turned out to be a dead beat and actually knew all these laws. I made a huge mistake not getting our agreements in writing. I never expected to meet someone so spineless. Anyways, I had a new found appreciation for these kinds of laws after that mess.

You may have been in the work force for longer than your peers, but you're still green in this new career track. You'll just have to accept that you're going to get a little under foot from time to time. This is why you get to make so much more later :)

Early in my career I also felt overwhelmed, you get this feeling that there's so much to learn and almost no time. What if you spend a month training on Angular only to find it's out of date?? My advice, don't worry about that. Even if that happened, the knowledge is still useful because either (A. the release docs of the next version will be enough to get you up to speed) or (B. you've just been exposed to one approach of doing things and you will see this re-surface at a latter point.)

Take one piece of technology or programming technique you're using or need to know in your current job, get some books, training videos, etc. and learn it well, then move on.

I see a lot of comments saying to go outside. Not a bad idea, but I think you were looking for new ideas. Ways to be innovative. If that's what you meant, I found one new way of thinking is finding a hobby or interest and pursuing it for a while. If it's ideas for software you want to write so you can make money, then you cross the two (your hobby and your job skills) with "hopefully" a fun project as a result. This is one of many routes to finding market niches. If it's no longer interesting to you, move on to your next item. Most people have a bucket list anyways, so I think it's a good practice for the sake of your feeling of life fulfillment.

I wish it were rare, I've seen it in a lot of projects I've had the privilege of dropping in on. They will often check for an error and log it, then "throw;".

edit: to further clarify my objective, I was thinking of a way to make the stack traces better, without risking the maintainability of the code now that I'm aware of the difference. I guess in all it would be best to just remove it. In my case, we've found some strange things in unexpected places and I prefer to not change stuff, unless I understand how the underlying portions work.

It looks really weird to me, having that empty catch block. I expect a lot of issues to accidentally be introduced from poor merges or something.

I couldn't agree more. Unless it's a startup, or the company produces "throw away" solutions. You're usually dropping in on a product where either the previous team was fired or it was boot-strapped by one guy who knew was he was doing, supported by 5 junior devs fresh out of college.

I don't have smooth scrolling, so these types of things are always jumpy and not very enjoyable.

First point in the header "Use photos from Instagram, Facebook, and your computer" what if I wanted to just use my computer photos?

Very true, you might not consider me your average user.