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

If interested reach out with an intro and CV/github/portfolio to [email protected]

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>

This does result in a “hiccup” for any clients wanting to connect. They will see a 502 gateway error at which point they should retry with exponential backoff.

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 can do this because I have chosen to work on niche problems and smaller markets. Scale is not my issue, even in very successful scenarios.

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.

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.