erso

12 年前議論

I've owned both. Had a ZBoard, have a Boosted Board.

The ZBoard is utter trash compared to the Boosted Board. Build quality, ease of operation, sound of operation, ride quality are all far superior on the Boosted Board.

erso

12 年前議論

For homebrew:

    cd $(brew --repository)
    git remote add krishicks [email protected]:krishicks/homebrew.git
    git fetch krishicks bash
    git checkout krishicks/bash
    brew upgrade bash

I've opened a PR: https://github.com/Homebrew/homebrew/pull/32753

erso

12 年前議論

  An interesting way to solve the issue is to hide the bar when scrolling down, and show it when scrolling up.

This pattern is one of the many irritating things about the mobile Chrome and iOS 7 browsers that prevents me from using devices implementing either.

I typically stick to reading around the top of my device, and occasionally I want to re-read something I just read. Instead of just getting to re-read the hidden lines, I have to continue scrolling while stupid chrome or a fixed bar appears, and then finally lets me scroll the content.

It's probably the case that a lot of people love this, but I hate it. If I want to see the browser chrome or navigational elements, I'm happy to tap the top of the window to scroll me there. I don't want the browser trying to figure out what I want to do based purely on scrolling.

erso

12 年前議論

I agree with losing the hamburger buttons, but the Facebook example is terrible:

http://tctechcrunch2011.files.wordpress.com/2014/05/facebook...

  Left: Facebook’s old hamburger button navigation. Right: The new tab bar style

Looks to me like they just moved the same set of buttons from the top to the bottom, adding a "More" button.. which is a hamburger button!

erso

12 年前議論

A well-written, real-world review of Glass. I enjoyed it.

erso

12 年前議論

I'm curious to know if, were the tweets to be used, they would also have to prove it was he that made them. Sure, they're from his account, but would that hold up in court? See: the many celebrities who have people tweet on their behalf with their (the celebrities') account.

erso

12 年前議論

It was at some point in the past. I recently booted up an old machine of mine that's running Chrome 7.0.517.41 beta, and the option is both there and ticked by default.

erso

12 年前議論

New York

Junior/Senior developers at DaisyBill

We're looking for 1-2 developers who are experienced with Ruby, Rails, and JavaScript. We don't have a designer, so having an eye towards good UX/UI is a plus.

We're also looking for someone at the CTO level.

DaisyBill is located at 34 W 15th Street in Manhattan. We're a SaaS vendor serving the workers' compensation e-billing market.

Workers' comp is a vastly underserved part of the medical e-billing trade which has been a struggle for all parties involved: the injured worker, the practice that treats the injured worker, and the insurance companies that handle the claims/bills. Electronic billing aims to make the situation better.

DaisyBill manages the entire billing process, both generating and sending the bill electronically and managing the responses about the status of the bill, including when it was paid and how much. As a result of using DaisyBill, practices are paid more quickly and accurately than when they submit bills via paper/snail mail. We're talking 15 days instead of 60, 90, or more, if at all. This makes practices more likely to take on injured workers as patients, an obvious benefit for all parties.

You can read more about our service offering at www.daisybill.com.

The stack we currently run is Rails 3 on Heroku.

We use Git for source control and use Macs for development. We develop in an agile manner in the style of ThoughtWorks and Pivotal Labs, using Pivotal Tracker. We like our code to have tests, and as such we have an extensive suite covering the Ruby, Rails, and JavaScript code on the site.

Please send all inquiries to [email protected].

erso

13 年前議論

I'm not sure I understand the point of the post.

I like the idea of submittal checklists, indeed this is a part of our business that maps very literally to what our users need to do: complete a list of tasks before submitting an electronic bill.

However, equating submittal checklists to something including stand ups seems weird to me. Would you really have a checklist saying "Did stand up meeting today." and if so, why?

The point of a checklist is to put knowledge of what needs to be done for a task in the world instead of keeping it in the head (I've borrowed this idea from The Design of Everyday Things). Checklists are for complicated things, like the aircraft checklist you mention, that require every step to be checked otherwise people may die.

I'm a fan of small checklists for software development that determine when a user story is completed. In Tracker there's tasks you can add to a story that can be used as acceptance criteria, for example.

But what good is a communication checklist? Is it really a desire to have a checklist that includes items such as "had standup meeting?" And if so, why?

erso

13 年前議論

DaisyBill - 34 W 15th Street, NYC - http://www.daisybill.com

Senior Ruby/Rails/JS developer, full-time and local only

DaisyBill does workers' compensation e-billing for the state of California.

We're a small company with 5 people in NYC and 2 in California.

Workers' Comp is a vastly underserved part of the medical billing trade which has been a struggle for all parties involved: the injured worker, the practice that performs services on the injured worker, and the insurance companies that handle the claims/bills. Electronic billing aims to make the situation better.

Effective October 18, 2012, all claims administrators (insurance companies, self-insured employers, et al) for California workers compensation claims are required to be able to receive bills electronically.

DaisyBill is the facilitator for practices to take advantage of this new law, allowing them to enter in the information about services rendered, seeing both what they should charge for the services and what they should expect to be paid (as these are not always the same). DaisyBill manages the entire billing process, both sending the bill electronically and managing the responses about the status of the bill, including when it was paid and how much. As a result of using DaisyBill, practices are paid more quickly and accurately than when they submit bills via paper/snail mail. We're talking 15 days instead of 60, 90, or more. This makes practices more likely to take on injured workers as patients, an obvious benefit for all parties.

--

We're looking for someone to help us with a new product/revenue stream we're going to be developing shortly. This product is a new fee calculator as the current one is expiring after the new year. We're also going to be integrating with third party billers that are currently unable to submit workers comp bills electronically. There is no shortage of work to be done and there is a lot of money to be made.

I'm Kris, the CTO and sole developer at DaisyBill. Previously I was at ThoughtWorks, then Pivotal Labs. I decided to get out of consulting and into a product company because I wanted to own the product I was working on. DaisyBill is the only company out of many I considered that has a solid business plan with an intent to make a lot of money and do some good in the process.

I'm looking for a senior developer that is experienced with Ruby, Rails, and JavaScript. The stack we currently run is Rails 3.2/PostgreSQL 9.2 on Heroku. I'd like to rewrite the site using AngularJS at some point in the near future, so Angular experience is a plus. We also don't have a designer, so having an eye towards good UX/UI is also a plus. We use Git and I'd expect any new hire to either already know Git quite well or be unafraid of it and be able to be brought up to speed quickly. I currently develop on an iMac with MacVim, and most people in the office use a standing desk.

You would be pairing reasonably regularly for the first few weeks but be expected to work independently not long after joining, asking questions as necessary. We also do a loose form of TDD: I typically like to sketch out an idea before trying to bake it in with tests. I also don't test every line of code. I believe in being pragmatic about testing. We use RSpec and Jasmine.

I do interviews similarly to the way they're done at Pivotal: After chatting about what you're looking for in a position I'd have you come in and pair on some code. I care a lot about the interview process allowing the candidate to suss out whether the work environment and the actual work is what they're interested in. I don't do conference room whiteboard programming.

I don't have a degree, and I don't expect you to have one, either. I don't necessarily care about how long you've been a developer, either. I care about the quality of your code today and your approach to solving problems. If you're capable and can show it, I'm interested.

You may reach me at [email protected].

Cheers.

erso

13 年前議論

Note to Pixelmator folks:

  Turn good-looking pictures into spectacular.

Perhaps that should say:

  Turn good-looking pictures into spectacular images.

Or something.

erso

13 年前議論

I've used only evasi0n on iOS 6.

erso

13 年前議論

Setting animation speed is also available for jailbroken iOS devices, if anyone's interested. The Cydia app is called FakeClockUp. I like setting it to 1.4x.

erso

13 年前議論

I found this article completely unreadable due to Helvetica Neue Light body font. The Helvetica Neue Ultra Light header is also ridiculously unreadable.

erso

13 年前議論

I found this post entirely unreadable due to its usage of Helvetica Neue Light #777 body font.

erso

13 年前議論

I've noticed this effect also, and across a number of apps, on both an iPad 4 and an iPad mini. It's most obvious on the mini due to the low pixel density on the iPad mini.

I can't read the mini in portrait mode mostly because I haven't found a font+size combo that I find acceptable.

erso

13 年前議論

Perhaps the first line of the post would have, then?

  In one of the most shocking videos I’ve seen
  since launching this blog six years ago...

erso

13 年前議論

Sorry, but what did you expect?

  California Police Arrest Man for Video Recording, then Kill his Dog

That seems pretty clear to me.

erso

13 年前議論

You consider Helvetica Neue body text in font-weight: 300 and color: #777 to be easy to read?

Jesus. I must be getting old or something.

I feel like this trend is a new kind of sickness plaguing web design everywhere. Even The Verge does it in articles: http://www.theverge.com/2013/6/17/4436332/macbook-air-review...

erso

13 年前議論

I'm not sure I understand.

If I'm making a change to some code and someone else makes a different change to it and pushes their change to origin before me, I do a rebase and see that they made the change, fix my commit (which is broken at that point in time), resolving the merge conflict, and continue on.

Instead of seeing some changes that have no basis in reality because they were fixed as part of resolving the conflict when doing the merge, you see only their changes applied on top of the correct state of the world, which gives you a clearer idea of what changes they made.

You can still get logical chunks of work with a rebase strategy: you simply rebase on top of the remote and then do a non-fast forward merge, via merge --no-ff.

投稿

Git rebase --onto

Deliver Value, Not Process

コメント