I'm local to the area of the company. Peeps in the community here have said they issue ridiculous old or underpowered laptops for many positions and that many if not all of those 30 employees are likely using their personal machines because they're more comfortable to the employee.
Unsupervised | Software Engineers | Full-time | US Remote or Boulder, Colorado
Unsupervised is an AI driven data analysis company. We run an unsupervised learning engine we built in-house to do a lot of analysis on customer data. The value (according to customers) is the insights we find that help them take action in their organization to move the needle on their metrics, things that matter to them and their goals.
We're hiring software engineers to work on our core compute engine and web interface. In the web app we use React and Graphql via apollo-server and TypeScript server-side, speaking to GRPC services we write in Go and Rust. In the compute engine, we're largely Python and C++. You don't need to know those coming in as long as you can learn it fast enough. On the compute side, Dask and Ray experience is a plus. You definitely need to know data structures and graphs enough to talk shop about them. We deploy on Kubernetes in a cloud native modern dev workflow, but we'll happily train what you need to know there, we've got decent tooling in place to make it very approachable and iterative.
Unsupervised | Software Engineers | Full-time | US Remote or Boulder, Colorado
Unsupervised is a Data Capitalization Management company. We help organizations find actionable insights in their data so they can make their data more of a measurable asset (think extreme leverage from data science). We do this by using an unsupervised learning engine we built in-house to do a lot of analysis on their data.
We're hiring software engineers to work on our core compute engine and web interface. In the web app we use React and Graphql via Graphene (Python Graphql server). In the compute engine, we're largely Python and C++, but you don't need to know those coming in as long as you can learn it fast enough. On the compute side, Dask and Ray experience is a plus. You definitely need to know data structures and graphs enough to talk shop about them. We deploy on Kubernetes in a cloud native modern dev workflow, but we'll happily train what you need to know there, we've got decent tooling in place to make it very approachable and iterative.
The vast majority of businesses are not going to fit any of this playbook. The problem is this playbook covers a niche. If you don't want to play that niche game, that's totally fine. However, like me, you will have to look elsewhere to decide what game you DO want to play, and what rules you'll have to live by. Sometimes that's customer focus, sometime's that is volume focus, or diversifying, or a 12 month profitability plan (sometimes longer, like maybe a restaurant).
There's no rules in business but the laws of the land. Pretending that there's one definition of success is very limiting to both focus and opportunity for all of us.
We started our company because I could fund it out of pocket for less than the cost of coffee or lunch for a week, and grow at whatever pace made sense. Even if we only occupy 0.1% of the market ever, we'll be able to pay the salaries of ourselves and our friends and have a lot of room to spare into other projects that we think should be made but probably need more development up front.
This isn't exactly an HN love story, but it's working out well for us so far, and we're learning a lot. I can't say I regret it, and at the moment I know that I would regret if I had gone after funding of some sort. Right now it's just me and the customer, working out who needs what. Third legs need not apply.
I do two things for this. One, I have a separate phone line that I largely ignore, and I give this as my main contact line for people or businesses that I have no dire need to talk to. Best Buy, for instance. If it's important, they'll leave a voicemail. This started as a land line, that was expensive but I needed DSL anyway (this was 10 years ago). It moved to a cell phone with basic service.
Fees sucked, so I started (shameless plug) Phone Janitor[1] to give me better filtering. This allows me to check voicemail anywhere, unlike my cell line (unless I sign up for their service) and just transferred it to my own company. Turns out this helps a lot of other folks with similar privacy desires. Control is a wonderful thing.
Ultimately it's really, really crappy, but the Telecoms and the FCC don't want to be too heavy handed in this, and advertisers are finding new ways of skirting the donotcall rules. They ruined SMS in this regard[2] as well, deliberately.
"People" in this instance is a handful of special edge cases compared to the majority of computer users, even if we're only looking at people that build their own computer, or hell, even just looking at only linux users. Dual booting is a minority. Yes, you CAN do it. Linux has made it easy. Great! But not many DO.
Nobody gives hell to every other OS manufacturer that will clobber our current bootloader configs. That means more than OSX, btw.
I don't buy it. The US is bringing their cases to protect their interests and the interests of their economies. It's not about territory control, it's about industry control. I don't agree with how they're going about it, but I'm not going to make up motivations that don't fit just because of my disdain for it.
Of course, this is one reason why I'm not in politics.
>It's not about territory control, it's about industry control.
He's talking about application of laws in foreign territories. Naturally, for the benefit of US and its own industry. How is that substantially different from what you're saying?
Every day we're hearing about another country attempting to apply it's laws on people not in the country. I've seen Canada, France, Germany. The US is huge in this, but they're hardly alone.
This opens up my mind to a lot of possibilities. Some poignant conversation starters for your local lunch group:
- What kind of investment returns did the stock of those bankrupted yellow pages make and at what cycles?
- What does it really take to kill an old technology?
- Is there a way to compete with established dying tech companies at their own game, or is it purely by trying to advance their users to your new tech?
- What does this say about transitional companies that possibly offer both the old AND the new techs, like the yellow pages that offer online versions? Are they going to move forward or are they just delaying their deaths a bit?
- What kind of talent is needed to sustain these kinds of businesses? It's going to look very different from the talent that grows new business, but I can't deny that they're both forms of talent.
