752 karma · joined June 16, 2010
Also I am wondering whether something fully integrated offers sufficient value or whether home assembled systems are superior in people's minds.
@Tam...seems to me like there were plenty of non tech businesses in there... restaurants, speakers, renting of items, office hours.
My core issue with these businesses, and 90+% of those I hear about in the valley, is that they are so extremely specialized for such an incredibly narrow market segment that they are next to impossible to get either traction or revenue. Usually, this is nothing more than a strategy by start-ups to AVOID competing with established products rather than creating an actually remarkable product of their own.
...and yes, I have many times heard about the people who are making a killing by selling some obscure little piece of software/product or service to an uber narrow market segment thereby facing nearly no competition. Not sure if that was Dan's strategy as well.
The office refused his pennies and said they wouldn't spend their entire week counting them and that he should pay in a different fashion. Well... apparently according to some law, if you refuse payment in legal tender, the person is not obliged to pay you...not sure if this is true or not but may be worth researching. You could see if your school wants to count all those pennies.
Discussing quality of passwords is only relevant in the context of a system that has no other weak points that can be easier/faster exploited than the passwords themselves.
And even then...key loggers, trojans, phishing, script injection etc...they can all capture passwords of arbitrary length and complexity...
I would be curious to see statistics around break-in where the root cause was actually hackers reverse engineering/guessing an unknown password vs obtained access using a password they obtained otherwise or simply bypassed any username/password mechanisms altogether. I have a feeling the latter two would comprise 99+%.
I have yet to encounter a manager (in the enterprise) who actually cared to take a closer look at the things mentioned in your above list. Managers promote those who make their lives easy and make them look good. They care alot more about whether your status report is up to date, if your time sheet is on time and if you are meeting deadlines than what your program structure is.
In fact, as long as it works and conforms to requirements, most managers don't care at all what your program actually looks like and it won't factor one bit into your yearly evaluation.
Granted, a poor program structure and organization may make you fail at any of the above mentioned points, which will lead to poor reviews, but the structure itself doesn't matter from my experience.
To me, as a technical architect and someone priding myself on my work...it does...but not necessarily to management.
Rather than just looking at the raw numbers (which these articles always love to do), I think the more relevant questions is, do or don't the "rich" deserve their wealth? If they deserve 85% of all wealth due to their involved in the economy, job creation etc...well, then they should have it.
I think few here in the HN community would argue against some entrepreneurial fellow HNer making a buzzillion dollars off of some cool and desirable product/service which instantaneously puts then into the 1st 20th percentile of the graph. Why? Because this person created enough value to earn that money....and maybe those other Americans in that top percentile did too.
First, go to the recruiter who can give you the best deal. That means, don't say yes to the first person who calls you. Tell them you'll get back to them and then check out the boards for whoever else is in the running. Apply to them all, talk to them all, and then decide which one you are the most comfortable dealing with. Even if the company isn't mentioned, it's fairly easy to compare requirements.
Second, know your price and be willing to walk away. The only reason you get screwed on rates is because you allow it. If you are not willing/able to walk away when your price isn't being met, then you have already lost. The competition for candidates is fierce so if you stand firm and you have the skills, you can often get the recruiter to submit you even if your price is above where the client is willing to go. Get your resume in front of the client and have them reconsider their price. If they still don't budge, walk away.
Third, they are a necessary evil since many jobs can't be accessed (or with great difficulty) without them. This is not because the headhunter makes it difficult, it's because the hiring company doesn't want to deal with the recruitment process and give headhunters an exclusive on the job.
Since trends are constantly changing and always towards something new and never before seen, there will simply never be a time when there is a bounty-full supply of shoe-in candidates.
American companies need to look for people who are fundamentally smart, able and willing to learn, are problem solvers and have reasoning skills and whom they can shape into the exact resource they need...and then know they can reshape them again when needed. I really believe this will lead to a far more qualified workforce at every company and be a source of renewed loyalty between employers and employees.
Consumerism has driven America into treating labor as any other store bought product which can be easily, quickly and cheaply acquired to fill a momentary need and discarded when trends change.
This is not a labor market problem, it's a problem of approach and mentality in staffing and HR.
Look at the really successful companies out there and you'll see they hire fundamentally smart people, everything else can be learned.
Being a techie in SF has been absolutely amazing. The startup community here is an incredible force. Meeting people is a no-brainer if you put yourself out there. I work as an independent consultant with clients located across the US so I can't speak to the job market in SF. After being here only 4 months, I am thinking it will be very difficult to leave when that day comes since the opportunities are just incredible.
I worked for a startup once where the founders had hired a CEO to manage things. They just stood by while the CEO ran the company into the ground even though it was in their power to step in at any moment. They chose not to have a confrontation over having a company. Don't be that owner.
Have a very serious conversation with your co-founder about how you feel and that you are on the brink of pulling out. Maybe that will make him listen to you, but have a very well laid out plan for what you want and how you want things to be, including any people you may want to replace.
Being unemployed can offer HUGE advantages in terms of being completely up to date on the latest and greatest, something most employed people simply don't have the time for.
You don't need a job to tech you the tools of the trade so make sure you walk in with those already in your back pocket.
There have been plenty of crafty people on HN who have built up a resume with experience by simply offering free services in order to prove they can do something. I would suggest you do the same at this point.
www.lawpivot.com
I have countless times seen job requirements demanding X+ years of some acronym when the technology has only been around for half of X.
Also, candidates are rejected by the people who interview them, each with a particular bias as to what they expect. Typically, a technical interviewer (i.e. fellow software engineer) will be heavily biased towards their own preferred technologies, philosophies or approaches. Anyone who doesn't share them with equal enthusiasm or depth of knowledge just isn't "skilled" enough.
Software people, and especially programmers have A LOT of ego, and it comes out especially strong when judging candidates.
I think startups probably do need an all star team to get off the ground and succeed. But once a company goes into operations mode, you need a mix of both stars and "average" programmers. The stars will probably tackle the new and untried while you also have a stable of people who don't mind doing the day to day boring maintenance bit without complaining too much.
First off, it was very cool to chat the other night at the night owls. Very much appreciated your thoughts on connecting to different APIs.
I do agree with the other reviewers that the purpose and uses for this product need to become more obvious. I would suggest including some brief illustrative use cases on the front page for people to start salivating over what cool things they can now do that they couldn't before. Having to read the FAQ via "What's Quirk" should not be the primary way visitors learn about your product.
Also, for the dramatic effect of getting your Quirk, why not actually generate it right on the front page with a subtext of "make this Quirk do...." with options for people to chose from? I think that would also help communicate the use of the product better.
Also, why can't I just paste a link (any link to anywhere) that I want my quirk to go to? You could make it a pass-through your site and probably find business models for that as well (I am making the assumption that the Quirk embeds the link back to your site specifically but could go anywhere).
"Link your social network accounts" makes me believe I will get a Quirk that takes people to my actual Facebook profile rather than a Quirk profile.
Smaller Things:
Once logged in, when I click you logo, it doesn't take me back to your front page as I would typically expect.
When I chose to log in via Facebook and then subsequently denied your oauth request, i just get an error page on your site.
http://www.meetup.com/Hackers-and-Founders/calendar/13712634...
I do agree with the basic premise that if an available solution does not meet expectations, the benefit of re-use does not always outweigh the inadequacies, thus supporting the business case of building it yourself.
HOWEVER...
...there are far too many organizations who think their needs are unique and different when they really aren't. I think that is a more common reason why companies re-invent the wheel and then post-factum realize their needs really weren't so special after all and could have bought off-the-shelf instead.
What cracks me up even more is, when a company realizes that an in house built system could be replaced with an off-the-shelf packet, then they have to weight their in-house maintenance costs against going out and buying an existing package. This quite frequently comes out cheaper over time, so right after they build their shiny new enterprise app, it's discontinued and replaced by a bought system.