I don't agree with the premise that flow is a good idea (it's probably a pretty bad idea actually).

IMs are bad because they usually force context switches (as do most interruptions). But IMs are easier to ignore than other context switch forcers like phone calls (unless you can just unplug the phone).

Isn't internet service notoriously horrible in the US? Specifically in the Valley?
Give me standard Japanese connections any day of the week. *drool*

I'm the same. For everything nonfiction I need paper. I usually marker stuff in 3 colors and have a bunch of paperclips holding together interesting sections and the like. I flip through, cross read and browse to parts. UI isn't there for anything e-book/PDF in that regard.
Huge advantage of digital is searchability though. For academic papers I need everything digital (makes it supereasy to autocite and autobuild references...which you'll appreciate tremendously the first time you have to change citation style midpaper when you write one) and I search in them and the database (Zotero) a lot...but I still print and marker the highlights. 3 pass reading is a lot harder in digital.

.

[While we're at it...I randomly upgraded to the latest OSX...and Outlook just ring of deaths. I think that was end of last week, still no fix. Lol Apple+Microsoft. I'm sure some universities/design studios/companies are going ape**** over this. Confirmed as a bug with status "working on it". Closed source software is the nutlow.]

You think flow is a bad idea?

yeah I'm not sure what's such a bad idea about getting things done faster.

If you work on hard problems flow is counterproductive. It's a "trance" of sorts. "Losing sense of time" is kind of baked into the philosophy of flow.
Taking scheduled short breaks is superior in many instances (typical setups of 25-5-25).

There was a pretty good talk (or maybe paper) on it but I don't remember by whom. Probably Hickey.

Man, I love working in flow. What's not to like about that state? Time flies by, you get so much done and you feel so satisfied afterwards.

For me, if the problem is hard I won't get into flow. Flow happens when you get good at something and it comes natural. Like if you are learning how to solve a math problem. At first it is hard but once you understand the method for that particular type of problem you can do it in flow.

The twenty five minute thing is related to the tomato timer movement, whatever it's called, yes?

I guess we'll have to disagree then Wolfram. I think flow leads to turning off the inner critic and sceptic in exchange for feeling good about what you do. At least that has been my overall result.

The one positive thing is that flow is fairly addicting which leads to a great motivation to schedule uninterrupted time...which I'd argue is the biggest benefit. Like I said I think there's better (more deliberate) ways of using that uninterrupted time once you've arranged it.

I think flow can be great and being able to "get into it" is useful. Specifically in the realm of programming I think it can be rather dangerous (subconsciously taking the easy approaches that let churn on).
I think it can be good as a starter though. Yay-yay flow boom...nice codebase to start from instead of still procrastinating and thinking about how to start.
I flow around regularly when doing base literature research. Once I have a good stock that is decently tagged I have to hit the breaks hard though.
[So maybe we don't disagree after, seems like you like flow for "routine" activities as well. I just tihnk it's somewhat dangerous to treat programming as routine work.]

Edit: Yes, pomodoro but generally it's good for the brain to take scheduled, regular breaks and drink water. Get up, walk around. Brain activity soars.

Yep.

I spend much more time out of flow than in it. I haven't really read any literature on what you're supposed to do, maybe people are trying to force it and that is probably not very productive.

Someone likes me after all.

Won't say the name of the place, but some of you know about it. You'd be shocked.

Congrats maybe?

awesome dave!

what stack are you using and what will you be doing?

Well, yes, I do have to get there on time and survive a few weeks.

I'll be doing the database work, using PostgreSQL, woohoo!

The stack is Linux, some Lisp, and other fun languages.

Actually the first job I've applied to out here that I really feel like I want. I also liked the people who interviewed me, which is another fine bonus.

Good stuff!

Hell yea daveT!! Stoked for you!

Sounds like a trifecta. Congrats!

I really did think a lot about the whole cultural fit thing. There was a few interviews where I could just sense I wouldn't like the people at all, and I'm starting to feel like it is super important after all.

I'm still trying to emotionally recover from my last job, and that really started to hit home with me the more I've been interviewing out here, and it wasn't until I started to interview and tried to describe my last job (positive or negative) that I understood how deeply it affected me. It turns out that it may be harder to find a cohesive group of people than I thought, but it is worth the effort to try.

Where I have been working, I noticed people talked to each other and appeared to look forward to working there. "Good morning" really meant "I'm happy to see you today," not "**** you and **** this job." I never seen this before, and that really hit home.

I was interviewed by the group of people I would be working with, and they all seemed to get along well. I could only feel deep respect between them all and I didn't sense any toxicity oozing through the cracks. These are people I'd sense would have a beer together, and that sounds important for some reason.

: thumb:

For whoever was wondering about taking on an internship despite feeling like he has no qualifications: do it now and don't wait. The worst feedback I ever received was being told I'd be too bored doing some work despite having no experience. Entry level or internships, as far as I'm gathering, means they want to mold you to what they want, and of course, you are more than qualified to do what they want. You just don't know it.

Congrats Dave!

That may have been me, if no one else claims it.

Been going through Head First Design Patterns and Cracking the Coding Interview, mostly because I don't want to completely fail any interview I do, and also because I think they'll make me a better programmer.

This bit was posted here before, but I had a follow-up, semi-related to dave's post:



How much of this stuff is an intern/apprentice-level applicant expected to know or have mastery of? In CtCI I think this was the baseline for people with experience to get jobs.

For example, one apprentice job I'm looking at has this for the requirement:

I don't know what qualifies as 'proficient'.

My apologies if I've asked this before, but I feel like I'll be applying sooner than later and while I wouldn't mind being semi-overqualified, I definitely don't want to go in and not know at least enough basics to be helpful and contribute.

Hopefully this will serve as my lack-of-confidence rant for this quarter.

Congrats Dave!

Can you write fizzbuzz? Bam proficient.

Roonil Wazlib,

Just apply and see what happens. It's hard to know what an employer wants.

We're hiring three coops for this spring. Pay is like mid-twenties per hour. PM me if you want to apply Roonil.

We are also looking to bring on several more experienced developers if anyone is looking for something new.

Rochester was just ranked #1 Best Place to Live for 2016 by livability.com: http://www.livability.com/best-place...s-to-live/2016