It depends on the situation. I had all of mine out this past weekend (in the US) and, because they were fully grown in, all they had to do was some local anaesthetic (about 8 shots around various parts of the mouth), wait 15 minutes, and loosen/pull them all. Total procedure was less than 30 minute and no painkillers prescribed after the fact.
HN user
numo16
I guess that depends on how users go about finding projects on github to file issues. If, for example, the user has an issue with this NixOS package (or debian package/any other repackaged example), and they start by just searching "python ambee github" or "Home Assistant ambee github" (seems like a reasonable first attempt to me) they will likely find the upstream near the top of the results.
Now, some users will perform due diligence and maybe find the NixOS issue referenced in OP and look elsewhere, but many will find the project and immediately file an issue there in the upstream, leading to the author's main concern of "I don't have time to support NixOS issues".
It would only remove the burden if users of the NixOS package know to go to the fork for support, as opposed to the upstream.
I would side with you on this bet. Lots of brodozer and parking lot princess F-150s up here in Michigan suburbs.
Saw it for $1.14 in south east Michigan
For html/dom parsing, I would recommend looking at either AngleSharp[0] or HtmlAgilityPack[1], as they tend to be the most popular in the community.
[0] https://github.com/AngleSharp/AngleSharp [1]: https://html-agility-pack.net/
I read an opinion piece[0] recently that suggested one of the (many) reasons that No Man's Sky was so poorly received at launch was due to the fact games have commonly been boiled down to constant action and "gotta beat the game" mentality, and that players don't know how to just explore and enjoy games as an open-ended single player experience.
As someone who plays almost exclusively single player games across a vast numbers of genres, I enjoyed No Man's Sky's "exploring and discovering the unknown" game play at launch and have ever since, as they add more and more content.
0: http://www.thegeeklygrind.com/opinion-no-mans-sky-doesnt-mul...
They will start looking for a new gig immediately
The response to this should be: "Good for them! They should look for somewhere that will pay them what they think they are worth."
I believe that is the whole point behind sharing salaries, to help level the playing field and help people who got low-balled on their offer to realize this.
And in the Midwest.
The way the greater Flint area's zip codes and address system works out had some other interesting impacts, as well, from a business perspective. After the crisis became more public, we started seeing businesses who were in Flint (greater Flint area, Flint mailing address), but not the City of Flint (the affected area), putting up signs and trying to make very obvious that they didn't have Flint water.
The City of Flint's water system is isolated from the rest of the county, which falls under the Genesee County Drain Commission's jurisdiction and is connected to the Detroit water system. It is still difficult to get some people to understand that they are different things (have had to explain to family many times that while we live in "Flint", we are not on Flint water). It would be interesting to see a study done on the effect this had on businesses both within the city and in the greater Flint area.
However, I'm not a software developer, so rhat could also have something to do with it
Definitely has something to do with it. I'm a software engineer in the Detroit area and the last time I switched jobs (4ish years ago), it took less than 2 weeks from the time I updated and posted my resume to signing an offer letter. With the number of calls and emails I get daily for different positions in the area, I have a feeling it would go just as quickly the next time I decide to make a move.
Seems more like it is heading towards the ideas behind the metaverse[0]
They haven't really shown an interest in Kubernetes thus far
Except for helping with Windows Server support for kubernetes[0] and supporting kubernetes in Azure Container Services[1]
[0] http://blog.kubernetes.io/2016/12/windows-server-support-kub...
[1] https://azure.microsoft.com/en-us/blog/kubernetes-now-genera...
Not sure if it still does, but I'm pretty sure omnisharp is what VS Code used for it's C# engine when it first came out
Windows Containers only went GA fairly recently with Windows Server 2016, so it is unlikely that many are using them yet. I have yet to see any CI services that mention any plans to support windows containers or acknowledge their existence.
If by multi-desktop you means virtual desktops, then you are in luck. Virtual desktops are a built-in feature of windows 10 [1].
[1] https://blogs.windows.com/windowsexperience/2015/04/16/virtu...
The containers that run natively use a windows based image, not linux. So, no kernel emulation, no linux syscall translation, just pure windows base
Docker for Windows, linked above, and Windows Container Service[0] are two separate things. Docker for Windows runs a linux VM in Hyper-V and allows you to run linux based docker containers. Windows Container Service allows you to run windows based container images (using Hyper-V as a backend) and can use either Docker or Powershell Container Commandlets as a frontend for interacting with those containers.
So, yes Microsoft did implement containers in the Windows kernel, but that isn't what OP is about.
[0] https://msdn.microsoft.com/en-us/virtualization/windowsconta...
Docker images still aren't generally available, but you can now run Windows Container Images based on the NanoServer docker image (and WindowsServerCore image if you replace nanoserver with windowsservercore in their image URL in the docs below) on Windows 10 (insiders build)[0].
[0] https://msdn.microsoft.com/en-us/virtualization/windowsconta...
Yeah, the SMB SaaS ERP area is pretty small currently. There are some of us (I work for Plex Systems[0], which caters more to manufacturing customers), but we don't see as many headlines as the big names.
That will definitely be interesting to see. I know my polling location is a PokeStop, so I might have to sit around and observe a bit on election day this year.
Plex Systems, Inc. | Software Engineer – API’s | Troy, MI ONSITE
We’re on a mission. As a fast-growing software company on the cutting-edge of technology, Plex is revolutionizing global manufacturing in the same way cloud solutions have transformed sales, marketing, and human capital management. We want manufactures to succeed. That’s why we’re on a mission to replace underperforming, on-premise enterprise resource planning (ERP) systems with the Plex Manufacturing Cloud – ERP built for today’s model of manufacturing. If you want to see the future of business, we’re what’s next.
In support of our ongoing growth, we are looking for a Software Engineer – API Designer to help guide the development of our next generation API platform. Position will be located in our Troy, MI headquarters.
Responsibilities include the following:
* Provide input on the design and contribute to the development of new platform and API features for middleware and partner applications using C# handling XML, JSON data formats
* Provide stewardship of the design, development and maintenance of scalable RESTful services and Web APIs.
* Ensure the implementation of industry best practices for API security, policies and versioning strategy.
* Work with product management to translate end-user requirements into working products
* Collaborate with other teams including Product Management, Product Developers, Data Center, and Dev Ops on successful delivery of systems enhancements
* Facilitate reviews of technical specifications and program code with other members of the technical team, communicating design, requirements, feature set, functionality and limitations of systems/applications to team and development lead
More info here: http://www.plex.com/about-plex/careers.html?p=job%2FoTy12fwe
I work for a company that averages around 50 production deployments per day for our customer-facing ERP, and we only do code reviews for new devs and changes to underlying framework changes for mostly the same reason sklivvz1971 mentions. We rollback very infrequently and a majority of our devs can deploy to prod with the push of a button as needed (this includes both application and database code). Not arguing that code review is unnecessary, just feel that with proper training and having devs with good judgement can help reduce the likely hood of breaking things when deploying small changes frequently.
Based on Microsoft's node.js guidelines[0], it looks like you should be able to get by with just installing the Visual C++ Build tools and not the full VS community edition.
[0] https://github.com/Microsoft/nodejs-guidelines/blob/master/w...
I use node on Windows everyday and very rarely run into any issues. Following the dev environment setup from microsoft's node.js guidelines[0] should take care of a majority of any issues you might run into with handling path length (tools for removing things > MAX_PATH), using c modules, etc...
When I was using HERE maps on windows phone previously, it would always display the current speed limit and make a noise when you exceeded the speed limit. It's a feature I miss now that I'm back in android with google maps
Microsoft started down the headless server route quite a while back with the Server Core [0] installations (started with server 2008)
IIRC starting with server 2012 or 2012 R2, all configuration and management functionality was exposed via powershell commandlets, as Server Core was the default installation type and server management was meant to be done via winRM/remote powershell sessions.
What I did do, though, was basically buy one of every brand of blade that was available on Amazon
For those interested, there is a service for this very thing now: http://www.tryablade.com/blade
Or you could go the DE safety razor route and pay $0.08/blade for 100 Derby Extras. Cartridge shaving just seems so expensive and wasteful to me...