This looks great. Going to play with this later.
245 karma · joined April 13, 2010
This looks great. Going to play with this later.
I like interviews to be like secret ballots:
* write down what you think about the person without any external influence
* then share the information with the other people who interviewed the same person
You are right on this - bias can interfere with decision making. A single gatekeeper who makes the wrong decision could be turning away someone fantastic.
The hardest thing is saying no to someone you know is great, or is going to be great. It isn't personal - it might be that one of the candidates had 5 more years experience on something that we were really looking for. In this case, if I am working with a recruiter, I always let them know how great the candidate was.
I try not to judge him too much on this, but it colors my opinion of his opinions a bit - what musician hates jazz? Then again, I am not a fan of Shellac or his other music, so I am probably missing something. In 10 years I might be telling people how wonderful Shellac is, and it might just click for me - that is the wonderful thing about art.
I wish that there was a world where musicians could make great music without having to tour and make money. Some music doesn't need to be structured to be played live.
Edited for clarity and I was too harsh.
I wish that in the languages I have worked on that I could just ignore precedence and use parens, but operator precedence is expected.
They are all separate parts, and you can do them in any order you want.
I like to think of the language as two parts - syntax and features. How do I want the language to look and what features do I want the language to have? The parser and lexer handle the syntax, and the AST handles the features.
This way, I can play around with the syntax of the language a little later.
I would start with a really simple language:
- add expressions, proper infix support for arithmetic
- variables
- if / else / else if
- scoping / functions
- loops if you don't want to just use recursion
then, you can get more advanced:
- lambda expressions / first class functions / closures
- namespaces or types
- macros. if you can make nice looking lisp-style macros for an infix language i would love you
write it as an interpreter, add an llvm backend.
It should be fun. do a little at a time.
And then he drew a dial from his poke,
And, looking on it with lack-lustre eye,
Says very wisely, 'It is ten o'clock:
Thus we may see,' quoth he, 'how the world wags:
'Tis but an hour ago since it was nine,
And after one hour more 'twill be eleven;
And so, from hour to hour, we ripe and ripe,
And then, from hour to hour, we rot and rot;
And thereby hangs a tale.'
Edit: added Act II, Scene VII from As You Like It for context.This doesn't include paper architects, which are pretty much salespeople.
I would like to hear other people's thoughts on this - this is the way that I have always handled projects.
Cast iron is a lot less maintenance than people think. I cook food too hot for Teflon, scrape the crap out if other pans, and like to throw things in the oven. I also use a metal spatula for everything. I pretty much do all of the things that these sites say not to, and never have problems.
Using cast iron is simple. Take a pan, throw in some oil, cook, clean, wipe down with some oil. I grew up using nothing but cast iron skillets and all of this talk about how only a perfect organic oil combined with a special oven can create a decent seasoning is bs. I use vegetable oil and they work fine. Also, my pans have a sandy surface and they work fine. I didn't buy mine at an estate sale, but at a store years ago and they work fine.
I fry food in mine, stick it them the oven to bake, make eggs, steaks, bacon, vegetables. I pretty much cook everything on cast iron because it is easy to take care of and lasts forever. People turn this into something it isn't.
I also grew up making lots of bbq in Texas. People do the same thing with bbq - they spend so much time working on perfecting their tools that they forget to cook the food.
What other texts do you recommend?
East Texas is very different from the rest of Texas. The accent, food, culture are all much more stereotypically southern than north, west, central, or south Texas. Even the BBQ is different - you put sauce on everything.
That being said, my comment offers no real information. I just thought that it would be fun to post.
Isn't there an actual real-life game where someone is sent from person to person to get help, eventually landing back at the first person?
My mom had once told me that she had a bad dream where someone grabbed her, and she bit the person's hand and it was like biting through dough. One night, during a dream, I remembered this and bit the area between my thumb and my index finger and there was no feeling.
Also, food has no taste when I am dreaming. It doesn't even really have texture.
The early rap career was kind of cringe-worthy, but he also lived a good deal of his life in public. I bet a lot of people would be in the same boat if they had billionaire fathers who supported their decisions. I found his father's support sweet.
When I am dreaming I have to check often that I am not actually awake, so I have a trick I use to make sure that I am dreaming. I know, it sounds a lot like Inception.
A little more - I had night terrors up until I was 12. I would walk though my house in a frantic dream state, sometimes seeing things that weren't there on top of things that were. Maybe the lucid dreaming and early night terrors were connected.
I am biased towards Python and Ruby. I think that they are nice looking languages.
Different tools for different jobs. Next time I am on a JS project and I want to model data, I will probably use CS again.
Worth watching. I have never seen anything like it.
It is like Wikipedia - click on an artist, then a related artist, then an artist related to that ... Great for road trips and long coding sessions. I can get a sampling of a little bit of music history without having to go to a record store and search through bins of records. Don't get me wrong - the record store was great, but this is better.
I remember a few months in when it really sunk in that I was actually working out of my home. My house was my office and my office was my house, and everywhere I went I could not get away from work. I had a sudden feeling that the walls were closing in. Lucky for me that went away, and I find that I get more done and am able to be more focused than I was in an office.
A few pointers to those starting to work at home:
1. If you are like me and tend towards being a work-a-holic, working from home can mean turning your normal 8-10 hour workday into a 24-hour workday. Set limits and work by them get...
2. ... a home office where you do your work. Make sure it has a door which closes and treat it like an office. You don't have to work in it 100% of the time, but it helps me to have a place I can leave my work. My office is great - I have a big desk, a couch, music, big windows. It is the office that I would like to work in.
3. Get out of the house. Not to work, but to play. Get around people. It is going to happen - you are going to have a crazy project and find yourself locked in your room for a few days. This is pretty normal, even in a normal office. It can easily become your life since there is no one telling you to go home.
The perks of working from home are great - no commute means more family time, and the you get a personal bathroom and kitchen. If you need to take a 20 minute nap no one is stopping you, and going for a jog is as simple as opening the door and taking off.
I translated excel into a javascript data structure, translating the formulas into javascript functions. The data structure could be saved to json, and them reloaded back into javascript. The cool thing is that changing a value (a2 = 3) automatically updates dependent values in the rest of the data structure. The data structure can be referenced much like the spreadsheet - it is a tree with branches for pages, rows, columns. There is a simple faster csv like API that makes it easy to go page by page, row by row. Also, cells can be looked up explicitly.
The code is proprietary, which is a shame. It was written as a library to quickly reverse engineer large, complex xlsx files. The trick in making it work is just having the right data structure.
Sorry if I am rambling or any misspellings. I am very sick right now, drowsy from medication, and trying to type thus on my phone.