HN user

alwold

49 karma
Posts0
Comments23
View on HN
No posts found.

I’m not sure about this one, but I recently installed LibreNMS (an open source nms) on my home network and it does a decent job keeping track of traffic on my ubiquiti edgerouter. It uses snmp so should work with most routers, I imagine. I specifically set it up to tell me when I use more than a certain amount of data in a day to avoid data caps. It was a bit fiddly to set up, but kind of fun.

I wonder how hard it would be to build a nice diff tool for IB files. If you could (semi) visually view the changes in a meaningful way, maybe a lot of this would be helped. Conflicts would still be hard to merge, but maybe something could be done about that as well.

Talking About Money 11 years ago

I don't think this is really that big of a concern. If you try to negotiate for more pay, I don't think anyone is going to rescind the offer. The worst case is that they won't budge, in which case you can still take it.

If someone is willing to rescind an offer because they are upset that you tried to negotiate, it's probably not someone you want to work with anyway.

Bringing an existing business you've been working on is against the rules. That should have been enforced by whoever was facilitating.

If the rules are well explained and enforced, and you keep an open mind, startup weekend can be pretty cool. If your idea is bad, it will get eliminated right away, and you have to be ready for that. It's also best to team up with people you don't know, and you might meet one or two people that you'll end up becoming friends with.

It looks like EBCDIC supports lower case letters just fine. Any idea why they used all uppercase? I've noticed use of all uppercase on a lot of old systems, and always sort of wondered why. Is there a good technical reason? Maybe a data type that uses less space per letter?

Eating lunch out every day can definitely get expensive, and people don't realize that. Of course, you don't have to buy your lunch in order to not eat at your desk. Assuming you have a place you can go (in this guy's example, a park), you can always bring something from home. Or, if you need something more exciting than what you can make at home, do like this guy:

http://www.slate.com/articles/life/food/2012/02/liberate_you...

...and then bring it somewhere other than your desk to eat.

It probably also depends on what you are trying to build. His initial example of building chips would probably be nearly impossible without a pretty big up front investment.

If you are building something with software, it is a lot more likely that you could self fund.

I don't really think you need enough so that you never need to work again to consider yourself financially independent. If you have enough to live for a year or two, you can be pretty independent. Yes, you'll have to work and earn some more money, but you aren't dependent on that biweekly paycheck, so you can be somewhat selective, and do whatever you want, within reason.

Also, if you are into minimalism, you can really live on quite a small amount of money, so that can reduce the amount of work you have to do even further.

I wouldn't think any significant form of active transport would be going on in a dead bird. Also, I think the sodium-potassium pump pumps sodium out, not in, although you could be talking about a different pump?

In the absence of any pumps going on, I would imagine a 35% solution would be extremely hypertonic compared to the interior of the cells, and water would definitely flow out.

Exception throwing is not that new. It's just a question of what is the style in the language you're using. In Java, for example, throwing exceptions has been the norm since JDBC was invented in 1997. PHP is definitely different in that exceptions are rare. Same story with C++. I'm not super experienced with Ruby, but they seem pretty common there, so I would've expected to get one.

My experience is somewhat limited to places that probably don't have the best developers in the world, but I think one of the major things I've noticed in people that I would consider to be mediocre programmers is a lack of desire to understand how something works. They just want to get the thing they need to work, and often times this lack of desire to understand how something works extends to their own code. If you strive to understand how your own code works, you will be much more likely to notice the bugs as you think through the flow.

Early on when I was learning to program, I had a very strong curiosity that made me want to understand how everything works. I think if you have that natural curiosity, it is the easiest way to become a better programmer. As I've gotten older, though, that has waned. In response, I've tried to build habits of investigating things and trying to learn about them when I don't understand them. It is tempting to just use google to find the answer, or "shotgun" it by trying all kinds of random things before you get it to work, but learning how it works is always the best, and it will pay off later.

So, I guess my main point here is to just keep tinkering and reading and getting your head wrapped around all these things so that you understand them well. Then things will eventually become "easy" and intuitive.

SEEKING WORK - Remote/Phoenix

I've got a lot of experience with Java, in both the web and mobile space. I did a lot of work on earlier mobile (J2ME, Blackberry, etc.). Now, I'm looking to do more Rails and iOS work, and have spent time getting familiar with those. I'm also starting to play with Node now, so if you need that I may be able to help.

See http://alwold.com for links to my github, resume, etc.

alwold at gmail dot com

SEEKING WORK - Remote/Phoenix

I've got a lot of experience with Java, in both the web and mobile space. I did a lot of work on earlier mobile (J2ME, Blackberry, etc.). Now, I'm looking to do more Rails and iOS work, and have spent time getting familiar with those.

See http://alwold.com for links to my github, resume, etc.

alwold at gmail dot com

It seems like it might make sense to re-brand the app as a generic stream player. Then you could provide some sort of directory service to look up available streams where you provide access to CBC, along with other streams from other providers. The directory could even be made into a community feature where users can add new stream URLs.