241–250 of 734 posts
A family member is a lawyer in the Worker's Comp, SS, and Family Law space. THE software for lawyers in this space is called A1 Law. It solves a lot of real problems lawyers in that space have (form letter generation, calendar integration, case management)... but it's so slow to use new technologies. They advertise PalmOS integration. My family member has to have their own server in a closet running the server versio…
A monthly subscription service for a fee of $5 - $10 where every month I get a new kind of quirky instrument (shaker, wind, wood block and stick, whistle, triangle, or other noise maker) as a surprise by mail. The point of the service in the music industry is to inspire new sounds and the device can either be kept or given away to somebody without a lot of second thought. Getting stuck is a big problem. Also in music…
I posted a similar question last year great discussion there too. https://news.ycombinator.com/item?id=9799007 I would suggest we make a monthly of these as they provide important insight into industries.
A cheap durable texting cel phone with long battery life for use as a pager. Edit: probably without android.
In real estate, developing with MLS data. - There are over 900 regional MLS providers each with different schemas. - You use RETS, a complicated, non web standards interface for downloading data. - MLS data is plagued with errors and denormalized data making queries difficult.
A ticketing system that doesn't sux (I like RequestTracker, but it shows its age). Top players are ridiculously overpriced. My management style is like this: every task/request is numbered, placed in a queue and assigned to a professional. What I expect from my ticketing system: - every manager should be able to assign tasks to someone and set the order they must be executed. He needs know what his team is doing and…
Personally, I think the optimal ticket system would have this data for each ticket:
* A unique, prefixed ticket # (JIRA gets this right)
* An assignee (like an email To:)
* A reporter (like an email From:)
* A one-line summary (like an email Subject:)
* A multi-line body (like an email body, but ideally with markdown)
* Attachments (like email attachments)
* History for edits of all of these (not like email!)
That's it! It really is basically email, but with a unique ID, and editable with history instead of immutable with replies, and a decent UI, perhaps RSS + notifications.
Unfortunately, everybody else seems to think that their ticketing system should embody their vaguely defined and ever-changing workflow, prioritization, approval, and release management system, so they want to be able to add any number of possible statuses, approvals, workflows and and all the rest. Once you add that, you end up with another JIRA or ClearQuest or BugZilla, and the cycle repeats itself.
The problem: privlidged access management and auditing.
The solution: Cyberark, but not $250k to cover 1,000 servers. Ain't nobody got money for that.
Earlier quoted context omitted.
Isn't a toaster oven a solution to this?
Sure, but it's very space and energy inefficient.
For toast it may be energy inefficient. But if I'm just making a small pizza, etc, it's way better than turning on the large oven.
Earlier quoted context omitted.
I'm actually close to launching this kind of product. A bit more complex than Word + Git, but I hope it will be worth it. One question: is there a use case for live group-editing? Same way live code editors work. I have to admit that I'm not super familiar of the workflows in that industry, so I am mostly just designing features the way I would like them to work.
I ran into this exact problem when selling my company. It's horrible. How far along is the product? Have you talked to any lawyers about it?
The MVP is mostly targeted at businesses who have to sign/generate contracts at scale. There's a lot of features for those use cases, and then there's features for users that the parent is talking about (pure contract-drafting).
I have not talked to any lawyers yet. I think the worst part is that I don't even know how good the computer-skills of lawyers are, so... designing features by my competence feels wrong. Since I can design the UI to match the general structure of a contract, there's a lot that I can add to make the user's life easier, but it also adds more for the user to learn.
Lots of services solved the just sending email part. And lots of mailchimp type services offer a complete product geared towards marketers. Not much in between and most existing players have laughably poor APIs that make custom integrations and extensions painful.