HNHacker News
TopNewBestAskShowJobs

gyepi

221 karma · joined May 14, 2010

self-hn-contact@gyepi.com

http://gyepi.com/pubkey.asc

https://github.com/gyepisam

submissionscomments
gyepi··on “Well, He’s Not Going to Get Very Far”
> Your "A-game" is your best, not the best in the world....

Hmm, that doesn't jibe with the idea of not rewarding mere effort, which is how I read it as well; we reward results, and "punish" lack of results. This isn't necessarily a bad thing; applicants know what they are getting into and can self select out if they don't feel up to it.

gyepi··on RTFC is the New RTFM
>I think the next time I interview a candidate I will ask them what major open-source libraries they use. Then I will ask them what they think of the quality of the source code

Sometimes, it is eye opening to read the source code to some popular libraries/frameworks and discover how badly the code is structured. Some definitely belie the notion that code is written for humans.

gyepi··on RTFC is the New RTFM
I have noticed the increasing paucity of documentation in many open source projects. In the past, this would annoy me when I had to context switch from a perfectly good flow state to a documentation reading state. However, I realized that I was doing it wrong; it meant that I was not spending enough time analyzing the code I was about to "adopt" and depend on for my project. Now, I read the documentation and source code for every open source program before I choose to use it. I also find correlations between the quality of the code and the documentation; good quality code sometimes lacks documentation but poor quality code rarely has good documentation.

Reading the code also provides the opportunity for learning beyond the documentation; there's a wealth of really good code out there just waiting to be read.

gyepi··on Process Managers: The Good, the Bad, and the Ugly
For years, I used daemontools (it still runs a bunch of machines) then moved to runit, which follows the same philosophy. Both are excellent tools and have worked extremely well under many different circumstances. Simple tools that do one thing extremely well. Every managed service requires a short, 1 to 3 line, script to actually start the target program, which may, initially, seem off-putting, but actually provides the often missing opportunity to easily customize the program environment.

BTW, runit also comes with svlogd and chpst, both of which have frequently proved invaluable. The latter is useful in its own right.

Most of the tools discussed either lack flexibility, try to do too much, or simply don't offer any benefits over runit and company.

gyepi··on Why women should embrace a ‘good enough’ life
Much of the advice in here is really good and actually applies to men too. It seems obvious to point out that a multidimensional life is richer, but it took me a long time to find out. Family life and personal development are no less important than a career, but the latter takes up, almost by default, most of our critical cycles. Creating the proper balance requires that we step back and evaluate how to spend our lives rather than merely following the well worn patterns. I doubt that anybody wishes, upon dying, that they had spent more time at the office.
gyepi··on Ack 2.0 has been released
Ack is wonderful example of tool use evolution. Before ack, I used grep to find stuff, but each use would frequently require additional options to exclude certain types of files, then coupled with a pipe to filter other stuff, etc, etc. After ack, everything is much simpler; just specify what you want. It has replaced most of my grep invocations. Honestly, if you work on the command line and use grep, you owe it to yourself to try ack. You (probably) won't look back.
gyepi··on Postgres 9.3 feature highlight: JSON operators
Hmm, I'd have to disagree with you on that. It is true that JSON processing could reduce raw scalalability in the sense that a query that uses JSON may be slower than one without. However, having JSON processing in the database simplifies quite a bit. For instance, imagine an app that processes and emits JSON and also uses a normalized database. This functionality now makes it possible to move some of the JSON processing closer to the database. In some cases, this may not be the best idea, and in others, it's a win. As with many things, having the choice is not the problem; it's how one chooses, given the choice. I can see the benefits of XML in the database, but I can also see how it could be misused. The key, as always, is to apply judicious thought to the problem.
gyepi··on Back of the Envelope Calculations [pdf]
Jon Bentley has a chapter on this topic in the performance section of Programming Pearls. This is a very useful skill for reasoning about problem boundaries. All too often, our performance estimates are on the order of "fast" and "crazy fast". Worse yet, we build systems without understanding how they will scale under load.
gyepi··on Balancer Battle – Load testing HAproxy, Nginx and HTTP-Proxy's WebSocket support
> nginx and haproxy were really close, it's almost not significant enough to say that one is faster or better then the other. But if you look at it from an operations stand point. It's easier to deploy and manage a single nginx server instead of stud and haproxy

From an operations standpoint, haproxy has other features (failover, cli management, clustering) that actually makes it a much better load balancer. I usually install all three haproxy, stud, nginx because they are each very good in their specific niche. As for the simplicity of installation, that can be handled with a configuration manager.

gyepi··on Don't Copy-Paste from Website to Terminal
FWIW, I use shell mode in emacs most of the time and it happily accepts, and buffers, multiline commands until you hit enter, unlike the terminal.
gyepi··on Don't Copy-Paste from Website to Terminal
Actually, you're copying more than a git clone command. That's the point of the posting. Look at the source or paste into a text editor to see it.
gyepi··on Talk about the problem, not the solution
Over the years, I constantly remind my manager, clients, an colleagues to bring me in much sooner than they think they need to. When that happens, the problem definitions are much easier and the resulting solution works. Obvious, when you think about it. The analogy I use is that if we were constructing houses, then my role is both architect and builder.
gyepi··on Talk about the problem, not the solution
> Or organisations being set up in such a way that the technical folk aren't in-play at the point where problem discovery is happening. Or the non-technical folk being assessed on "solution providing" not "problem defining".... and so on

This is the fundamental problem and is, I think, largely due to the fact that the kinds of problems we are solving do not naturally fall into the neat specialties into which most companies categorize their workers. Specialization promotes serial thinking whereas what's needed is near simultaneous thinking and that requires deep communication (and smart people)

gyepi··on Free Must-Have “Security Engineering” Book
Most programmers are, I think, quite capable of designing and building software to a set of specifications. However, most would not, in the process, also try to think of all the ways in which users and attackers would try to break their software. This book provides a comprehensive introduction to security issues in general and particular ways in which systems can be broken (and protected).

It is not prescriptive by any means but reading it provides a level of security awareness that is frequently lacking.

Knuth once wrote that before he writing tests for his programs, he puts himself in the meanest, nastiest mood he is capable of. I believe that this book can a similar purpose ,in the security context, for those of us to whom deviousness and cunning do not come naturally.

gyepi··on The Quiet Revolution in Programming
>By going this way you're running towards a brick wall, the wall of your limited brainpower: at one point you will not have enough brainpower to keep juggling the increasing number of "proper tools" and you'll have to stop growing, stop learning and enclose yourself in warm niche/bubble.

I couldn't disagree more with this statement; it seems to me you have this backwards. The purpose of "proper tools" is exactly to encapsulate the complexity and provide a simpler interface with which we can address the problems. In fact, as the level of complexity rises, you need tools that provide the right level of abstraction. In many cases, those tools are specialized because they address specific aspects of the problem. Each such tool pushes out the boundaries of our limited brain power.

For instance, I use a lot of code generation in my work. A complicating factor in code generation is the fact that you are working at two or more levels simultaneously; the code generator and the target language. However, with the proper tools, the problem becomes very tractable. In this case, I am referring to explicit code generation, but exactly the same issues arise when generating code with Lisp style macros.

As to the universality of languages, I can only say that the practice gives lie to the theory. Once you've used enough languages, their differences (and fitness for particular problems) become clearer.

gyepi··on The Quiet Revolution in Programming
This line of reasoning is quite standard, and for many purposes, quite valid. However, in my particular case, it is not. Each language served a specific purpose that could have been accomplished by another, but with greater effort. Sometimes, it's better to use multiple languages in a system than to use just one throughout. Unfortunately, I can't go into more detailed reasons, but I assure you, it is not for "toying" around.
gyepi··on Free Must-Have “Security Engineering” Book
Free is fine, but this book is worth acquiring in paper.

I have both editions and cannot recommend it enough. If you are responsible for the security of any kind of system and have not read this book you may want to fix that asap.

gyepi··on The Quiet Revolution in Programming
It's scary because, knowing only one language means that he can only think about, and express solutions to, any problems in terms of that language. In this case, he was not expert at Perl either, so the net result was ... not good. I remember seeing Perl programs that would have been better written as very short shell scripts.

Note that "mainly just knows Perl" is quite different from "only knows Perl".

Since then, I have never met another programmer who knows only one language; I think they are pretty rare. As for proving the case, I don't think I can: there may well exist a good monolingual programmer out there. It's just not likely.

gyepi··on The Quiet Revolution in Programming
Given that the circumstances differ, I don't think I could provide any specific guidelines.

I am not averse to using multiple languages in a project if each serves a need so, in the past two months, I have used gsl, TCL, Python, C, and Go for various components of an ongoing project. But not necessarily all at the same time. Most days, I focus on one and only deal with two simultaneously during integration or code generation.

gyepi··on Douglas Hofstadter has a new book
> See George Lakoff and Mark Johnson’s 1980 book, Metaphors We Live By

I highly recommend this book! You'll find yourself nodding in agreement at one line and then realizing that you're agreeing with a deeper truth than you knew. At the very least, you'll start reading newspapers at multiple levels.

gyepi··on The Quiet Revolution in Programming
Many years ago, I was working with a Perl programmer and, making conversation over a lunch or coffee break, I asked him what other languages he knew. He replied, "only Perl." I was shocked and persisted in my questioning, even offering up other common languages in the hopes that he was being merely forgetful, but he was quite clear that he knew only a single programming language. This, I find very scary.

This is probably not far from the norm where a programmer "knows" multiple languages but are only expert in one. This is almost as scary to me.

At least for me, there's a refreshingly synergistic effect from knowing and understanding multiple languages well.

In fact, I would go so far as to claim that a good programmer should know and understand a variety of languages and, ideally, use them frequently.

gyepi··on A mother tongue spoken by millions of Americans still gets no respect
AAVE is indeed spoken by people of low economic status, but is certainly not limited to them. I have met many, many African-Americans of high economic status who also do so, but informally and generally only with other African-Americans. I think the stigma is more closely associated with their culture than economic status.
gyepi··on Ask HN: Where are the hard programming challenges/jobs?
This is a good question. I've worked in a lot of different domains and can tell you that:

1. They all have boring parts

2. They all have interesting parts.

3. Doing the interesting parts well can be very challenging.

CRUD is only boring because of the generally repetitious nature of talking to the database, but repetition usually means that it can be generated. Whenever possible, I write code generators for that sort of thing. This is not only more interesting and gives me time to solve the more interesting problems but also allows me to produce more and better code than I could just typing it all out.

You could get a PhD, I suppose, but hard problems generally require the insight to see them and the willingness and ability to work on them. Sometimes ability requires a PhD, but that's not a given.

gyepi··on Ask HN: Where are the hard programming challenges/jobs?
Sorry, but I don't think there's a distinction to be made, other than one of degree unless the implication is that improving government/military processes is not aligned with the long term goals of the military.
gyepi··on The Setup: Mike Fogus
I always enjoy finding out how others work. Mostly for curiosity, but also to glean new methods and habits I could adapt for myself. I particularly enjoyed this one because fogus seems to share my habits of using a pen/pencil as a thinking tool, thinking hard before jumping into a problem and using a Model M keyboard.
gyepi··on Why Use Make
> If your project sports auto-generated code, or any sort of > build targets that depend on inputs only known after > generation -- Make simply cannot handle this. > There are ugly workarounds but they don't work well.

Hmm. I write a lot of generated code and have not found this to be true at all. Many of my projects have multiple levels of code generation that and make handles them just fine. The key is to play to make's strengths and define pattern rules so you can hook into rules engine. Nothing like typing make and having it know to run a script to generate a text file that is further processed by another tool to generate more files that eventually get compiled to produce what you want.

gyepi··on A Short Rant About Working Remotely
I've noticed quite a few responses in this vein. It may be worth considering that indeed, personal productivity is part of the benefit people get out of this kind of work.

I, too, am much more productive working at home. So much so that I started working from home 3 days a week and eventually just switched to remote work. I understand the need for team productivity but there are ways to solve it that don't require constant face time. When I, as a remote worker, had to hire employees to work for me at the office, I made sure to hire people who were good enough not to require constant supervision and did not need to ask a question every 5 minutes. After the initial orientation, I made sure to be available by email, IM, phone (in that order) which worked out just fine.

I think part of the reason for the strong differences of opinion is that both can be right. The right team, colocated, can be very productive. However, I have seen many colocated teams fail, sometimes horribly. Conversely, I've seen remote teams do extremely well also. In fact, all remote teams I've worked with have done quite well. Obviously some of that may be due to their motivation, skills, experience, etc. But the fact remains. As I say to everyone who asks, remote work is not for everyone. We're used to the norm of working on location, but that, too, isn't for everyone.

gyepi··on The Best
yes
gyepi··on Who has the most electoral votes right now
Given that the process is still unfolding, a single page site around a single, albeit moving, data point is slightly amusing. However, I fail to any other point to it.
gyepi··on Whatever It Takes: Visualizations in E-mail with d3.js
If you think about it, it's no more brittle than ajax calls that return HTML. Having used this technique successfully, I know it works and can work well.

I don't recall any handicap at all.

Yes, this kind of solution requires more resources.

Yes, if zoom, filtering, panning and other interaction is required, then the server would have to output SVG and some javascript to manipulate it.

These objections are all worth raising but do not negate the power of this kind of solution. For certain categories of highly interaction apps with a large amount of image or data processing, doing all the work on the client side is a really bad idea, given the wide varieties of client capabilities and available bandwidth.

← PreviousPage 4 of 5Next →