start: 1,2,7,10|
1: 7,10|1,2 = 2 minutes
2: 1,7,10|2 = 1 minute
3: 1|2,7,10 = 10 minutes
4: 1,2|7,10 = 2 minutes
5: |1,2,7,10 = 2 minutes
total: 17 minutes74 karma · joined March 3, 2014
start: 1,2,7,10|
1: 7,10|1,2 = 2 minutes
2: 1,7,10|2 = 1 minute
3: 1|2,7,10 = 10 minutes
4: 1,2|7,10 = 2 minutes
5: |1,2,7,10 = 2 minutes
total: 17 minutesBrewery: https://news.ycombinator.com/item?id=7375043 Food Truck: https://news.ycombinator.com/item?id=5376402
Different languages have different sets of phonemes. For instance, in Japanese, "L" and "R" are allophones, meaning native speakers consider the sounds to be the same. So, take these two UBI's:
http://ubicate.me/NALADU-MAMOKE
http://ubicate.me/NARADU-MAMOKE
Smack dab in the middle of Tokyo, about 15 minutes apart from each other.
Also, this would require speakers having the same vowel distribution/phonological rules. I pronounce "PACASU-FADERO" and "PACASU-FEDERO" pretty similarly. Relying on letters that are only different in voicing is also risky. For instance, take "P" and "B". It's easy to mistake "PACASU-BATERO" for "PACASU-PATERO".
Finally, street names have an advantage over UBI's. Street names are usually formed from words in the inhabitants' native language, so they sound more natural and will of course be easier to pronounce.
Not only can you can have dynamic pricing based upon stations and times, imagine having a feature where you can "call" for a bike at an empty station. There can be an app that notifies people near other close non-empty stations to ride a bike over for you. Or, you could even display it on the screen of the kiosk.
How would you get people to ride these bikes for re-balancing or on demand?
Offer something like a rewards plan (re-balance a bike X number of times and receive a discount on your next bike rental) or pay them in micro-payments (Think Tom Hanks returning luggage trolleys in The Terminal).
How could you ensure that people riding bikes on demand don't take advantage of the process to just get a free ride to wherever?
First, make sure that the bike being taken out is checked into the station it's being delivered to. Second, impose some sort of time limit in which that needs to be done. Base the time limit on an acceptable pace and take into account the distance between the stations (with a time buffer). If it exceeds that limit, it becomes a regular rental and the deliverer is charged regularly. Also, it then becomes possible to add bonus incentives for getting the bike to the station faster.
One particular bonus of this system is that it can leverage a city's homeless population as a workforce. (If you disagree due to cleanliness issues, I'm sorry to tell you that the homeless already use citibikes as cycling machines). Of course, there would be a need to hedge against the possibility they may just take out a bike and never return it, since they don't really have any sort of credit. One possibility would be to sponsor a homeless person by covering the cost of a bike and then having them operate on a "one strike" policy.
1. The work-for-hire occurred at least two years ago. This would peg the time frame at roughly early-mid 2012.
2. Pigeonly started out as Fotopigeon, the photo sending portion of the company. Telepigeon was added at a much later date.
3. Pigeonly applied to the YCombinator Summer 2012 batch, but was rejected [1].
4. Pigeonly entered the NewMe Accelerator as part of their Spring 2013 batch[2]. The equity stake that NewMe took was 4%[3]. Crunchbase lists the intial investment date at October 2012[7]
5. Pigeonly also received a $20000 investment in December 2012 from FIU AVCC as well as $10000 in services from New Frontier Nomads to build out a MVP[4].
6. Frederick Hutson is placed in a work-release program in September 2011 and is released in March 2012[5].
7. Hutson's budget prior to December 2012 was a minimum of $2500[5].
8. From the article: "From the halfway house, he did not have any money, so he persuaded the photo company to do some coding for free." [5]
9. The developer claims Pigeonly fell behind on payments[6].
Now for the assumptions/conclusions:
A. From #2 and #5 we can conclude that that the codebase in question is not in use today.
B. Prior to October 2012, based upon #3, #4, #6 and #7, we can assume that the total amount of funding Pigeonly had was not substantially more than $X000.
C. From #8, interpreting the identity of "the photo company" is impossible, but if we assume that it is the developer, then D follows.
D. From #8, initial coding occurs while Hutson is in the work-release program ("halfway house"), pegging the date at some time between September 2011 and March 2012 (from #6)
E. From B and D, it seems that #9 is plausible, if not probable.
[1] https://news.ycombinator.com/threads?id=jparkside [2] http://www.newmeaccelerator.com/2013/02/04/spring-2013-start... [3] http://www.f6s.com/profile/38508 [4] http://avcc2012.fiu.edu/ (second image on the carousel) [5] http://www.tampabay.com/news/humaninterest/idea-mans-latest-... [6] https://news.ycombinator.com/item?id=8227225 [7] http://www.crunchbase.com/organization/pigeonly
The first method (contracts) is dependent upon people. The second method (money) is dependent upon your currency remaining relevant as well as finding some way of managing the fund. People and money are both fallible, but I included them for completeness. I personally think that the last two reasons are much more likely if we're talking about hundreds (or thousands) of years. At those intervals though, a more relevant question might be, "who would store and maintain the bodies?"
I'm not familiar with how you're processing the picture, but it might be possible to identify the columns by utilizing the empty row at the top of each column. I count 7 positions/bits. You can use 2 bits to mark the month and the remaining 5 bits to mark the day of the month. Using this encoding, you could even add a fourth month without any problems.
Also, another cool level of granularity (if needed) could be using 1x2 or 1x1 lego blocks to add more information that's easily seen in the photo. Not only do you have different colors of 1x2 and 1x1 blocks, you can also place them in different positions (left/right vertically, top/bottom horizontally).
All in all, great idea. I'd like to set one of these up myself in the future.
1: http://www.npr.org/2011/08/23/139854129/young-entrepreneur-h...
As for the last article, that one does talk about residential housing. I will agree that the article does talk about urbanization as the natural progression of town maturation. However, note that the article talks about progressions/increments (i.e. going from a house to a duplex, from a duplex, to a row of houses, from a row of houses to an apartment building) and not skipping those progressions (going straight from a house to an apartment building). In fact, the article specifically outlines that the changes must be natural, be compatible with the neighborhood, and must fit in. Overall, Marohn's more concerned with adding value to properties than increasing population density. He even goes as far as to specifically address our topic of discussion. I quote:
"I am going to pause now before going on to the next step and reiterate something important. I know there are those of you reading this right now, sitting at the kitchen table of your nice single family home, saying, "There is no way on God's green earth that I'm going to allow a set of row houses across the street from me. Who does this Strong Towns guy think he is?" Fair point, and the reality is that most neighborhoods will not grow beyond the single family stage. That's okay too, at least as long as the public infrastructure and services stay scaled to that investment level." Emphasis mine.
He states that what's tantamount is responsible spending.
"Here’s what he means. The way suburban development usually works is that a town lays the pipes, plumbing, and infrastructure for housing development—often getting big loans from the government to do so—and soon after a developer appears and offers to build homes on it. Developers usually fund most of the cost of the infrastructure because they make their money back from the sale of the homes. The short-term cost to the city or town, therefore, is very low: it gets a cash infusion from whichever entity fronted the costs, and the city gets to keep all the revenue from property taxes. The thinking is that either taxes will cover the maintenance costs, or the city will keep growing and generate enough future cash flow to cover the obligations. But the tax revenue at low suburban densities isn’t nearly enough to pay the bills; in Marohn’s estimation, property taxes at suburban densities bring in anywhere from 4 cents to 65 cents for every dollar of liability. Most suburban municipalities, he says, are therefore unable to pay the maintenance costs of their infrastructure, let alone replace things when they inevitably wear out after twenty to twenty-five years. The only way to survive is to keep growing or take on more debt, or both. “It is a ridiculously unproductive system,” he says."
Taken in context, the quoted sentence is specifically talking about the development/expansion of a town beyond its current financial means. In other words, the town builds out its infrastructure and is banking on an influx of new homeowners (taxpayers) to help with the maintenance of the infrastructure. When that doesn't happen, that's when the tax revenue/liabilities ratio dips below 1.
Also, if you go to the Strong Towns[1] website that Charles Marohn helped start and read the Mission Statement and their Quantification of a Strong Town, nowhere does it talk about population density or converting suburbs/towns into cities.
Here's what I've got so far:
Software development is, at its core, a terribly frustrating profession. You're lured in with promises of being a lone hacker building a billion-dollar website overnight in your dorm and hear about the excitement of building a new product or even embarking on a new project for a client. It's only later that you find out that most people who stay up all night hacking away on side projects never ship them (or if they do, they never make a dime) and that most of your work is going to be maintaining and updating code rather than writing your own from scratch. Eventually, you fall into some sort of coping mechanism such as the pomodoro technique, Agile development, or some other poor solution to the fundamental problem of the profession. The problem is that the software development industry hates software developers. It really hates us and, if you think about it, that makes sense, because we can make a lot of demands to business types that others simply can’t.
Recently, the industry has tried to curb our influence by outsourcing our jobs. It was thought that business could just hire seventy-five (75) percent off their staff offshore for one-third of the price and use that as downward price pressure in the domestic market. Though that hasn’t gone as well as some would have liked, it certainly hasn’t failed completely. Still, the results were less than stellar and a lot of business are now hitting pain points with foreign development, causing many of them to bring their dev projects back home. But, these businesses don't want a seventy-five (75) percent price increase overnight, so what’s a slick talking, frugal businessman to do?
You sell the lone hacker myth and hand out little bottles of Facebook-style startup Kool-Aid. After all, it turns out that a lot of young programmers have an inflated sense of their abilities and can be easily manipulated into working what amounts to unpaid overtime. Only an idiot would put a young developer on an hourly wage when they could instead give him a set salary with unrealistic deadlines to squeeze the extra work out of every penny. Well, guess what? It worked! These young developers will work 50-60 hour weeks for their businesses and still promise to work harder next week. Better still, if they have a personal event or other issue, they will even apologize for that rare 40 hour week! You've got to love kids! You must be so happy. Look at all the value you can show your investors and how modest the L side of your P&L is!
But wait, something seems wrong. It’s been about a year and your dev is becoming a little harder to work with. He’s starting to mention things like vacation tim. Doesn’t he know that <insert random month here> is super important for <insert company name here> and it’s crunch time? Sure, it was crunch time the month you brought him on and pretty much every month after that, but isn’t that just the nature of the business? Worse still, he is out the door every day after his eight hours – is he no longer committed?
Then, it happens. Your dev up and bails on you. Maybe he gives you two weeks of notice; maybe he doesn’t. Either way you're down a dev and probably not sure why. Well, the answer varies based on the dev – it could be family, a better offer, or any other reason. But, there is a commonality in most of these cases: on some level the dev figures out that the economics just don’t make sense; at least not if he is to work the hours that you expected. Before wondering what happened ask yourself this: if that dev were a lawyer or CPA would you have expected the same type of “commitment”?
Let’s face it no business manager would think about asking for the level of commitment and self-sacrifice that is commonly asked of software developers of a lawyer or CPA. The reason is simple: most businessmen value lawyers and CPAs – they respect them and see them as professionals. The see them as professional adults where developers are just overgrown teens in their eyes. The sad part is that we allow this. We have created the youth culture around “hip” development technologies that allows this sort of age discrimination against more mature developer while simultaneously promotes the abuse of young developers. It’s time that we as software developers demand the same respect that other professionals get and end these age issues.
We are of course not blameless in this lack of respect. Whenever a dev shows up to a meeting in a hoodie or gaming tee, he sends the message that he is not a professional. So please give the hoodies to the Salvation Army and throw on a polo. Also, you are not a “rockstar”, “ninja”, or “code samurai”. You are, however, a “Software Developer”, Software Engineer”, or “Programmer”, so make sure your business card has one of the latter titles on it rather than the former and use the more professional title in conversations. One more thing. Keep your conference presentations PG13 and please don’t make sexual comments; that goes double for dongle jokes. If we can all act like professionals maybe we will be treated like professionals.
I subsisted off the $1 Double Cheeseburger for a year in college. Now I feel rather guilty about it. Oops.
[1] http://en.wikipedia.org/wiki/Bystander_effect [2] http://en.wikipedia.org/wiki/Diffusion_of_responsibility [3] http://en.wikipedia.org/wiki/Volunteer's_dilemma
could not reproduce.
For firefox or chrome, right-click the search bar on any site and select "Add a Keyword for this Search" ("Add as search engine" for chrome).
[1]http://rady.ucsd.edu.prx.us.teleport.to/faculty/directory/gn...