Hacker Newsnew | comments | show | ask | jobs | submit | petethomas's comments login

Watching the GSN video on YouTube I was struck by the generic presentation of non-cash prizes. Press Your Luck was apparently content to just mention the contestant won a "Sailboat" without tethering it to a brand which seems like overlooked opportunity even for the simpler time since contemporaries like The Price Is Right were integrating brands into their show.


I'm not aware of a JS adapter for clara rules but per the wiki it does offer ClojureScript support "with a couple constraints"[1]

[1] https://github.com/rbrush/clara-rules/wiki/ClojureScript


Kansas City, MO

C2FO - https://c2fo.com - hiring software engineers.

Our name stands for "Collaborative Cash Flow Optimization" and we maintain a web platform that dynamically prices working capital so companies of any size can connect with each other to meet cash flow needs without involving traditional financial intermediaries like banks or financial factors.

The platform runs as a marketplace similar to a stock exchange where the assets considered are approved invoices. We work mainly in JavaScript and particularly node.js; our open source projects are available at https://github.com/C2FO. We also have some great investors on board including Mithril Capital Management, Summerhill Venture Partners, and Union Square Ventures.

More about the openings at https://github.com/C2FO/jobs


One question perhaps worth asking: Why do this piece and the many similarly tiresome pieces preceding it mostly fail to mention how higher salaries offered would motivate graduates and other unemployed people to acquire these missing skills?

Put a different way, fifteen or so years ago: "Economists who have studied occupational shortages generally hold the view that in an unconstrained market, supply will equal demand at the 'true' market price. If demand exceeds supply, salaries will be bid up until the market clears." [1]

Also of interest but perhaps unrelated, "At Goldman Sachs and JPMorgan Chase average pay slipped by about 5% in the first nine months of last year, a figure that is probably representative of the wider industry." [2]

[1] http://www.bls.gov/mlr/1999/03/art2full.pdf

[2] http://www.economist.com/news/finance-and-economics/21592642...


In Europe, money isn't everything, especially for youngsters choosing to study for an academic degree. The idea of "following your dreams" or studying what you like is still big. Because studying is often subsidized, people can make that choice easily because they won't have an enormous amount of dept in return for a "worthless" degree. Before the crisis finding a job with whatever degree wasn't hard and the previous crisis (1980s) didn't do much to prevent choosing "worthless" degrees either.

Most of the people growing up since the late 1960s have had the possibility to do whatever they wanted without regard for future earnings and sustainability of their lives. Just re-schooling people with degrees in the humanities, fun-studies, social sciences, and so on to science, technology and engineering sounds easier than it is for these people have made conscious choices to neglect and dismiss mathematics and science courses since leaving primary school. To some degree, their whole social and cultural being seems to be incompatible with that of science and technology.


EditGrid is still around and free and unlike Google Spreadsheet's broken importXML function (see: http://goo.gl/fWYDi) it has a web_xpath function that mostly works.

Also worth noting DabbleDB is one of the (few?) relatively well-known projects implemented in Squeak/Seaside as discussed here: http://www.jarober.com/blog/blogView?showComments=true&t...


I am very glad they got Seaside out before the sale: it has really helped to revitalize Smalltalk.


Seaside was pre-DabbleDB as far as I can tell from following the framework when it was in it's youth.


Also WSJ's "From Diapers to 'Depends': Marketers Discreetly Retool for Aging Boomers" http://online.wsj.com/article/SB1000142405274870401360457610...




According to Rapleaf's blog, this site has a bunch of opt out cookies you can use: http://www.networkadvertising.org/managing/opt_out.asp

Nice find. Opting out by email doesn't seem that useful though. I probably have 20+ emails associated with my person, and figuring them all out will be a lot of work.

There needs to be some kind of statutory privacy protection that targets both keepers of such information and consumers of the information.


To be bypassed at all times by anyone interested in making a buck on others' data, with a bit less in the way of scruples.

You cannot prevent it all, and not all of it is even illegitimate - how can you tell the difference, if not on a case-by-case, human-decided basis? In which case, the cost would be astronomical; I'm not paying it. It'd be wrong sometimes anyway. At best, you can make it difficult for legitimate uses to exist, and do only a little to slow the illegitimate. And push them underground, making finding and stopping them harder than it already is.

Heck, Facebook can be seen as a massive deanonymizer, and they exposed way more (and more accurate) info about me publicly through their API. Their ads were horrendously inaccurate, but prior to deleting my account they were probably the most accurate measure of "me" online by an order of magnitude. And any attempt to restrict public access to the data - useful for a number of services / applications - would make lots of legitimate uses impossible.


It likely depends on what kind of B2B service you are promoting, the size of the companies you are targeting, and how deeply your service needs to integrate with the target customers' existing software systems. In my experience marketing to businesses via the same channels that work well for consumer web products is no easy task.

Give serious consideration to making a real effort to discover, meet, interview, get to know, perhaps even partner with a talented salesperson with great personal and/or professional connections in the industry you're trying to reach.

Here are a couple posts that you might find useful:




I couldn't locate a direct link but the "full 28 page report" is viewable and downloadable as a PDF via docstoc on the CB Insights blog: http://www.cbinsights.com/blog/venture-capital/venture-capit...


The main advantage of one-database-per-business-customer isn't isolating customer data, it's the ability to serve business customers who are willing to pay for heavy customizations and the extra support those entail, while not polluting your core offering through the introduction of attributes, features, etc. for which other customers will have no use.

For a lot of B2B web applications aimed at serving "bigger" companies, customer adoption can still hinge on scotch-sipping and rounds of golf more than well-placed sign-up buttons or great viral marketing campaigns. It's been argued of late that maybe this part of the industry is becoming more "web-like"[1], but in any case it's not very web-like yet, when it comes to sealing deals.

Many times the companies who were convinced by your talented sales team to buy your product eventually demand that the product be tailored to their (sometimes very company-specific) needs. If you want to keep the customer happy, or maybe just keep the customer, you have to keep customizing.

One could make the argument that the most talented sales teams are the ones that sign deals with customers who are willing to "stay on core", but over time as your customers' own businesses evolve, the challenge grows for everyone involved.

[1] http://techcrunch.com/2010/07/25/enterprise-software-is-sexy...


    it's the ability to serve business customers who are 
    willing to pay for heavy customizations and the extra
    support those entail
You'd need to have flags in the app itself, which would likely turn into an unmaintainable monstrosity. If you have a handful of large clients, are heavily customizing the app for each one, are using a modern framework like Django or Rails and a DVCS, the obvious maintainable approach is to have full individual installs, forks for each install and a modular application that pushes the customizations into pluggable components as much as possible.


Having a shared core and a lot of hooks for customization is the road we have taken for our application. I've written a lengthy post about it just last friday:



Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact