386 karma · joined May 7, 2011
As one of Helidor's other posts mentioned, it needs to be mentioned that a flexible schedule/later "clock-in" time is acceptable as long as you get your work done if that's what an individual truly cares about. This all comes back to the position that I and most others I know hold, and that being that you pick your values that you won't budge on, make them known, and poke around until you find something that fits.
To your point of being forced to do something you don't want to do, having been in a company that "forced" me to work 60+ weeks on a regular basis and having almost no time to spend with my family drove me up the wall. I bounced out as soon as I found something better. That presented a very big challenge for all three of us in my family to the point where my kid wondered if I was going to be home in time to put her to bed some days. Hearing those kinds of statements from your kid really puts things into perspective and makes you see if what you are doing is really worth it.
Explain why 9am does not work for a 20-something. Yes, I am a family guy as well, but even when I was single, I was at work by 9am almost every day at the ripe old age of 21. If you said your reason was, "I don't like waking up before 9am," I'll buy that, but the position you state is an empty one at best without some sort of evidence.
EDIT: Bah, no WP7 app, but it's understandable since most of HN probably isn't using that OS.
Yeah, I'd pretty much say that the IQ test was pointless in this case and luckily that was the only company I had run into using it.
EDIT: Forgot to mention that the test also took 3 hours to go through and had no limit on the questions that you would get. There was no possible way you could finish every question on the test.
People think you can do it again... and again... and again as if it was something you could just conjure out of thin air. There are many papers written on this topic. I've been playing around with a few ways to achieve this more frequently, and it has worked to some degree, but it's not something I could rely on in the heat of battle.
This is probably a terrible explanation, but I'm giving it my best shot.
Point #1: Math is fun while you are learning it and figuring it out. After that, it isn't so much fun as it becomes exactly what it was meant to be: a tool. It's just useful at that point. "I know how to do X and it's useful in this case." To the point that there isn't a fun way to demonstrate it, I disagree. One of the best examples I can think of was when I took a science class and we were learning about velocity, vectors, and acceleration. The teacher had us build model rockets and launch them, guessing how high they would go based on calculations. That same teacher went to a different school and did the same thing, except on a bigger scale. All the students worked on one rocket with a goal to break the sound barrier. They put a few electronics in the rocket to measure acceleration and g-forces (IIRC). When the students calculated the altitude the rocket would reach, they were pretty close. Not terribly advanced, but advanced enough with actual application of the concept being learned. It wasn't entirely out of reach for the students to achieve, but a teacher needed to guide them there. The teacher needs to figure out how to present the information in an engaging way to draw students in. But, at the same time, the student needs to be willing to fish for the answer and occasionally accept the I-don't-know answer.
Point #2: While I understand the student's sentiment, I agree with your point. Unless a student realizes they could be FIRED over the fact that something is late at a real job, it won't sink in. It's a good thing to have deadlines, otherwise someone would be spending all their time on reddit/HN. A better approach would be to give the student an assignment that's a little tight on the schedule. That forces the student to concentrate on the material if they want to get a decent grade. I think it would be better if a student was kicked out of the class if they repeatedly turned things in late, and in a sense, be fired from the class.
Point #3: You don't need to learn the theory right away. There's no point in drowning a student in theory when they have nothing concrete to anchor it to. If I started talking about Optimization without giving a student an example of a slow program and a fast program that do they exact same thing with the only difference being optimization, they wouldn't have much of a reference point. If you look at a big program that's had execution analytics run against it and realize that a slightly less optimal solution is slowing the program down by a fact of 5, you then have a solid reference point to learn algorithms/data structures and optimization. You then understand the why behind needing to know something, rather than someone standing in front of a whiteboard saying, "Hey, this is important, you need to know this."
- Look at WEST 8TH ST. Zoom in as far as possible, then zoom out one click. That was the easiest for me to read because it was higher contrast and the letters naturally had more space in and around the letters.
- WASHINGTON SQ N is almost impossible for me to distinguish. All I could make out was WA...TON SO N at first. I couldn't tell that there was a Q in SQ and kept thinking it was an O.
- I really, really like the map styling.
Hopefully that helps you.
Another point a coworker made is that we are squeezing the inefficiency out of these systems. Models of business that worked well 10-50 years ago don't work nearly as well or at all now because there is technology in place that eliminates the need for some or all of the distribution methods in place that they are trying to protect.
There were plenty of companies (I'm guessing around 50%) that simply never responded back to me, even if I sent them an inquiry about where I stood in the interview process.
I think the worst one was a company that: - did an initial HR interview with me, then asked to me come back 3 weeks later. - sat me down for a 3 hour long "Skills Examination and Aptitude Test" (think SATs mixed with the ASVAB, "If you turn gear A, which direction will gear D turn" kind of stuff) - never called me in for an actual Technical Skills test - gave me an offer for a position that I didn't apply for, was not relevant to my skill set, was 15k lower than I expected for the position offered, and that I wasn't interested in.
Some of the companies I've talked to were dreadfully slow and got to the point that I simply didn't even remember talking to them when they finally responded. When they finally responded, I'd look up the last time they contacted me in a spreadsheet I kept and ask them why it took them X months to respond. The usual answers were, "we had so many applicants"/"The previous HR employee left"/"That position is no longer open but we wanted to consider you for another"/etc.
You are entirely correct. Dan's product does have competition, and maybe the other products do have better price points. We have talked about these other offerings before our lunch discussion. Other people have mentioned this point to Dan already.
However, this post was not about Dan's product specifically, but it was about what I learned from him while he and I were talking over lunch. I did reference what Dan was doing a lot in the post, I will agree, but you could apply these ideas to pretty much any project a person works on.
Definitely comes into play in good design. One of the biggest things I've found is that to constantly look at new ways to approach a problem. Don't just assume you've learned it all.
One thing I'd like to learn how to do better is to refactor better.
In my experience at a previous company, they upgraded every developer and QA engineer's workspace to have high-end hardware and dual 24" monitors (1920x1200, not the 1080p BS). Previously barely-missed deadlines were practically eliminated, better employee morale appeared, more innovative ideas started appearing, and various other things showed up.
All in all, this convinced me and I'm a firm believer in giving employees great tools and freedom to approach things in their own way. It shows that the company cares about you, and that goes a long way with employees and their performance backs that up.
People need money to live (ESPECIALLY after college), which usually entails getting a job, and an internship can be a good way to get your foot in the door (it's how I did it). It's common knowledge that it can be at least a year before a startup reaches ramen-profitable. There are multiple companies that the founders were doing other work while hashing out the idea for the startup.
So, again, how does your comment apply?