sheraz

nuvoair.com | Full-stack engineer | FULLTIME | ONSITE | Stockholm, Sweden

No visa sponsorship available. You must have permission to work in EU.

We are a small but fast-moving funded (2017) digital health start-up changing the way healthcare is delivered. We combine hardware, software and data to improve lives of people suffering from respiratory conditions and to enable better clinical decisions.

Your key responsibilities are to build, test and maintain architecture. Discover opportunities for data acquisition, and to assist scientists with data modeling, mining and deployment.

Your skill set and qualifications include: Minimum 5 years of commercial software development/ Python, Django and Flask frameworks and SQL / Strong linux command line a plus -- GIT/Jenkins/Docker/etc -- Testing (unit and integration) / Strong communication and documentation skills (fluent in English)

What we offer:

  - Competitive salary incl. pension plan
  - Opportunity to participate in our option plan
  - 6-week annual leave
  - Subsidized gym membership
  - English speaking office in central Stockholm
  - A fast-growing startup
  - The opportunity to shape the future of healthcare

I'm think the "doesn't suck" does not really sells this.

What, exactly are the benefits here over bootstrap or any of the 300 other frameworks with similar specs?

Looking at your examples I can't immediately see the difference to bootstrap other than (maybe) the smaller file size.

Moved away purely for simplicity. Clustering brings too many black boxes in the mix.

I moved off of swarm and back to regular docker after taking a hard look at our needs and infrastructure. Turns out we don't need all the clustering and scaling magic of swarm or kubernetes.

In fact, this has greatly simplified our development, testing, deployments, monitoring, and recovery.

If I need to scale then I add more cores to a machine with minimal downtime. No need for all this rolling upgrade stuff (at least for my applications)

Perhaps rather than using bootstrap on a high stakes project (like client work or apps with paying customers) you could try bootstrap customization on a low risk side project? That way when (not if) your screw it up there is no anxiety of an angry client or customers demanding a fix? There is no anxiety of having to support IE or some client’s esoteric dom-modifying browser plugins.

This way you can learn at your own pace and really get s feel for the codebase and workflows for bootstrap customization.

Crud apps and java with spring boot.

Dot net and sql server

Strangely I see a lot of nodejs for IOT thinks with big companies as well.

Great news, but interesting to see that they still recommend securing individual domain names. I imagine this is for security purposes?

Well, the trick is that I have downtime but it last for only a few seconds.

  Docker pull <image name>
  Docker container stop <container name>
  Docker run <opts> <image name>

And that is the trick — make the client retry with the exponential backoff. Document it as the expected behavior when that event arises. And for our traffic patterns this is acceptable.

Sure, but there is a bit of relativism here, isn't there? A 10 year-old might consider Coldplay an oldie the same way a fresh javascript developer might consider jquery old legacy stuff despite the fact that both continue to make releases.

I think if you are selling services as a consultant then perhaps sell the solution rather than the technology behind it.

When I buy a car I’m buying the benefit of it, which is convenient transportation. I don’t really think that I’m buying a drive train, engine, steel body, airbags and whatnot.

Question - how long does it take for your projects to “grow into” the stack and complexity you have scaffolded up around it?

Yes, and I love it.

In hindsight I have been guilty of resume-padding and falling prey to hype by choosing to build on technology not appropriate to the problems at hand. And I find myself reverting back to basics, with bits of new tech sprinkled in.

My reversions:

  - React, flux, redux ---->  jQuery and intercoolerjs when needed
  - Swarm, Kubernetes  ---->  Just plain old docker on single machine, scale vertically with cores and memory when needed
  - Microservices first ----> Django Monolith first, then break out microservice when needed
  - API Gateways (kong, Azure) ----> Nginx reverse proxy with hand-edited configs.

I see jQuery will have a place in my stack for some time to come. It just works (tm), and it plays well when I need to level-up with wither intercooler or yes -- backbone.

Another benefit is that it is a low barrier to entry for junior developers. It allows me to establish a baseline knowledge, and then mentor other things like workflow, code structure, and architectural things rather than chasing weird configuration things inside of webpack or the taskrunner-du-jour.

Easy offboarding from Heroku into dokku [1] and digital ocean [2].

But these days I run simple docker in digital ocean and Azure with deployments managed via my CI.

[1] http://dokku.viewdocs.io/dokku/

[2] https://www.digitalocean.com/products/one-click-apps/dokku/

yup. happy pycharm and docker user here. even have it working with debugging and breakpoints.

How many hundreds of thousands pass through American borders with little hassle every day? That is not news (but maybe it should be as well).

Also, one cannot paint with such a wide brush as "The USA." It is the same mistake as any American visiting London, Paris, and Berlin -- and then saying they have seen "Europe." They didn't see Europe -- they saw globalized mega-regions that happened to be located on the European continent.

Unfortunately, Baltimore is an outlier when it comes to violent crime, corruption, and poverty. It is an urban center in decline and in need of all kinds of help. (This is where I stop, else it becomes political very quickly).

Compare Baltimore to places like Denver, Dallas, or Phoenix, and you will see very different cities. The US is huge in geography, population, and economics. Pinpointing an outlier and concluding that the entire country is poor and dangerous does not make for constructive conversation.

We would do ourselves a favor to talk more about the specific problems Baltimore faces, and then look at the broader American context to see which sister similar cities have tackled similar problems.

Sure, if you only ever consume terrible news then it would seem that way.

I can cast sweden in a similar light. Or even Disneys magic kingdom.

The productivity drop I see is that machines spiking CPU and apps like sketch struggling to keep up with updates and refresh. When that starts then devs and designers start tweaking settings and googling answers and boom. 1 hour gone to IT issues. Swapping adapters. Swapping cables. Cycle continues...

well said. That stupid apple dongle on iPhone. Amazing that I can't charge AND use my urban ears. Wtf.

Or apple abandoning that cool magnetic charger! My mbp 2010 had that skinny one, and I never came off.

Now we have usbc or whatever it is called, but waaaaay longer battery life, so that might be the answer there.

Come to think of it, is there wireless charging for laptops yet?

Cool idea, but from the article it really seems like they want to license the tech rather than go head to head against established browsers.

This reminds me of something that I would see on dribbble as a UI/UX exploration.

Last point, the data consumption! I'd like to see the data and power draw for this app.

Great story. What was that startup oriented fan pages you mentioned?

Like this one? https://github.com/vivianhylee/seam-carving

Yeah I'll stick with Sonos, thanks. We have one at work, and the only complaint I have is the terrible taste in music of my colleagues :-)

For me, the Medium name is hurting the credibility with anyone who would publish there. I'm more likely to give my attention to someone with a static site, even if it is a boring old template. (I'm thinking of doing the same for myself).

As for Hackernoon I would be more likely to read their content off-medium. However, I do feel like I see them too often on HN, which means I now actively filter them out when deciding what to read. They are a little overexposed here.

I rarely click on links when I see the source as medium.com. The quality of content there feels too much like blogspot back in the day.

I think the author echos some things I've been feeling about my work environment (the desktop). There is a lot of friction that comes when each of my applications wants to be its own immersive experience. My take-away from his post is that he seems to be iterating away from those rich, colorful, and distracting interfaces to something that is kind of interface-less.

This, too, is my dream (or sorts).

- Spotify without the spotify interface. (Google Music, in his case)

- Slack without the slack interface (IRC, I guess)

- Email without the web-client or sluggish Apple mail interface.

I know there are CLI for each of those use cases. But it takes commitment to learn and get them working to your liking.

so I'm guessing something like Time-based One-Time Password algorithm (TOTP) then flashed out from flashlight to the sensor on the door?

Why not just TOTP in my google Authenticator app then just type into keypad?

Like this: https://github.com/cathalgarvey/formadoor

First bitbucket and now slack?

not a good day to be an enterprise saas...

Yep. I do the exact thing for a lot of network related things (dns lookups, http requests). I use this nifty library: https://github.com/jd/tenacity

Not a ProGet user here, but this definitely seems like a good idea.

What are the open-source / self-hosting options here? It gets a little messy with all the sub-dependencies, doesn't it?

you might want to look at yacy for that.

https://yacy.net/en/index.html