HNHacker News
TopNewBestAskShowJobs

sp4rki

1,384 karma · joined July 3, 2008

submissionscomments
sp4rki··on _Why Documentary at Rubyconf 2012, Denver
Why should we not at least respect him a litte? He did do a gazillion things for the community and made learning (I knew ruby already at the time, but his teaching methods and his excitement off all things Ruby made me revisit the language in a completely different way) quirkily fun.

He might have taken all his work down knowing that it would probably live on through source control and people at the time using his work and making it available for everyone no? Anyways, the fact is that he made a mark, and because of it I believe people (including me) respect him so much.

sp4rki··on _Why Documentary at Rubyconf 2012, Denver
I agree it's weird. I also read his intro to ruby guide. I don't idolize him, but I respect him quite a lot. I think he earned said respect and to a point maybe even earned being idolized, not necessarily because he wrote an intro to ruby, but because the way he did such task was incredibly engaging and fun.

I do have to accept that I also have an extremely weird sense of humor (which is based on my encyclopedic knowledge of trivial, useless, and completely irrelevant facts [...wait! I had something for this!] ), and therefore I can totally relate to his methods and tactics of expression.

I posted the story for a reason though. In a world where we're reading about startup this and startup that boilerplate news over and over again, it's a bit refreshing to stop for a minute and get a small insight into the mind of a person who did quite a bit for the "community", and maybe -just maybe - get inspired to find an equally engaging and fun way to communicate to others whatever it is we can contribute to the distribution of knowledge and the further advancement of people's careers in the world of software development.

Also: http://tryruby.org/

sp4rki··on Grunt.js
Not useful or common knowledge to you doesn't mean it's not useful or new for others. If you knew about it, and dislike it, what are you doing commenting here? If I had the same opinion I would have shrugged and told myself "Oh... grunt... again... Move along", not come in here to make a completely useless remark, which by the way obviously does not align with what the majority here thinks.
sp4rki··on Tomorrow Theme
I agree.

I like Tomorrow and everything, but I've got Solarized on my iTerm, Vim, etc all set up already and it's probably the only theme I've felt 99% confortable with and which didn't give me eye strain after 48 hour marathons. What's the benefit I'd get from switching? Being "new" doesn't cut it, is there some science or statistics that make this theme viable in place of Solarized? If not, then the title is misleading.

sp4rki··on Lobsters
I would also love an invite! Anyone care to patch me in?
sp4rki··on PG: The Art of Funding a Startup is now free on Amazon
I've been tempted to do just that: Convert all my Amazon kindle books into MOBI and get out of the "walled garden" as you put it. There was one thing stopping me though. I have an inherent need to support authors as much as I can since I not only wanted to be a writer when I was a kid, but I actually ended up writing a few short stories and a couple of novels. All unpublished off course since they where not mature (as in experience and style) enough. I fear that if I get out of the walled garden I'll end up buying a lot less books (and supporting authors less and less) because of how easy it is to get books online, and I don't necessarily mean pirating FYI.

So yeah, I installed Calibre and was amazed by the flexibility it gave me... and I uninstalled it an hour later because I realized that I couldn't support authors if it was that easy not to do so.

In any case this is great information, thanks for the walkthrough. maybe one day I'll go ahead with it and get out of Amazons lawn (get it get it? garden && lawn?)

sp4rki··on How to Get a Job as a Developer in Less Than Six Months
I agree completely. But I think that both subsets, the degree laden and the "no degrees allowed" crowd both apply the same labeling towards one another. Get's to a point where no one who's hiring for a worthwhile company cares about computer science degrees and cares more about exposure, references, and past experience. I think the industry is becoming more hostile towards both, no degree and degree types all the same. It's hostile towards anyone that hasn't proven they're worth their weight in gold either because of their github account or their past work experience. And that my friend a good thing.
sp4rki··on How to Get a Job as a Developer in Less Than Six Months
I don't think that's the case now... I wary of people with a bunch of certifications and college degrees when I'm hiring for my department. I tend to look more for the small details that let me know that the person is up to date and loves programming more than if they have been taught "classically" .

Interestingly enough, almost every "computer science engineer" with 11 page CV's I've interviewed have not been able to pass a basic test I get all possible recruits do. Be assured though, it's just a filter to get the people that just don't know enough, not an actual "test" per-se

sp4rki··on 4bit - Terminal Color Scheme Designer
Oh but I'm not color blind :)

Also solarized comes with various different "contrast versions" have you tried them all? By the way, what's your choice in color scheme being color blind and all?

sp4rki··on 4bit - Terminal Color Scheme Designer
Ohhh boy you brought back memories of Textmate for me! I used to use Monokai also. Great color scheme! Loved it until I found a need to have a bit less contrast in my code. For some reason I got so used to the contrast that I only saw stuff in the pink/fushia and my mind completely ignored the rest.
sp4rki··on Why passwords have never been weaker—and crackers have never been stronger
Being the second in command of a development team I made the decision to change ALL our authentication to bcrypt a week into the job overnight (luckily we where storing password encrypted in way I could retrieve all the passwords), had to hack into the database server though. The result was an angry customer service department, and the realization that our security was complete shit. I also ended up working with the IT guys to secure our networks. The real result is that now we don't get huge security meltdowns every couple of months. I got a bonus for the initiative... Oh and the customer service guys still hate me :D
sp4rki··on 4bit - Terminal Color Scheme Designer
Makes me kind of sad that I got used to the Solarized color scheme already (I use it in VIM, iTerm, Visual Studio etc... ), so I have no use for customizing my color schemes any further. I'd love to use this :(
sp4rki··on The Two Week Problem
I agree that sometimes a new job might bring into light a toolset you;ve never used. I've never taken more than a day or two to get everything up to speed though. Interestingly enough, after being a unix guy for more than 10 years, my latest job required me to use visual studio. My first commit was three days after I started. This days I even have a file with all my VS configuration.

You also gave a perfect example of the only case I explicitly said you shouldn't point the finger to "new developers", which is when IT - or even the senior developers - are at fault for having a crappy development environment.

sp4rki··on The Two Week Problem
Well then use your own repo, or bring a usb, have it veted by IT and get your configs on your dev machine.
sp4rki··on The Two Week Problem
I think this is probably a problem more with new developers vs seasoned developers. I've noticed that configurations woes plague people who haven't got to a point where they have already configured their environments to their liking tens of times. i can get a machine configured for development use in a few hours and be productive the next day. Why? Because I have a repo of all my latest dotfiles including my vim plugins and configs. I also have a list of software I need to download the moment I use a new machine in my 1Password notes. Lastly I have another note with all the stuff I usually change in OSX and Linux. I've even been thinking lately about make it even more streamlined by having scripts actually do all my work.

To get up to speed with my developing environment, I just need to sync a couple of dropbox folders on my dev machine, checkout my repos, or bring a usb (if not allowed to dropbox sync my stuff, in which case I'd really consider getting a job where I'm not limited by stupid policies that make little sense for developers) with my latest configs. Lastly I might spend a day configuring the companies environment architecture (svn I'm looking at you), but even in the worst situations this things are generally trivial.

For a developer, his machine should be free to configure to his liking as long as security constraints are taken into account. If the developer can't be up and running with his environment in a few days, he's either not experienced enough or the IT department utterly sucks. Generally, it's the first option.

sp4rki··on The Ugly Side of Learning to Code
That really depends on what type of programming you're doing and the platform you're developing on top of. If you're doing a crud app in rails, I'd agree with you math itself is pretty much useless after knowing the core operations (add, subtract, etc...). But the moment you're dealing with lower lever programing, creating or implementing algorithms, managing memory, etc... understanding more advanced mathematical concepts starts to shine as a necessity more than an option plus. Actually, if you're developing a rails application for the financial or analytics sector you're most definitely benefit from knowing advanced math and having done a course or two on statistics.

Let's be honest, if you're creating an application to improve or help accounting of a business, you need to know accounting. If you're creating an application for banking and finances companies, you need to know financial math. If you want to make an app that converts a business' Excel data into complex charts you need to at least understand statistics and more complex math than the 15 year old learns in school. Don't even get me started on a program that draws graphics programmatically and the need for some trigonometry in there.

Lastly, though I do a lot of backend and sys admin stuff because of the nature of my speciality at work, I spend half my time doing frontend programming and css (thank god for sass), and if I didn't have knowledge of algebra and trig I would take at least half as much time to do what I do. I know (and work with) a bunch of great programmers, but I'm still the guy people go to at work for mathematical advise when al algorithm is not behaving as it should and it mathematically complex.

I'm not trying to argue with your point though, most of the time you don't need those advanced mathematical concepts, and the important part of learning math is the reasoning aspect. i completely agree with that. Nevertheless I've found that advanced concepts can speed development and in some cases having that knowledge can make or break a project.

sp4rki··on Programming Languages Have Social Mores Not Idioms
Actually I agree that new programmers are better of starting with .each, and also that experienced ones can also benefit from an overload of .each to change the patterns they are used to. I commented on why I disagree with Zed's decision that each should be taught later before even getting to this "trollish" thread.

Regarding your second and third bullet points: As I've tried to explain before, there is a tremendous difference between someone reading "The Ruby Programming Language" and "The Ruby Way" trying to "learn" the Ruby programming language, and a person who goes from tutorial, to example, to tutorial, to built product. I can certainly relate to the latter since I started learning C and even a little Asm (thank you SoftIce) by myself when I was 12 thanks to a small stint in a cracking group. These days, though, after programming for around 17 years, when I want to use a new programming language I read on it's syntax, it's methodology, it's patterns... Let's do the analogy thing here: If you want to "learn" multiplication as a child, you have two options. Memorize the multiplication tables, since it's improbable that you'll need anything higher, or actually learn the mechanics of multiplication and how to carry numbers up to the next order of magnitude. There are two completely different monsters. In one you learn what you need to do to create something specific. In the other you learn everything there is to learn about a topic to further your understanding of a topic. Learning the how and the why are two completely different things that get emphasized depending on you needs. My point here is that we're trying to discuss the best methodology for the teaching of a language. In a book. Generally meant to leave students with a complete understanding of the subject at matter.

A small aside, I didn't mean ruby blocks on that last section, I just meant block in the general sense. In any case, I totally agree on the last line you typed. And that's what I've been trying to get the OP to understand. I agree to teach each first because of a plethora of reasons I've already discussed here, but I don't agree Zed is a "troll" because he thinks the explanation of core concepts in his book should be more linear.

sp4rki··on Programming Languages Have Social Mores Not Idioms
Understanding how to drive vs building a car is the same thing as understanding how to use a program vs building the program. Once again the point is that if you want to learn how to program in a specific language, you need to understand it's concepts and patterns. It's akin to the fact that if you want to learn how to build a car, you need to understand it's mechanics. You can easily take whatever you find in the internet and build a program. Or you could tweak an example to do something else without another care in the world. Guess what? You still don't understand what's happening or why, and because of that the end product will most probably be defective in some way. You still don't know what the point is, you only know that it works. That's OK if you need a quick solution for a small problem, but it's not when your goal in itself is to learn how to program (in Ruby)...

Go ahead and read Zed's article again, only this time do so slowly and with care. Come back and realize two very important things you seem to be missing:

A) This is Zed's opinion about TEACHING a programming language. TEACHING being the keyword. If you want to learn a programming language, you inherently need to understand it. As a small aside, he did write "Learn Python The Hard Way" which was pretty much a success, but don't believe me... he's probably a troll as you say.

B) The discussion is basically that a form of writing a specific block of code is easier to explain than another, although the latter is more widely used and considered the correct. Readability, though important, has little to do with choosing the correct construct to teach as to provide a good balance of the time and effort you need to put into learning.

You want to keep going with the analogies? You shouldn't drive a manual transmission car if you've only driven automatics, the same way you shouldn't deploy code to your clients that you've figured out will give you the results you want when you've never understood what the program is doing on the first place because you made assumptions when you started.

sp4rki··on Programming Languages Have Social Mores Not Idioms
For starters, you do realize that the author/troll of the article is Zed Shaw right?

The fact that you can read a piece of code doesn't mean that you understand it. The whole point of teaching how to program is to actually get the student to learn what is actually going on, not just get them to a point where they can give a half assed explanation that really doesn't teach a thing. Repeating the line of code with extra words to convey meaning most certainly does not make it a valid explanation.

And then you come along with a list of "responses" to the concepts outlined in the article, out of which you don't even actually understand half of, and completely destroy your initial argument because of it. You complain that Zed is a troll because you can actually read the code easily, when the whole topic of his is actually wether you can understand it. It's a completely different game. You basically just proved Zed right. The problem with teaching .each first according to Zed is that since you don't understand even half of what is going on, you just do things blindly because you've grown to predict the behavior you expect from a specific piece of code.

For dessert I'm gonna "troll" a little bit. 1) If I should know variables, arrays, function calls, blocks passed to function calls (which includes an arbitrary comment about BASIC and goto statements), and scope, before I start coding then how the hell am I supposed to learn those very basic concepts? I mean according to you I shouldn't be coding right? 2) If you really don't grasp the concepts you say you don't understand in the list, you probably don't program for a living and/or have not had to actually teach any programming concepts besides the very basics. If this is the case, I'd argue that you still have a long way to go before actually having the experience to compare both "teaching orders" being compared here. 3) You give me the impression of a guy that has only done a bunch of jQuery and perhaps a Rails tutorial or two... AMIRITE?

I'm sorry if this comes off like a lengthy angry diatribe (rest assured it's not my intention), but you tried to sound knowledgeable and ended up putting your own foot in your mouth. My mother once told me to only open my mouth if I know what I'm talking about. That my friend is my advice for you.

sp4rki··on Programming Languages Have Social Mores Not Idioms
I'd argue that using .each is a better choice in both of the most common cases of people wanting to learn ruby. The novice who's learning his first language will probably benefit by being taught early what it's considered the correct way to do a task. A novice can learn other "styles" later, but as a teacher you want to plant the seed in the students brain that .each is the shiznitz. In contrast an experienced programmer will probably come with for loops deeply lodged in his brain. Therefore it's also beneficial to challenge that prelearned behavior to establish the use of patters that are considered "more correct".

A novice needs to learn the most practical and correct way to do things. An experienced developer needs to learn to transpose his current knowledge to a new syntax. Both benefit from being taught the most common or correct syntaxes and patterns.

sp4rki··on How Instacart (YC S12) Hacked YC
I'm guessing you missed the smily face at the end. But even if he was dead drop serious, social reality is that "No" generally means "You're gonna need to try a little harder" this days. "No, I really don't have any interest in getting to know you as you're not my type" is a total negative, but a regular "Sorry no" with a smirk or small smile, is generally females being hard to get. Besides, I really think that "A NO is not really a NO" in HN is most probably not a Julian Assange type of rethoric, but a "I'm gonna try to win the girl over unless she really tells me she's not interested, even if she said NO before while at the same time licking her lips seductively and winking over 9000 times at me...". Being very politically and socially correct this days is really an obstacle while meeting new people or trying to express your opinion. I say keep it fun but courteous, not safe and conservative.
sp4rki··on At what point can I say I’ve “learned” a language?
I agree. You can say you "learned" a language when you can solve problems with it (because you've already "learned" programming as a whole) and you can actually think in the language (and it's specific features) to the point that further instruction on said language is not really "learning", but more akin to continuous mastery.
sp4rki··on Ben Horowitz: A Good Place to Work
I think people are not getting the point of the parable inherent in this article if the only things that come out of reading the blog post are "Ohh 12 to 16 hours of work" or "I would quit because I got threatened".

The focus should not be in the way the situation was handled, but in the priorities displayed by the author. Could he have handled the situation better than to voice a harsh requirement which if not met would result in termination? The answer is obviously a huge "YES". Now take into account that the administrative team have been told that one if their main objectives is not to be "classical" bossy managers, but to be the main conduit of incentives and communication between the company and it's employees to ensure the productiveness and happiness of the cogs that move the company forward.

This is not about reprimanding a manager because he did not turn a report on time - which by the way should be handled by asking the reason and though process of the manager's decision to use time for something else he deems more important. This is about a manager not being able to fulfill one of the KEY objectives stablished by the company's head honcho. If you're always trying to nicely get people to do what you say and it doesn't work, sometimes you have to resort to drastic measures.

In this story, both Tim and Steve failed to accomplish a goal that had long been stablished to have a high priority. It's akin to a sales person not selling, or to a programmer not doing his programming quota. There is something wrong with the machine, and one cog not working correctly can bring said machine down to the ground. I think that he should have asked why things aren't getting done first before resorting to drastic monologues, but at the end of the day drastic monologues are sometimes the only way to push, incentive, or realign a rogue "cog". At the very list I'd prefer to hear "You're not doing your job correctly because of A, B, and C. Either you fix it or your out!" than "You're just not working out for the company, and no I wont tell you why... Oh and I'm replacing you so pack your things..."

sp4rki··on Ben Horowitz: A Good Place to Work
He never said it (working 12~16 hours) was expected of his employees, but it is most probable that this is part of the startup culture "thing". I work for a big tech company, but being the second in command, I've worked with my boss to establish a culture that even though it has a lot of the startup usual hardcore-ness, is also full of benefits. Here I am, working on a Saturday at 6:30 pm... I've done pretty much a 66 hour work week this week. I've done so because I care enough about the company and our products to want (this here being the keyword) to finish a series of tasks (some of which are improvements I've myself tasked my person with, not bug tickets or feature requests) I deem needed for the continuous improvement of the software. I've also had weeks where I spent around 20 hours (2 days) helping out IT to solve some tricky architecture + linux challenges the company was having (my role as a application UX and frontend wizard, doesn't mean I'm not also the "I love to create algorithms for our backend" and "local linux mastermind" roles) - and then left on a trip to camp until the next week.

This time I took off was not discounted from my pay, frowned upon, or taken out of official vacation time. It was just the company telling me that they appreciate all the effort I put in and that they respect my decision making regarding how I spend my time on the company clock, be it working unpaid overtime, or taking a few days to decompress. For me that is the real good company startup culture. The company gives me the freedom to stay late and to leave early, gives me the tools I need to be productive and doesn't force me into preset managerial roles that don't really do anything to increase productivity or facilitate increased code throughput, and gives me the trust that I'm going to achieve what my responsibilities require however I see fit.

Am I a workaholic? Not a chance. I once worked almost 50 hours straight, not because I "want to work", but because I had a challenge I wanted to solve. I solved it and I went home to sleep and took a personal day (once again not unpaid or taken out of any "special time") after that. I'm not the usual geek slash programmer. I enjoy going to the gym and having one too many beers with my friends. I enjoy bar hopping and pickup up girls at clubs. I also enjoy coding, and if I weren't spending 4 to 6 extra hours at work writing code, I'd be doing it at home.

sp4rki··on $200 for a Fake Security System
For some time when I lived with my family houses in my block where getting robbed. The first time mine got hit I ran after the kid (probably not even 18) with a knife. Houses all around where getting entered and things where stolen... not mine ever again. Then one day there was a shooting involving a neighbor and he got one of the thieves. Years later the neighborhood could not be any safer.

My conclusion? The best security system is a bunch of crazy ass homeowners thieves are afraid of. I guess there's a correlation somewhere with fake security systems.

sp4rki··on Restaurant offers a 5% discount if you eat without your phone on the table
I'd argue that even though I might value your time and inherent effort of meeting me somewhere, I also would also establish that there are things more important than anyone's company and small talk over dinner. I would feel like a total jackass if I complain (even to myself, without voicing my distaste verbally/publicly) about you taking a call or message, and then you telling me that you have to leave because your father is in the hospital.

Sure I agree it's distasteful to answer a random sms while we're having a beer, and I would never do such a thing - but it's also very distasteful to voice concerns/annoyance about the value of any current interaction versus whatever inherent need a person has to be reachable for communication.

If you tell me that a I'm a jerk for answering a random call and interrupting for 5 minutes while talking to my girlfriend about trivial or banal stuff, I would totally agree. But that kind of sentiment should generally be saved for when you realize someone is being a jerk, not to immediately label a person for having his phone reachable or before an explanation of the reason for taking a call or message.

sp4rki··on Restaurant offers a 5% discount if you eat without your phone on the table
I agree with huggyface. The parent post was ridden with angry sentiments by the original poster. In my case, I consider good manners towards all the patrons to keep your phone in silence/vibrate in a restaurant/movie theater/bar because it might impact the ambient slash "moment" of other people that surround you. That doesn't mean I'm not taking a call if I deem it important, and depending on the place I might go outside to take said call. I might even need to keep my phone on the table to actually notice the call because of the noise inherent on some types of businesses.

Browsing Facebook while having dinner with someone is very offensive, I agree. It is also offensive to get "angry" because I took a call from my neighbor telling me that my grandma fell on the stairs, my work because the servers imploded and we're loosing thousands of dollars a minute, or my brother calling to tell me his girlfriend said yes to his marriage proposal.

My family, livelihood, and friends are all going to be more important to me than someone's arbitrary definition of table/movie-theater manners. I'll take steps to minimize the amount of inconvenience caused by having to be reachable during such events, but I will not apologize (actually I will as a courtesy, apples to oranges I guess) to having to interrupt whatever small talk I'm having because I got a call I deem more important.

It's your prerogative to not go out with people like me I suppose, but guess what, it would be mine to not go out with people that believe they're so much more important than other people's needs and wants.

sp4rki··on Vim and Vi Tips: Essential Vim and Vi Editor Skills, free on Amazon today only
For me the mouse is never quicker. I think that over time your brain kind of memorizes the number of lines (rows) and characters (columns) available in your screen and it certainly gets to a point where you don't really think about the science behind motions and you end up just using motions defined through past experiences. I amaze myself (and my coworkers) when I apply a seemingly random number to a motion and I end up exactly where I wanted to be. Last time a coworker asked me if I'm a math freak and I did the calculations in my head when doing a complex motion in a second, and even though I answer that I am (jokingly), I know that it's actually just a combination of muscle memory and past memories.

In any case, even though I don't agree with the school that says that to learn vi/vim you should forgo arrow keys and non vim (cmd + s to save, command + left arrow to go the left of the line, etc) key combinations, I think that a major point of inflection while learning the editor is choosing a trick/combination/command that you want to learn because it will increase your productivity and keep forcing it, even if it means not using the arrow keys or other combinations you're not used to, until it becomes second nature. And then do the next one and so on.

sp4rki··on Ruby Frameworks? Which one? Bye bye Rails.
I remember using Datamapper with Sinatra to develop a pretty basic system for some weird user registration needs of a company offering medical assistance in the way of air ambulances in 2010. I don't really know if it's still supported since I've been doing .Net stuff since then... but I can definitely tell you it WAS supported two years ago, and I seriously doubt that they don't now.
sp4rki··on Ask HN: Best book you read in 2011
And in a similar vein, I'd recommend both Practical Programming and 5/3/1. The first is great to get a more thorough understanding on what is learned on SS and help's you understand how to modify your routines for maximum gains. 5/3/1 Has in my opinion been one of the best plans for the moment you stall on SS and need something more advanced. This stuff builds not only your body, but your strength and does heaps for your confidence which I believe is as important.
← PreviousPage 4 of 19Next →