3,088 karma · joined March 11, 2012
https://www.gitclear.com
https://www.amplenote.com
https://bill.harding.blog
Because inner peace and contentment are overrated.
Step two will be for me to sift through the offers and figure out how they can be pieced together into a plan of action. It seems unrealistic to expect that we could raise more than... $20k?... from detail-oriented perfectionists, so I still need to figure out how best to constrain the scope of the goals enough to get this done with scarce resources (unless someone at Microsoft wants to kick in $1m in exchange for the affection of several thousand developers? :D)
It doesn't help that my day job is running a company in the process of launching two new products -- this has a tendency to gobble up available evenings and weekends and I wouldn't recommend it. But I've added it to my todo list to puzzle out how to combine these dev resources into a plan. It's plausible that the current libinput developer could be swayed by this outpouring to help me build a viable plan to build a modern Linux touchpad driver. I'll start there.
Look for an updated blog post with progress in the next couple months. And who knows, maybe I won't still be using this 10 year old hardware in another year?
Judging by the other responses here, I’m in a distinct minority to claim that you could consider building both businesses.
The jury is still out on whether this will prove to be a sound idea, we started building two separate projects last year and only one has been soft launched thus far (StaticObject.com).
That said, a couple relevant takeaways from our work to date:
1. The only way a multi product company can possibly work is if you’ve accumulated an inner circle that can stand in for you. You’re not going to do a great job building two things at the same time. You’ll need to find others who can pick up your slack 2. Our arrangement was pursued in part cuz we’re almost entirely self-funded, which means less VCs to encourage/force us to follow the path more traveled 3. A single, great developer can get as much done on a project as a team of 5 developers by virtue of reduced communication cost, and (hopefully) less tech debt. There is meaningful leverage available by splitting great devs onto separate projects.
Nevermind that the ride I canceled was 10+ minutes away, and was canceled immediately upon being booked.
Advantage: Lyft.
My conclusion: it's nice revenue while you can get it, but that probably won't be very long. Make money with their program and they're coming for you.
It's one thing that S3 keeps going down today; we run our own server cluster and I accept that 100% uptime isn't possible. But it's aggravating that they can't at least figure out how to give timely updates on their dashboard when something is broken.
We inevitably learn of S3 outages through our internal error reporting systems before AWS posts it to their status page. When they do finally post, it is usually a tiny "information" icon, even when reporting a problem that makes the service unusable. The laggy, misleading nature of their status page gives the impression they must be tying bonuses to the status icons. Can't fathom why else they would be so inept when it comes to keeping us updated when something is wrong. Surely they have sufficient internal monitoring to pick up on these outages long before they update their customers.
The only drawback is having to occasionally justify to friends why I don't bring a friend along (aren't you lonely? Aren't you bored? No). Probably a lot like the dog and pony show vegans have to put on when they meet someone new (don't you miss the eggs and cheese?)
We're looking for a developer to help us continue to build the Background Burner in Seattle, WA.
The Background Burner is a technology that embodies the adage that "the best way to predict the future is to invent it." It's all but certain that in the not-very-distant future, photo studios as we know them will cease to exist, replaced by studio-quality photos that require only a smartphone and the Background Burner.
It is fun to work on a tool that's on its way to becoming a staple of life, from online selling, to family photos & Christmas cards.
This software has already been used to process more than 10 million images, but we're only getting started. Some of what we're cooking up for it:
* Build a mobile app for users to make Background Burns from iPhone and Android
* Improve the speed & accuracy of the front-end editing tool
* Increase accuracy of background identification for pictures of humans.
* Work with CEO to build an image matching system to accompany the Background Burner
* Help flesh out our background replacement tool
* Optimize image processing times
See: http://www.bonanza.com/jobs/1 or email jobs@bonanza.com
The battle to get scummy dudes to behave appropriately feels in some ways like the battle to get thieves not to steal. You can tell a thief not to steal, you can describe to them how a victim feels when their house is broken into, but it just doesn't register. A certain subset of the population lacks the empathy to respond to such appeals.
If the thieving analogy holds, the only way to fix someone like the masseuse would be to threaten punishment, but good luck creating/enforcing that.
Full-Stack Rails Developer
We're looking for a full time, full stack Ruby on Rails developer to continually improve the user interface, performance, feel, and other aspects of our site to make our customers happier, save time, and have more fun buying and selling on Bonanza.com.
We’ve already built Bonanza into a leading person-to-person marketplace, but we'll never stop making it even better. Some things you’ll be responsible for might include:
* Fix bugs reported by customers and the dev team * Implement new features as needed * Learn and grow your skills under the guidance of world-class Rails coders on our dev team * Use the website regularly and contribute your own suggestions on how we can make it better
Requirements
We strongly prefer that you have some Ruby on Rails experience in a production environment. You’ll be working in the full stack, from the mysql database up to jQuery and HTML/CSS. You should be comfortable receiving sometimes-vague bug reports, and having the doggedness to track down repro steps and make an appropriate fix. You should have the empathy to see problems from our customers’ perspectives and keep their needs in mind while building solutions. An innate sense of good UX design would be super helpful in this position.
Because we’re a small and close-knit team, attitude is a critical element in our selection process. The ideal candidate will be able to speak both "geek" and "human," and will approach problems with a "can-do" attitude.
Note: If you're not currently located in the Seattle area, we're open to working remotely with a strong candidate.
Benefits
In addition to a very competitive salary, Bonanza offers the following perks:
* "Work from home Wednesday" - every Wednesday we get to work from home, coffee shops, or wherever suits us (remote staff can work from home every day!) * "Freedom February" - every February we retreat from the gloom of Seattle and work from a remote tropical locale. So far we've been to Costa Rica and Oahu. Next year we're eyeing Nicaragua. * Fast growing (averaged 50-100% yearly growth over 5 years), and already-profitable company. It's fun to work for a winner. * Work from a waterfront office in downtown Seattle (food trucks aplenty!) * Full arcade room in the office * Pong table on site * All employees get fully paid health insurance coverage, vacation benefits, holidays, stock options, and more.
Apply for this job
To apply to any of the above jobs, please email jobs -at- bonanza.com. Specify in the title the position you are applying for, and include a one page cover letter, plus your resume. We look forward to hearing from you!
We ran our forums at Bonanza for about 4 years, and had millions of posts made to them. We spent hundreds (thousands?) of hours of time building tech and training moderators.
In spite of the overwhelming effort we put into making them useful and productive, we ultimately had to concede that the folks who sought to undermine our forums had 100x the time that we did, and displayed a level of resolve (creating duplicate accounts/their own forums/blogs to pick apart our decisions) that could have been a huge asset, if not for being dedicated to subterfuge.
After seeing all this firsthand for years, I am now solidly of the belief that the Internet and productive forums are hopelessly at odds. I hope Discourse can prove me wrong. But all it takes is a small handful of people to undermine the best technology and intentions.
That Paul Graham has been able to keep HN discussions civil for years (even though I've read it causes him great consternation) is an inspiring counterexample. But I can scarcely imagine the number of cycles he and his team probably have to expend to keep the signal-to-noise ratio as high as it is here.
Getting a performance increase during an upgrade would be a highly welcomed change in our world.
Even if we just arbitrarily said "let's focus on whichever method is cumulatively taking most time," we have no reference point for whether Rails could make that method faster or not. The time taken by a method or instantiation is just some number, and whether that number is "good enough" is ultimately a judgement call in which I have little basis for comparison.
I hope I'm wrong and that there are some big obvious things to optimize, but when I've gone down these rabbit holes in the past, my experience has been that there's usually so much data and so many pieces things contributing to slowdown that it's hard to find high-impact things to fix. Especially when it comes to a framework as multilayered & complex as Rails.
The trick with pinpointing a cause is that when I look at the data NR provides, every partial rendered and every action called is slower than it had been previously. Combined with the immensity of our codebase, it's going to be time-consuming to put a finger on a single repro-able cause. But we'll do our best to isolate and report back.
FWIW, have you guys ever considered creating a performance suite test app? With such sparse Google results around Rails performance changes over time, it could be useful to compare the performance of Rails versions on an apples-to-apples basis if we could see how the performance of the test app changed over Rails versions. If we're lucky, it might even catch some of the performance regressions that have happened in the dot releases previously. Even if not, it would at least demonstrate that performance is an important consideration in Rails' evolution. I'd sleep better knowing that.
Maybe take a popular mid-sized framework like Spree and see how it performs on 3.0, 3.1, 3.2, etc.?
I think that the creatives who just cover their ears and stop listening to the reviewers have something useful figured out. There are so many channels through which feedback can travel, why bother spending time on the mean-spirited, irrational ones?
Pros: Doesn't require the fg/bg coloring step needed here, just figures out your FG without intervention. Cons: Have to register for an account to access it currently, but can use FB or Google to register
Every story I see about the supposed "tech talent crunch" makes me wince at the fact that the average web developer salary is about the same from when I started my company five years ago to now. If there's really a shortage, the makers ought to be getting paid: in dollars, not kool aid.
This isn't even to mention the "glory deficit" that goes with being an employee. With today's incubator explosion, any decent technologist can own 50%+ of their own company. If they're going to work for yours, you'd better pay them. And spend more time glorifying those who want to work as a team, rather than those that chase the CEO/Founder glory (a common blog post written by CEOs, Founders and VCs).
The FUD that CNet was able to perpetrate far outweighs any reasonable outcome that I can foresee. For this reason, I take Kevin at his word: both that they aren't going to do stupidly publish user pics on the side of buses, and that they will learn from this blunder.
Every single week it seems there is a new story from a reputable source lamenting the many billions that are being extorted by anti-innovation entities. But the conclusion of the story always seems to be: "And that's why it sucks to be in the software business." I'd much rather read "And here is what you can do if reading this made you feel depressed..."
The fact is, most of the older people I know (my parents, grandparents, etc) still listen to the music they were listening to at age 25. Many of them (such as my aunt) are still working at jobs that use technologies they learned 30 years ago. It's not because they are incapable of evolving. I think it is because they never made it a point to sharpen their openness & curiosity.
If I saw a 55 yo engineer with a Github portfolio of Ruby and Python projects, hell yes I would interview that candidate. But the reality is that when I've interviewed older candidates in the past, they are in general more likely to be behind the curve when it comes to speaking the language of the latest tech and developments. My hunch is that complacency breeds this attitude. It is hard to constantly learn new tech for 40+ years, because so much of the learning process is about being wrong repeatedly.
My solution personally is to try to constantly force myself to understand and appreciate the zeitgeist of music, programming, and design as I age. In terms of personal empowerment, it seems to me one of the most sensible routes to fight ageism.
Calling out others who promote ageism is good too, but it doesn't directly address the fact that someday we will all be old, and we'll need an actionable strategy to succeed in spite of that.
Admittedly, there is enough gray area in marketplace transactions where determining "right and wrong" can sometimes prove difficult. But I like to think that we start from a neutral POV, rather than the "buyer is always right" mentality that eBay has increasingly gravitated toward.
The author here doesn't seem to be particularly passionate about learning from his battles with Hard Problems. I don't blame him, because it's hard and painful to be in a constant battle. But for my part, I hope that I still have a taste for the pain of learning when I'm 50; the day I stop wanting to learn is the day I become bored & boring.