If someone were to have a mightier-than-thou attitude when giving the feedback, then maybe that would throw me, but I would more likely get annoyed because feedback from people like that tend to be redundant or just complete shit.
21 karma · joined May 31, 2013
If someone were to have a mightier-than-thou attitude when giving the feedback, then maybe that would throw me, but I would more likely get annoyed because feedback from people like that tend to be redundant or just complete shit.
Nowadays, people seem to care less about this technical aspect and more about whether they like you (but perhaps it has always been this way). They also seem to be stuck on very specific ways of doing things (to the point that their reasons for not hiring you may seem arbitrary and stupid), and anything that's even slightly off from this will result in failure. So you have to figure out how to have them like you, what they will perceive as you demonstrating competence, and the true reasons they are looking to hire for your position, then you have to do everything to fit that description.
It could be something out of your control and discriminatory, like you aren't the right age, gender, or race, but hopefully that's not the case.
Either way, I'm sure that no matter what they are looking for, they'll have trouble turning down a strong candidate, so figure out what it takes to become one of those, then enjoy. Also, you may be applying to the wrong companies.
I think a lot of people are getting bored and frustrated with the service, but they have a lot of history on the site, and they don't have a better alternative to turn to. This causes the wrong form of user "loyalty:" they are trapped.
It's hard to imagine a better service coming along, but they can eventually be outdone on the mobile front or their own internal inertia (which it seems they are fighting) will prevent them from being able to compete.
Change happens fast. Something will show up overnight, then BOOM.. the end.
My training in the CS fundamentals are solid, but I have a Computer Engineering degree, so there are some gaps (weakness when it comes to graph theory), but those are made up for by a wide range of experiences in Electrical Engineering whose applications overlap Software Engineering in a very real way (if you can see it). For example, I use the Kalman Filter in my head ALL the time, and it seems like thinking about things as being in a black box that you feed input and get output is very useful for debugging and getting started quickly. I naturally like drawing connections between disparate things, and learning a wide variety of things which can then in turn be applied to a wide variety of things, so a Computer Engineering degree was the correct one. I can easily brush up on the gaps, which is what I'm doing now, and then all that exists is a Computer Scientist with all this extra knowledge that he's waiting to apply in clever or unique ways.
I not only know backend and frontend, but I'm good at both. Though I'm good, I'm often unconventional, so those that are sticklers for convention and the specs won't be able to appreciate the work that I do. I spit in the face of minutiae like code formatting and spending a lot of time breaking things down in favor of getting something working, then when it's working to my satisfaction I can dive into all the details. I would previously get overwhelmed, because when starting a new project I would see the entire system and how it all came together and would get stuck on all the details, but after learning how to wait and how to let things marinate for a while, I see this as a good thing. I see everything connected together, and design a system that's holistically sound. And the better I get across the board, the better wired together the system is.
If you are a backend engineer, then learn javascript and that will get you a long way toward being a full-stack developer. It seems as though picking up language is not that difficult for many engineers, so you can just think of javascript as another language. Then learn HTML and CSS. Even if you don't become full-stack, it's good to know the other side of the fence, so you have an idea what's going on. All you have to avoid is to try forcing baby-understood conventions, as though you know what you're doing, on those front-end people trying to do something different, or that all of a sudden seem to not know that much. Things are rarely as simple as these management-fueled blanket rules (which are often sh*t).
That said, I hope I'm wrong.
I don't know how it happens, but somehow, even though it's compiled into a faster-executed runtime, many Java applications end up slow anyway.
"Powerful" language.
Then again, they also have some of the best Engineers. But I don't think that's a testament to a great hiring process, as that could be the result of great marketing. The "we allow you the freedom to actually do stuff and to work with the best" type marketing. From what I read/saw, the great Engineers didn't seem that happy, so maybe those marketing claims aren't really true, but perhaps things have changed since then.
Programmers need to grow, so it's important for there to be opportunities to try new technology. Obviously this can't frequently get in the way of the main thing, but it matters; you don't want to fall behind.
Image Search: https://chrome.google.com/webstore/detail/search-by-image-by...
Hacker News Infinite Scroll: https://chrome.google.com/webstore/detail/hn-infinite-scroll...