News for hackers. Stuff that matters.
Re:Work on interesting problems. Not interesting tech by legerdemain on Friday September 10, 2021 @03:28PM (#28485995)
Want to work on interesting problems? Build software for doctors' offices and medical groups! Help lawyers crawl out of their low-tech hole! Work on software to revolutionize public classrooms! Why work on interesting tech when you could throw yourself at intractable problems that we never get any closer to solving?
Re:Work on interesting problems. Not interesting tech by reureu on Friday September 10, 2021 @06:12PM (#28487488)
> Build software for doctors' offices and medical groups!

Please please please go into these areas with humility. Having worked for health tech companies in SF for a decade, I've seen so many people come from Google/Facebook/Mozilla/Ticketmaster/eBay to healthcare in order to "disrupt" and "fix" it. Their disruption or fixes are many times illegal, impractical, vaporware, or completely ignore industry standards and so can't speak the same language as all the other tools in the ecosystem. It generally doesn't end well if you don't deeply partner with stakeholders and domain experts.

Re:Work on interesting problems. Not interesting tech by toomanyducks on Friday September 10, 2021 @08:10PM (#28488255)
The above x100. Technology isn't a cheat code for a hard problem, it's just another tool. When we assume that tech fixes everything with no further research, everyone gets a lot worse off.
Re:Work on interesting problems. Not interesting tech by bloodyplonker22 on Friday September 10, 2021 @06:34PM (#28487654)
I heard some woman with a fake deep voice is on trial now.
Re:Work on interesting problems. Not interesting tech by reureu on Friday September 10, 2021 @06:45PM (#28487724)
I haven't been following that situation, I'm too focused on getting my insurance company to pay to sequence my poop.
Re:Work on interesting problems. Not interesting tech by cutemonster on Sunday September 12, 2021 @04:41AM (#28499524)
> insurance company to pay to sequence my poop.

What's that about?

Re:Work on interesting problems. Not interesting tech by reureu on Sunday September 12, 2021 @03:56PM (#28504341)
uBiome— you’d send fecal samples to them and they’d sequence and tell you what bacteria you have. They claimed to have clinical value and started billing insurance, before eventually being raided and shut down for something along the lines of insurance fraud.
Re:Work on interesting problems. Not interesting tech by cutemonster on Monday September 13, 2021 @08:12AM (#28510474)
Aha, such odd behavior by them
Re:Work on interesting problems. Not interesting tech by vishnugupta on Saturday September 11, 2021 @01:54AM (#28489713)
This is why I keep emphasising on "domain knowledge". As an engineer my domain knowledge is zero when I wade into a new problem space.

A good way to approach is to partner with a domain expert to understand the following aspects.

  1. Know about various stake holders that make up a business process. Understand each of their incentives. Some actors standout explicitly but some do not, such as regulators.
  2. The value add by different player/stake holder in the chain.
  3. Location of power centres. No one will explicitly call it out but you will be able to figure it out.
Now pick one stake holder or actor, go deep into their problems, and see how you can make their life easier without disrupting rest of the actors. This latter part is important. If there are three actors (A, B, and C) and your solution is intended to make life easy for "A" but requires B and C to disrupt their workflow without them getting anything in return then it'll be that much difficult for your solution to be adopted.

Also, at the end of the day automation is making someone (or part of someone) redundant. Make sure you identify that person and be subtle about your messaging to them.

All of this takes time so in olden days there used to be a role called "system analysts". Their job was to go deep into the problem domain, untangle all the above for you and help you define product. These analysts are typically ex-workers in the same domain so they have seen everything first hand. Given the nature of their job their role is not fungible in that you can't take one person and make them move around to be system analyst in different domains. Somewhere along the way system analyst role disappeared and they were replaced by fungible "product managers". These PMs have a generic set of product development skills such as UX, user retention optimisation etc., But they lack the domain knowledge. And they are expected to be fungible. If a PM changes job once every 3 years into a different domain they can at best do a superficial job.

Of the top of my head here are two examples.

There's this software called Docon (https://docon.co.in) used by small-setup medical doctors and physicians. The value add for doctors is very clear. It saves them time and all the hassle. What is good about Docon is it requires zero actions by the patient or any one else. So Doctors are happy to be using it. It is a nifty little tool to automate key parts of doctors' workflow.

Now let me talk about JIRA. It is mainly targeted towards management and execs. Because, let's face it, they have a genuine problem of not having clear view into project development state. They can't see how their quarterly projects are shaping up at different zoom levels. To that end I would say JIRA does a reasonably good job. Where JIRA fails spectacularly is it requires leaf level works to massively disrupt their workflow. Not only does it require them to use JIRA for daily updates and what not it also forces a way of agile development which comes with its own set of baggages.

Re:Work on interesting problems. Not interesting tech by iancmceachern on Saturday September 11, 2021 @01:01AM (#28489548)
Exactly this. I've seen it personally repeatedly.
Re:Work on interesting problems. Not interesting tech by faeyanpiraat on Friday September 10, 2021 @07:33PM (#28488032)
Can you give some examples for illegal stuff?
Re:Work on interesting problems. Not interesting tech by reureu on Friday September 10, 2021 @11:33PM (#28489227)
Theranos, uBiome, and Practice Fusion all have well known scandals. I'm aware of other issues at some other health tech startups surrounding misrepresenting their impact on quality of care, building biased algorithms that have a discriminatory impact on care delivery, companies looking at questionable payment models that seem like they'd violate stark laws, straight up medicare fraud, etc. I'll just say that I'm skeptical of health tech companies that claim/suggest any impact on a medical condition, that claim to have a predictive algorithm related to a medical condition that's their core product, or that somehow give free things to providers.
Re:Work on interesting problems. Not interesting tech by elcritch on Saturday September 11, 2021 @03:01AM (#28489951)
To be fair I'd take that list and expand it to include the big pharmaceutical companies (see the new Alzheimers drug scandal at the FDA, billions spent on next generation statins that proved ineffective by confusing correlation and causation, etc), to include doctors and surgeons and various surgical practices or novel medical treatments (billions spent on full Meniscectomies that just lead to arthritis after years, pointless heart stints, etc).

True many startups in health are trying scammy payment models, but hospital bills often aren't much better unfortunately.

Personally my life has been positively improved by 23andme when they could still list health research, or by "zany" microbiome/probiotics startups years before the medical establishment caught up. Obviously these fields should be regulated, but properly so without just providing an excuse for regulatory capture for existing players.

0: https://www.nytimes.com/2021/07/19/health/alzheimers-drug-ad... 1: https://www.crossfit.com/health/the-great-statin-scam-time-t... 2: https://www.vox.com/the-big-idea/2017/12/28/16823266/medical... 3: https://www.theatlantic.com/health/archive/2017/02/when-evid...

Re:Work on interesting problems. Not interesting tech by iancmceachern on Saturday September 11, 2021 @01:31AM (#28489640)
Not following applicable standards like IEC 62304, 60601, etc.

https://en.m.wikipedia.org/wiki/IEC_62304

https://en.m.wikipedia.org/wiki/IEC_60601

Re:Work on interesting problems. Not interesting tech by outside1234 on Friday September 10, 2021 @07:54PM (#28488180)
Re:Work on interesting problems. Not interesting tech by dboreham on Saturday September 11, 2021 @12:33AM (#28489444)
Better bring a FAX machine..
Re:Work on interesting problems. Not interesting tech by reureu on Saturday September 11, 2021 @02:08PM (#28494271)
This comment exemplifies my point.

Faxes are common in healthcare, and it's a common punch line from newcomers. But there's a series of standards that have been iterated on since the late 80s/early 90s that are finally getting to a place where they can eliminate faxes. There's standards for how to transmit data between EHRs, standards for how to store and represent data, and a standard API for 3rd parties to be able to write/read that data.

Regardless of these standards, you can already share data between hospitals using the same EHR -- so epic-to-epic (epic is the largest EHR vendor in the US) data sharing has been happening for a decade without any faxes. Unfortunately, there's a ton of different players in this game, so getting to a place where everyone has adopted the standards takes a long time, and the system still needs to keep running while this switch happens. To be clear, this is a common problem throughout tech: is it possible to run a native android app on iPhone? Do you think Google and Apple will ever make it possible to do that?

I can think of at least one medical company that builds their own technology and managed to paint themselves into a corner by not working from within the system. They just hire a bunch of engineers, who hear about how faxes run healthcare, so they say "cool, I can digitize the faxes" without bothering to consider or learn about other standards that are being developed. This leads to proprietary data models, with proprietary data representation, all transmitted using outdated technology. The engineers quit and go back to non-health tech, and tell their friends that health tech is so frustrating because it's so dated (make sure to bring your fax machine when you start your new job!).

But, really, the problem was never faxes. The problem is that healthcare is way more complicated, with way more stakeholders than consumer tech. You can't just launch a new product and iterate on the bugs later; people's lives are at stake, so the whole industry is heavily regulated. But if you enter with humility, recognizing that there is too much information for one person to know, but know that your skills are welcomed and needed. Take time to learn about things like HL7, FHIR, and clinical ontologies. And partner-- not just a quick knowledge sharing session-- actually partner with the domain experts, then there's a whole world of fascinating possibility out there.

Re:Work on interesting problems. Not interesting tech by lifeisstillgood on Friday September 10, 2021 @04:10PM (#28486357)
I was talking to my physio today (doing fine thanks for asking), and she was fed up about having to prove that a client had not paid her - manually matching payments into her bank account with appointments etc. It wasted an hour of her time or more.

Now the heart of that is 5 lines of python. It could be written by anyone after a days "starting from zero" coding experience.

But actually solving that in real world is a mess of just trying to access the data - it's her data and she only wants to see her bits. But the level of effort is ridiculous.

Anyway my point is that solving problems like software for doctor's offices is not the point - that's just building another silo. A doctor who has (secure) access to a industry wide common open data layer can do all the work to run their office themselves.

In short we are trying to solve the wrong problem - usually because proprietary code is not a profitable as proprietary data

Re:Work on interesting problems. Not interesting tech by MontyCarloHall on Friday September 10, 2021 @05:42PM (#28487226)
> usually because proprietary code is not a[s] profitable as proprietary data

Bingo. This is why Google et al. would never sell your data; they just keep it for themselves and merely sell to advertisers the ability to precisely target you (“pick a demographic down to the shampoo brand and we can target your ads to it”). But those advertisers (or anyone else) will never see a single iota of your data. It’s simply too valuable.

Re:Work on interesting problems. Not interesting tech by datameta on Friday September 10, 2021 @08:20PM (#28488313)
In a weird kafkaesque way this makes me feel better about my data.
Re:Work on interesting problems. Not interesting tech by amelius on Friday September 10, 2021 @08:32PM (#28488361)
Now when you click an ad, the advertiser knows which shampoo brand you use.

Next, when you click an ad, the advertiser knows which medical problems you have (because that's where they targeted their ad at).

Google has a data leak, and nobody seems to care about it.

Re:Work on interesting problems. Not interesting tech by datameta on Friday September 10, 2021 @08:39PM (#28488415)
Luckily I haven't clicked an ad in a decade!
Re:Work on interesting problems. Not interesting tech by mbrodersen on Friday September 10, 2021 @10:22PM (#28488938)
Easy. Don’t click ads.
Re:Work on interesting problems. Not interesting tech by kyleee on Friday September 10, 2021 @11:23PM (#28489181)
And beyond that, block them ruthlessly without a second thought
Re:Work on interesting problems. Not interesting tech by fma on Friday September 10, 2021 @07:15PM (#28487921)
Sounds like she just needs to sign up for something like Square where your customers set an appointment, order services and pay and invoice. They can even be asked to pay before hand.

Square is not the only player doing service appointment payments.

Re:Work on interesting problems. Not interesting tech by lifeisstillgood on Friday September 10, 2021 @07:51PM (#28488153)
That's very much not my point. What you are describing is the square development team taking their representation of a client, an invoice, a payment event and so on, and then they guess a feature like match up invoices and develop it and write a gui and hide it somewhere and...

But we (society) should have a standard representation of a calendar event, standard access to bank accounts and so on so that all she needs to go is write five lines

Once the data is free we won't need proprietary co e

Re:Work on interesting problems. Not interesting tech by tuatoru on Friday September 10, 2021 @07:46PM (#28488118)
The reason that people don't do the "obvious" thing is rarely that they're ignorant or stupid. Best not to assume that you know all the relevant context.
Re:Work on interesting problems. Not interesting tech by fma on Sunday September 12, 2021 @10:44AM (#28501599)
Why do you assume this is the obvious thing? Maybe you shouldn't assume till you know all the relevant context?

I have a brick and mortar small business that takes appointments, have monthly recurring services and did not use Square appointments. We did everything manually to handle calendar appointments, invoice, charging for payments. Found out after a few months the time is not worth the savings and rather just get a service like Square. I thought maybe his client was the same and was trying to help.

But hey maybe Square was very obvious for your brick and mortar service based business and I'm one of the few "ignorant and stupid one".

Re:Work on interesting problems. Not interesting tech by philipswood on Saturday September 11, 2021 @12:48AM (#28489505)
Interesting definition of "interesting" you're using there.

I don't think he was necessarily saying that you should sacrifice yourself to your own idea of the pointless "greater noble good".

Build a stamp database, an app to record baseball cards, automatically conjugate latin verbs, make a recipe database that can give you a list of what can be made with a given set of ingredients, make a 3d anatomical viewer based on the BodyPart3D database, make a catalog of open source projects for a given combination of JavaScript technologies, make a periodic table that shows the 3D orbital structure of the atom involved, calculate and visualise knitting patterns, simulate an H-Bomb or global thermonuclear war...

Do it in Golang, write it in Rust or Haskell or PHP, or with a shell script if you have to...

Run it on baremetal, on a VM, in a unikernel, deploy it in a k8s cluster, or nomad, or docker-compose or host it on a microcontroller if that fits...

But for a change focus on the problem and not the tools.

Re:Work on interesting problems. Not interesting tech by xfer on Saturday September 11, 2021 @01:11AM (#28489575)
Tools are also problems for some people, they don't exist magically. If nobody cared about tools we would be writing machine code.
Re:Work on interesting problems. Not interesting tech by pasabagi on Friday September 10, 2021 @05:45PM (#28487250)
I think with lawyers, the problem is basically GUIs. Because most computer users, even very high-skilled computer users like lawyers, are used to consuming software in the form of GUIs, you tend to get these kind of all-encompassing WYSIWYG programs like Word, with mysterious internals, and an endless labyrinth of useful tricks that lawyers tend to know, which are in one way amazing, but in another way essentially limited by the imaginations of the programmers, because they're monolithic and basically inflexible.

This is basically an education / culture problem. I'm sure in two hundred years, people will recognize that 'sort' or 'uniq' is really elemental functionality like a saw or a hammer, and baking it all into one giant saw-hammer-sanding machine that's really only good for making tables, and occasionally eats your cat, is just not the way to go. Until that point, I don't think that some plucky new startup is going to magic away all the problems. I mean, obviously there are some crazy low-hanging fruit out there, but the fundamental issue starts with how people are using computers in the first place.

Re:Work on interesting problems. Not interesting tech by smt88 on Friday September 10, 2021 @05:27PM (#28487081)
Most people in software seem to create interesting technology that sells ads, so your sarcastic examples sound a lot better to me.

I'm currently building a company that is replacing Excel at some of the biggest commercial real estate firms, which is "impossible" by your standards.

Re:Work on interesting problems. Not interesting tech by ie21 on Saturday September 11, 2021 @05:04AM (#28490502)
Honestly curious, why is it better for them then Excel? What is the value proposition? Thanks.
Re:Work on interesting problems. Not interesting tech by bumby on Friday September 10, 2021 @04:37PM (#28486600)
Man, I sure am glad Curtis and the Wright brothers didn't take this stance after Lord Kelvin claimed "Heavier-than-air flying machines are impossible" before they proved him wrong less than 20 years later.

Or NASA when Lee Deforest claimed flight to the moon was impossible "regardless of all future advances."

Or when Einstein claimed ""There is not the slightest indication that nuclear energy will ever be obtainable."

Etc. etc.

Re:Work on interesting problems. Not interesting tech by hirvi74 on Friday September 10, 2021 @05:23PM (#28487039)
> when Einstein claimed ""There is not the slightest indication that nuclear energy will ever be obtainable."

Not to be pedantic, but was Einstein incorrect at that time/in the future? Were there any actual indications that nuclear energy would be obtainable at that time?

Einstein didn't seem to say, "Obtaining nuclear energy is absolutely impossible, and can never be achieved." All he said was that there is not the _slightest indication_.

I am sorry if this comes off as being semantical, but I just want to make sure I am not misinterpreting you or what Einstein said.

As for the other points, yes. Those were great examples.

Re:Work on interesting problems. Not interesting tech by marcosdumay on Friday September 10, 2021 @11:49PM (#28489294)
Ok, so libquote says this was stated at 1934, what is after the discovery of Uranium fission and that it emits neutrons that could start further fissions.

The quote is of course completely out of context, and looks a lot like something one throws at annoyingly overeagle people. Also, I imagine the context for saying it only existed because nuclear fission seemed perfectly plausible and just over the horizon. It was technically correct, nobody could imagine a Manhattan Project at that time, and it wasn't obvious that it was even possible, but there was a clear possibility.

Re:Work on interesting problems. Not interesting tech by bumby on Saturday September 11, 2021 @07:48AM (#28491162)
>nobody could imagine a Manhattan Project at that time, and it wasn't obvious that it was even possible, but there was a clear possibility.

That’s exactly the point. And yet the Manhattan project was less than a decade away.

Lord Kelvin said his quote in 1895. Deforest said his in 1926. In the myopic timeframe they were all technically correct.*

The GP stated that all those other problems were “obviously” intractable, but whose to say they won’t be solved under some ambitious effort in the next 20 years?

*Aside: All three examples come from the same place in terms of being plausible in the timeframe they were made yet wrong in hindsight. I wonder if people are more fiercely defending the Einstein quote because he’s more revered in popular culture. It’s interesting that his quote is the only one being defended.

Re:Work on interesting problems. Not interesting tech by marcosdumay on Saturday September 11, 2021 @08:10AM (#28491307)
Oh, your comment is spot on.

I guess my point is only that all those famous quotes probably just meant "shut-up and give me some space, journalist, I have some immediately pressing problems to solve", and probably nobody undesrtood them as anything else at the time too.

Anyway, my favorite of those is the Michelson's famous "physics is complete" one, that basically meant "let me do the experiment first, then we can talk about the results", but is excellent out of context.

Re:Work on interesting problems. Not interesting tech by gpsx on Friday September 10, 2021 @08:05PM (#28488236)
I assume this statement was made not long after Einstein discovered the equivalence between mass and energy, so it's understandable it may not have been obvious at the time that we could generate power that way.
Re:Work on interesting problems. Not interesting tech by bumby on Friday September 10, 2021 @05:48PM (#28487271)
I guess it's hard to tell without over-parsing his words, but you bring up an important distinction.

It may be fair to read it as a scientist essentially saying "we have no evidence it's possible." But as I read it, the addition of "ever" came across as saying he thought it was an unsolvable problem rather than one that had yet to come upon a solution.

Re:Work on interesting problems. Not interesting tech by smoldesu on Friday September 10, 2021 @06:21PM (#28487555)
The Wright brothers didn't get off the ground by gluing wings to their arms, and Einstein didn't discover the theory of relativity in his study of alchemy. Entertaining silly or stupid ideas is risky, and for every Wright brother there's another 100 failed entrepreneurs who lost everything trying to make that dream a reality.
Re:Work on interesting problems. Not interesting tech by bernulli on Friday September 10, 2021 @09:27PM (#28488671)
Case in point: Lilienthal, who wrote the aerodynamics book that inspired much of the wing building of the Wrights, died when he crashed with one of his gliders.

Amazing book by the way, there was a cheap reprint published a few years ago.

Re:Work on interesting problems. Not interesting tech by bumby on Friday September 10, 2021 @11:13PM (#28489146)
That comes across as straw manning. The point is that all kinds of problems are seen as intractable to the cynic, not that every optimist has the correct approach to solve the problem.

It’s easy and weak to just throw up ones hands and say it’s too hard but I don’t want to live in a society where 100% of people take that approach.

Re:Work on interesting problems. Not interesting tech by 1vuio0pswjnm7 on Friday September 10, 2021 @11:41PM (#28489261)
The parent comment does not actually define any specific problem.

"Build software for doctors' offices and medical groups!"

A problem that needs to be solved is _____________?

"Help lawyers crawl out of their low-tech holes!"

A problem that needs to be solved is _____________?

"Work on software to revolutionise public classrooms!"

A problem that needs to be solved is _____________?

Let us know when can provide even a single answer to any of these questions.

As other commenters point out, answering them means actually talking the people who will be using the software, or working in their shoes in these industries, before anyone starts programming anything.

Re:Work on interesting problems. Not interesting tech by LegitShady on Friday September 10, 2021 @11:45PM (#28489278)
Those are a set of questions with many answers - each answer might be a totally different business. If there was only one answer then all the software would be written already.
Re:Work on interesting problems. Not interesting tech by ummwhat on Friday September 10, 2021 @08:35PM (#28488386)
Those are the types of problems which I describe as "solving the problem is half the problem". Anyone can easily write the fixes to these sorts of problems. They don't because the real complication isn't the surface level obstacle.
Re:Work on interesting problems. Not interesting tech by nickjj on Friday September 10, 2021 @05:30PM (#28487105)
Indeed, there's lots of great problems to solve in this space.

If anyone is interested I recorded a 90 minute podcast with a lead developer + ops engineer who created a custom electronic medical record system for an Ophthalmology clinic (eye care).

It's at: https://runninginproduction.com/podcast/99-a-custom-electron...

We talked all about using Rails to help consolidate 9 separate 3rd party solutions into a monolithic server rendered Rails app that the clinic uses internally to manage all of their patients. We also chatted about transitioning from Elastic Beanstalk to self managed EC2 instances to using Kubernetes with EKS.

Re:Work on interesting problems. Not interesting tech by andrepd on Friday September 10, 2021 @06:17PM (#28487535)
The problem is that advertising or finance companies can outbid public classrooms and students 10000:1. It's the sad reality: in the current system finding ever more sophisticated ways to get people to buy more crap is very profitable, helping underprivileged students succeed is not.
Re:Work on interesting problems. Not interesting tech by q-big on Friday September 10, 2021 @07:01PM (#28487833)
If you seriously want to target classrooms (selling to the education sector is hard), target elite schools rather than poor public classrooms with underprivileged students. This way, at least potentially money could be made.
Re:Work on interesting problems. Not interesting tech by Existenceblinks on Friday September 10, 2021 @05:21PM (#28487024)
And many times, better solution is not to use software at all. People don't need to leave Excel or Wordpress at all. I don't even think using paper is a problem. They have pros and cons. "solution looking for problems" is actually accurate, ironically.
Re:Work on interesting problems. Not interesting tech by bob1029 on Friday September 10, 2021 @05:45PM (#28487247)
We're doing this kind of thing in banking right now. Would like to attack medical and insurance next.
Re:Work on interesting problems. Not interesting tech by endisneigh on Friday September 10, 2021 @06:04PM (#28487419)
What a defeatist mindset lol
Re:Work on interesting problems. Not interesting tech by xwdv on Friday September 10, 2021 @11:59PM (#28489330)
Why? Because I don’t give a damn I’m just here to write code and make piles of money and interesting tech makes it less dull.
Re:Work on interesting problems. Not interesting tech by treeman79 on Friday September 10, 2021 @06:43PM (#28487710)
Hippa compliance...

Development is a nightmare

Re:Work on interesting problems. Not interesting tech by Spivak on Saturday September 11, 2021 @02:33AM (#28489851)
HIPAA isn’t really that bad. If you’re following normal good security practices at your company you’re probably at the point where becoming complaint is more about implementing a bunch of small mostly meaningless changes to your infra and documenting stuff than some fundamental change to your architecture.
Re:Work on interesting problems. Not interesting tech by vangelis on Friday September 10, 2021 @07:02PM (#28487838)
Thankfully we only have to worry about HIPAA.