wmij

> I see MSFT keeping GitHub as a "simple" choice for repo hosting.

I didn't say that the "simple" choice for repo hosting would go away... My point was that if you need GitHub Enterprise, you get it only with the biggest MSDN subscription and end up with a bunch of things either you don't need or don't want and having to agree to licensing that's MS/MSDN specific.

> Why would they sunset TFS (Or VSTS)?

Admittedly I've been away from TFS for a number of years, however, it seems that GitHub Enterprise is a natural fit product wise for revenue stream via licensing thru MSDN to get organizations onboard with GitHub that weren't before. If they were to sunset TFS and provide a migration path, it would end up giving them significant licensing dollars.

The more important point I was trying to make is that orgs that are now on GitHub Enterprise would need to subscribe to MSDN enterprise licenses for a bunch of things that aren't relevant and get locked into TOS that they hadn't been previously.

Regardless of sunsetting TFS/VSTS, I think that Github Enterprise will be only available through a MSDN enterprise/premium license or whatever that is now in 2018.

There probably won't be (m)any noticeable changes for the open source and devs running personal private repos and possibly the same for GitHub team plans. However, I'd bet Microsoft will plan on a sunset timetable for TFS and push their licensing and sales machine toward GitHub for Enterprise. I'm glad my group isn't on GitHub for Enterprise because after seeing this news I'd be looking to migrate away ASAP. I can envision the the potential for their draconian licensing lock-in and TOS language spawning a nightmare for teams that are running GH Enterprise. These GH enterprise installations will likely be required to purchase MSDN licenses.

I also find this challenging. One thing I can suggest that has helped me on my current project, is to do a morning standup. It's always brief but I use this time to set a mood/tone for the day. I try to lead with something relevant for the team or business, hopefully good news, but still try to motivate with a sense of direction towards what we're working on and where we're going. We'll each give our status and have an opportunity to bring up blocking issues, successes, or anything else. But I've found that my team looks for this ritual to assess my mood. I try to stay optimistic towards the effort, our business and the opportunities we're all working towards. When it gets slightly frustrating on a day to day basis where the "business" side may not be meeting the "engineering" side, I try to make dry light humor where we can laugh a bit during standup knowing that we're pointed in the same direction. Not an exact science, but on the day to day, try to find something to laugh about. This usually finds people willing to pair up together to take on "the cause" or whatever the team needs to get done.

Yes. It has happened especially as the team has scaled in developer size and when we are in development modes where there's better chances for conflicts, for example iterating on core code during feature development, or when we're touching/adding to common configuration settings. But it hasn't been that often where a developer needed to fix a tricky conflict.

I encourage members on our team to rebase frequently as they're iterating prior to opening their PRs for their individual feature branches and I think this helps us avoid problems for our typical PRs.

Also as a rule, don't sign off on a PR until all conflicts are resolved, if there were any and review the final commit(s) carefully.

We also have the option because of some of the CI tools we've written to give our QA people access to specific SHAs that can be tested, so sometimes (rarely) QA sign-off is asked for as part of the PR.

This is the flow my team uses for addressing any comments, concerns, changes, bugs, etc. We push all subsequent commits to the branch under review and prefix the commit messages with either 'fixup!', 'squash!', etc. that address the comments. The team then reviews the fixup commits further making additional comments or giving a :+1 to the specific commit SHAs. Once everything, including all fixup commits get a :+1 as sign-off will be the only time the developer does a force push to the remote branch under review. Then the developer that owns the PR is responsible for the squash, merge and closing the PR.

Using this flow we never lose any comments during the PR process and can revisit the individual commits, diffs and files changed while the PR is open.

NorthPage - http://northpage.com - Southbury, CT.

We are seeking software engineers to join our team and help us advance the development of our cloud based cognitive marketing analysis platform. Our software helps many leading retail, financial services, consumer product, pharmaceutical and technology companies achieve digital marketing success.

Ideal candidates will have experience developing RESTful APIs and will have worked with any of the following technology: Java, MySQL, Redis, Selenium, WebSockets, AngularJS.

To apply, please email careers@northpage.com

Full Stack Engineer | NorthPage | http://northpage.com/careers.html#job3 - Southbury, CT. (Boston/CT/NYC area) | REMOTE potential

We're a Digital Marketing Analytics software company growing our engineering team and looking for engineers that enjoy working across the entire stack - front (Angular, Bootstrap, Sass) to back (MySQL, Redis, Solr, Java SE, AWS). You'll join a team with an engineering culture that fosters technical transparency and mutual mentoring. We're solving interesting problems related to digital marketing performance and seek talented engineers to help us deliver solutions and insight to our customers for achieving digital marketing success.

- Salary is competitive/open and ultimately depends on the candidate's fit and experience. - This position is based in our corporate headquarters in Southbury, Connecticut, but for the right person, we are open to other possibilities, especially if you are either in the Boston or NYC areas.

To apply, send an email to careers [at] northpage.com with the subject 'Full Stack Engineer'

Please be sure to tell us about your experience (resume, GitHub profile, past projects), what you're working on now, what you're looking for in a new opportunity and the best way for us to contact you.

For me, auto starting a video in news item I want to read is an abandonment driver unless the link either had the word 'video' in the title or an icon that represented a video would be part of the story. 'Your video will begin momentarily...' - Oh no it won't.

I once added a reply to a news site to give my feedback on their use of videos and it was removed.

I've been working on a web based JSON generator called ObjGen that lets users model and generate JSON data interactively using an easy to use shorthand syntax. I wanted to write a tool for quick modeling and prototyping of API values for other projects that I work on. Since putting it online, I've gotten some good user feedback and have heard that it's been helpful for students just learning about JSON and data structures. Check it out here http://www.objgen.com/json?demo=true

I have a couple of other live generators online there too for creating html fragments and java classes, but haven't really updated them in a while. The html generator is Bootstrap aware, but only supports Bootstrap 2 css. The html generator was good for pair mockup sessions, but haven't used it much lately because my other projects are all Bootstrap 3 now.

It sounds and feels like 7/8 to me. So it's 13/16, cool stuff! I have a clock at home that plays the Big Ben Westminster Chimes in 5/4 time. Once I figured out it played in 5/4, I think of "5" now every time I hear it. There is a definite art to creating melodies that feel good in odd time signatures.

NorthPage - Southbury, CT - Front End Developer

We are seeking a front-end web developer, experienced in UI/UX design to advance our modern, responsive web applications that visualize the data that drives and is produced by our software platform.

Your Skills & Experience

- 3+ years of front-end web development experience (JavaScript, HTML, CSS, JSON, jQuery)

- Recent experience using modern front-end web frameworks, like AngularJS and Bootstrap

- Recent front-end development experience working with REST APIs to build data driven web views

- Solid UI/UX design experience

About NorthPage

We are a well-funded, early stage software company located in beautiful New England, close to the NYC area. Our tools and technology help many leading retail, financial services, consumer product, pharmaceutical and technology companies achieve digital marketing success.

To apply for this position please send an email to development@northpage.com that tells us who you are, more about your skills, samples of your work, your resume and contact information.

My approach to situations when there are no unit tests for existing legacy code is to start by writing a few coarse grained, or basic tests. Just enough to get initial coverage on critical functionality. Then you can add a few more tests over time.

What also works well is to give someone new to the project some initial tasks to write and fill in gaps for missing unit tests and coverage. Just enough to get them productive from the start, but don't task them with writing all the missing tests. I've found that for most developers that it helps them come up to speed on getting their environment configured, looking at the code, and introduces them to your build and version control process from the start.

Ultimately it's going to depend on the project and how hard it is to go back and add the tests.

This has been an ongoing side project of mine as a utility for quickly generating prototype code using just raw formatted text as input. I've had the live JSON generator up and running for a bit and just recently added support for generating HTML elements with support for Bootstrap that uses a HAML like syntax. Would like to share with the community and get some feedback and hopefully people find it useful.