Cool! I would have expected a ton of things like this, but there really aren't.
If it's free, though, who pays for your hosting?
71 karma · joined October 8, 2015
If it's free, though, who pays for your hosting?
Your target audience is theoretically Excel users who want/need to code instead, but I think you're alienating the power users of Excel, because their power tools are unavailable in the Mito spreadsheet editor.
For example, have you considered dumping the dataframes to "smart" xlsx files with backing code that connects to a local server, listens to worksheet events and tells the server everything that happens so it can write python code in the source notebook?
However, as someone who sight-reads all of his piano music, I'd be interested in experiencing if this makes sight-reading any easier or harder. It's taken many years of experience to be able to spot and predict patterns several measures ahead of where I'm playing, and I wonder if future musicians could get to advanced sight-reading levels more quickly using an alternative notation.
Full-time | Remote
We are a small, fully distributed but tight-knit team working on transforming how we find, plan, shop for and cook our everyday meals. Our mission is to make cooking easy for everyone, regardless of experience. https://www.cheffe.com/
We are looking for a few early founding team members and will offer cash+equity packages:
Head of Engineering, or Full-Stack Engineer: Be the second engineer (first eng hire) and make an invaluable impact on the company. All our code was written by the founding team, and our current stack is JS (React, Next.js), Swift, Python, Firebase and AWS.
Head of Product, or Product/UX Designer: Understand our users and develop the best cooking app in the world.
ML/NLP Engineer: Ever wanted to generate food, or at least understand it? ;)
We are also looking for a marketing intern and a business analyst intern for a late summer / fall start.
Email me directly at arseniy@cheffe.com
You should of course practice solving the kind of problem you want to solve or enjoy solving.
If you’re optimizing for an IC career at a large company, then you should of course practice that kind of work (and get mentored and get depth and everything the article says).
If you’re an engineer trying to transition to building businesses or being an investor, then you should of course NOT do what the article suggests. You should instead practice startup problems (probably at startups or by starting your own), like prioritization and resource allocation and networking.
And if that’s the goal, then you can easily find business mentors or startup mentors that will make an impact on your career, and what the article pejoratively calls “breadth” in software problems will actually turn out to be depth in business or startup problems (like prioritization and resource allocation and networking).
tl;dr – Sure, find mentorship and get experience, but make sure you articulate your goals first.
I tried to use DDG, but now I don’t because I never knew whether it was just my DDG search that had been unsuccessful or whether there were truly no results.
In fact, I wouldn’t know with any search engine whether there are “truly no results”, so I use G because I prefer to get what’s widely accepted to be the closest results possible.
You shouldn’t have to unpack complexity just to understand where a test failed or whether it failed because of bad test code or bad tested code.
Once you have so much complexity that reading and mentally executing the test takes time, you should probably be writing tests of your unit tests.
Analogy to movie production is spot on, I think. I suppose game dev is also different from other software/tech products because releasing continuous updates is harder. Also, players expect more from the first published version of a game: it shouldn't merely be playable (compare: early adopters could pay money for a SaaS MVP) but already polished, fun, engaging, well-designed. I've never worked on hardware products or products in heavily regulated areas, like health care, but I suppose the production cycle is just as tough.