bartonfink

This isn't difficult to research on your own.

Anyone who says that hasn't tried hard enough. You can absolutely outrun your fork. You just have to run a lot further than you think. There are no fat people who run 50 miles a week.

Yes.

Discipline and making it a non-negotiable priority in my daily life. For me, a day I don't run is a wasted day, so I like to get it done before other stuff can interrupt. I structure my life to make that possible.

I go run about 10 miles around 4:30 to be done by the time kids need to wake for school. To make that happen, I go to bed before 9:00 every night. It doesn't leave very much time for other activities but I can't say my life was improved by wasting time on personal projects or watching TV.

You can absolutely outrun your fork, you just have to run a lot farther than you think. There are no fat people who run 50 miles a week.

Some people hear "one mile burns roughly a soda", look at the numbers and assume that weight loss through exercise is not going to work for them or anyone. These people give up way too easy.

HN suffers from a peculiar obsession with theory and optimization. There's no secret to aerobic exercise: go get your heart rate mildly elevated for a while. Do whatever activity you can stand making part of your regular life, and stick with it. Do it long enough and you'll lose weight to boot. This is a simple truth. Things get complicated at the fringes, or if you want to actually train vs just get fit, but most of HN is not a fringe case unable to benefit from basic exercise. They just pretend to be to ignore that simple truth.

Commit to an exercise regimen, ultimately building up to an hour or so of vigorous activity a day. Find some physical activity you enjoy and train hard to get better at it. Your diet and weight will ultimately take care of themselves if you commit to staying active and improving.

There are no fat people who consistently run 50 miles a week.

They do, to a certain extent. It's called whole wheat.

You're not losing fat because you're too sedentary. You absolutely can outrun your fork. You just have to run a lot further than you think. Show me a fat person who runs 50 miles a week.

You can absolutely outrun your fork, even into middle age. You just have to run a lot fucking farther than you think. A mile burns about 100 calories, very conservatively. Do the math, then do the miles. It's not going to be easy but it's unequivocally possible without a Herculean training regimen.

[REMOTE] [Full-Time]

The Edge Foundation team at WalmartLabs is looking to fill multiple open positions at Senior and Staff levels of experience. We build systems to optimize and deliver the assets, images and scripts on a variety of high traffic websites. Bytes and milliseconds matter, wherever we can find them. Our purview is helping customers “Save Money and Live Better” by accelerating performance across ALL of Walmart’s eCommerce traffic.

* Fully distributed team

* 90+% Go

* Distributed Systems

* Observability

* Performance is #1 objective

The team is completely remote. USA is the only frictionless option (although we have occasionally been able to make arrangements in China/Poland/UK/Canada).

If you're interested, please feel free to shoot me an email (personal email is jsbeal@gmail.com - you cannot possibly waste my time by dropping a line).

Whole Latte Love | Remote (HQ is Rochester, NY) | Full-Time (W2)

Whole Latte Love is among the largest retailers of coffee, espresso and other caffinated goodness on the internet today. In business since 1997 and based out of Rochester, NY, Whole Latte Love sells high end coffee beans and equipment to thousands of people around the world. At Whole Latte Love we are about everything coffee and we put passion behind everything we do. We're looking for a couple of developers to help scale out an in-house development team and expand a successful US-based business overseas. This is going to mean a lot of development to grow from our current monorail storefronts to a more service-based platform.

Right now, we are built on Rails with a heavily customized Spree back end. We deploy to AWS via Ansible, and are backed by MySQL and Redis. Our front-ends are primarily Deface/ERB - this is a traditional multi-page app for the time being. We believe in using the right tool for the job, and are always open to evaluating new technologies and platforms. We're not looking specifically for front-end, back-end or devops specialists, although we have pain points that would be served by any of these. Rather, our ideal candidate will build a role around themselves, and be able to find multiple ways they can contribute across our systems, without getting distracted or going too deep down the rabbit hole. We aren't tied to any specific amount of experience, but we expect that you'll be able to take a feature or issue to production without too much hand holding (what might be called a mid-level or senior developer).

It's a low-key work environment, and we have a lot of management buy-in to build as effective a development team as possible. Development is primarily remote, so proactive communication, responsibility and accountability are at least as important as technical ability. There will need to be regular overlap with core hours (8:30-5:00 EST) but we can work out the specifics of what that overlap entails depending on where you live.

Please write to coffeejobs@wholelattelove.com with an introduction and resume. An online code repository is helpful and even encouraged, but absolutely not required. Thanks!

I worked at AIG during that crash, in their mortgage insurance subsidiary. To say we were hammered is a massive understatement. Two thirds of the company was laid off during one week: the gating factor was meeting rooms in which to process the layoffs. Many of these people haven't fully recovered: they were "lifers" and most of their skills were tied to that specific company and industry.

Free soda immediately went away, with a very lame justification ("it clogs the drains when people pour them down the sink").

There were news cameras parked outside for a couple weeks, trying to get sound bites from people coming and going.

There were even a few attacks on employees in the streets immediately afterwards. We were encouraged to go out in small groups: alone, there was danger of being accosted by people who lost their mortgage, while in large groups it created the impression we didn't care about what was happening to the world outside.

It was pretty intense. I'm glad I saw it as close as I did, but I'm not sure I would like to do that again.

Compilers, for start.

Isaac Asimov thought so. I recall reading a quote by him at one point about how air conditioning and television directly made cities (of which he was very fond) less safe and friendly places because people didn't stay outside to socialize with their neighbors and stay cool: they stayed inside.

"Night was a wonderful time in Brooklyn in the 1930s. Air conditioning was unknown except in movie houses, and so was television. There was nothing to keep one in the house. Furthermore, few people owned automobiles, so there was nothing to carry one away. That left the streets and the stoops. The very fullness served as an inhibition to crime."

Hypothetical response:

"Of course, brudgers, and with your experience I'd hope that you would understand that we don't expect you to replace the $LANGUAGE standard library on this job. However, it's still important to us to know that you have some idea how to do that, even if only as a proxy for the sort of work we do expect you to do on this job. So, mind humoring us and taking a stab at it?"

Two I've seen and enjoyed were:

1.) Given a name, print out the appropriate lyrics to the "name game."

2.) Given a word (and the morse code table), output its Morse code translation.

I've worked for startups, bigco's and a couple places in between, doing full-stack development, tech leadership and whatever else needs doing. I'm looking for something new after a startup I was trying to pull out of a nosedive crashed.

Location: Denver, CO

Remote: Preferred, but let's talk.

Willing to relocate: Let's talk.

Technologies: Scala (Play!), Ruby (Rails/Sinatra), Java (Play!, Spring, J2EE), Javascript (Node, Backbone, Angular), Databases (Relational, MongoDB, Redis, Neo4J), DevOps (used Heroku and AWS).

Resume: Best viewed on LinkedIn at https://www.linkedin.com/in/jsbeal

Email: jsbeal@gmail.com

I once read an interesting solution to this specific problem on the old Joel on Software forum. In addition to offering a competitive salary for people to work at an odd location, you could offer a relocation bonus for people to leave. This assuages a large concern that some folks might have: that they'd love to work at your company, but if things go sour, they'd be stuck in Pigs Knuckle, Arkansas without any other job opportunities. I'm sure there are wrinkles to iron out, but that would directly target a mostly unrealized objection to relocating to a less desirable area.

I've written this exact idiom in some parts of a very poorly structured, tightly-coupled PHP codebase I've inherited. I'm not a huge fan, because it clutters the codebase a bit (that's 4 lines of overhead per dependency), but in the absence of a true DI framework this is better than nothing. You get many of the functional benefits of DI, but not all of the niceties when it comes to cleaning up your code.

The phrasing is very similar to "quis custodiet custodies" - who watches the watchmen - which is a very well known phrase. The most I can make of this is "Who $foo's the $foo'ers".

Does anyone have any idea what crespo and crespulum mean? I checked two of my dead-tree Latin dictionaries and even resorted to an online search and came up empty. This is going to stick in my craw for a while until I can sort it out. Any other Latinists out there with ideas?

Considering SQLite is only 15 years old and implements a rigorous specification instead of an evolving set of product requirements, you're just over halfway to what he talked about.

That's interesting. Their Boulder office contacted me earlier this year about an interview, and I felt it would have been a pointless exercise since they'd fallen so far behind their competition (iTunes/Apple, Spotify, Grooveshark) that innovation and quality would take a back seat to revenue. Having just left a job at MapQuest (which is well on a similar advertising-driven downward spiral), I just declined and haven't heard anything further.

Glad to hear an anecdote that confirms I made the right read on that.

That reminds me of something I didn't really like about the otherwise excellent Europa Report.

<rot13> Jul jbhyq gur Rhebcn perngherf unir ribyirq ovbyhzvarfprapr, naq rfcrpvnyyl gur novyvgl gb hfr vg sbe pbzzhavpngvba, tvira gurve raivebazrag? Nyy yvsr ba Rhebcn jbhyq unir ribyirq va n yvtugyrff bprna, beovgvat n eryngviryl snvag Fha, ohevrq haqre n eryngviryl guvpx pehfg bs vpr. Guvf frrzf yvxr vg jbhyq cerpyhqr gur qrirybczrag bs gur rlr (jr frr gung gur rlr vf fryrpgrq ntnvafg va pnir-qjryyvat svfu, sbe vafgnapr), naq guhf jbhyq znxr ovbyhzvarfprapr varssrpgvir naq na haarprffnel jnfgr bs cerfhznoyl fpnepr erfbheprf. </rot13>

It's not a major point, but it struck me as odd given the otherwise rigorous nature of the film.

That checked exceptions aren't nearly the boondoggle they're made out to be.

Human readability is a concern of a client and is independent of the storage mechanism. Every modern database stores integers in binary format, for instance, but clients display them as a decimal string of characters as opposed to a binary or hexadecimal representation. Timestamps are similarly stored in binary fashion, but often formatted for human readability in the client.

I had a friend blow a job interview on something very similar. The company gave a description of an app and asked that he code something up over the weekend and host it on github for them to see. He wrote up a pretty basic app that did what they wanted, but the poor guy completely lost his head and couldn't remember `git init`, so they passed. Whether that's fair or not is another ? (I think it was, given he was interviewing for a senior role), but it's important to keep in mind that even though you may have been a productive maintenance engineer, working within an established codebase, basic infrastructure-level stuff that comes up once a project can still bite you.

In my experience, it's not technical knowledge that makes me view someone as a "go to" engineer: it's reliability. I don't like surprises from anybody when it comes to work, and I really respect engineers who can deliver thoroughly and on time without surprises in code quality.

Getting something done on time can be tricky, but the hallmark of a "go to" engineer is that, if something's going to slip, they speak early about it. Going down a rabbit hole is a bad thing, but going down a rabbit hole without telling people and checking back to see if you still need to be down there is worse.

Getting something done thoroughly means, to me, that you've written code that is tested and is reasonably robust given the nature of what you're doing. Code that lacks null checks (if you're in a language where that's a concern) is not robust. Code that doesn't handle obvious errors is not robust. Code that doesn't have any tests with it is not robust.

Code quality is a matter of taste, but what it boils down to is how well code follows the established patterns in the codebase or, if those patterns need to be changed, how well the new solution solves problems the old pattern exposed. Most development does not take place in a vacuum, and if someone goes off and does a lot of extraneous refactoring, everyone else has to pay the price of merging their work together and acclimating themselves to whatever's changed. Frequently, large refactors aren't worth that cost, and a "go-to" engineer is going to understand that balance and err on the side of getting things done versus getting things perfect.

I have one of the Dell XPS 13's, and while the machine itself is great, you should take note that the power adapters are Dell-specific. I noticed this after my original power cord got cut and none of the replacement adapters I purchased worked. Dell's adapters send a signal that is picked up by a chip on the motherboard that will disable charging unless that signal is detected. This check is beneath the level of the OS or even the BIOS. Effectively, that means that you're stuck paying a Dell markup (which can be substantial - 100% was what I saw) for an official charger.