225 karma · joined April 6, 2011
Of course, we also had some slow tests we rewrote and had to fix some tests that did not play nice concurrently. But it was well worth it.
I don't think you'll see a big benefit for a current 10-second run because of fixed cost of startup is some of that. But running tests in parallel may reveal some bad testing practices: leaving data behind or improper mocking that cause tests to fail in parallel. Fixing all that once you get to a massive set of tests is really painful and slow becuase you have to fix them ALL before switching your testing config. So that might be a benefit to turning it on soon and growing your tests already in an parallel environment.
I definitely don't want a sales call to show me everything I just saw in the video.
This site I could take a few of these and go write a few paragraphs about off-the-cuff. Looking forward to playing more when the site comes back up.
JetBrains needs to reassure us multiple instances are ok on same machine and across VMs. Will running the IDE in OS X and also a guest Linux VM look like multi-machine use? If so, that's really a bad flaw in licensing.
I am curious about "JetBrains now controls pricing". Haven't they always? If they raised their price outrageously for yearly upgrade model, they would lose customers, so that's true of new and old system. I have control of whether I pay their price or not, but they get to control the price, as always.
I understand to some degree that losing access to a tool is an inconvenience, but it doesn't strike me as a terrible burden. It's all just a view into the code, there's nothing irreplaceable about it. So renting compared to having guaranteed permanent access is a loss, but it doesn't seem that awful - but that's very different person to person.
Anyway, I am legitimately curious to hear more about this viewpoint. I kind of get it but don't have the strong visceral reaction to it as many others on here. Is it a use case difference, of people who skip upgrades versus those who don't and pay every year? Or is it fundamentally a philosophical stance on own versus rent?
My complaint is the Mozilla folks missed a more general, better capability they could have built.
I wish the article had talked about how big this actually is. Is it a fraction of a perfect of the cliff, does it make a visual difference? Can locals tell by looking, or is this amount so insignificant that it's barely worth discussing, except as part of realizing how large structures like Half Dome really are?
For several reasons, I think our move toward microservices is a good one. But in our case I have seen complexity move from code to coordination.
Some people don't seem able to take naps. My advice is: give it a few tries. For me it took a few attempts for my brain to figure out how to shut down like that. And some days it just doesn't happen.
I've found nothing better than taking some caffeine and immediately taking a power nap. When the refresh from both hit about 45 minutes later, it's like starting the day over, energy-wise.
I think you should take a critical look at the front page and see what it is communicating. My personal take: I have no idea. A modern ticketing system... like TicketMaster? Train tickets? Is this an API that interfaces with venues? After my developer instincts kicked in I thought maybe a bug-tracking system. The page needs to be specific about what type of ticketing and who will want to use it.
Ah, in the Windows Fact Sheet I found this: "NodePoint is a ticket management platform based on the Bootstrap framework. It is meant to be simple to setup and use, yet still offers many features such as user management, access levels, commenting, release tracking, email notifications and a JSON API."
THAT's what should be on the front page, although "ticket management" still is vague, and referring to Bootstrap seems irrelevant to me personally - that's a developer detail.
----
The "Changes and Improvements" is way more visible than any further information, which is way down in the footer. The "Sales" link is just an email link. What type of enquiries are you expecting? What is there to sell, if it is free? You might have two audiences: small businesses and developers. You may need to totally separate the messaging so they each can see what would interest them.
And finally, the demo requires me to register which isn't going to happen when I know so little. What if you just generate a random login and auto-login the visitor?
So look, I personally think the page could use some rethink for clarity of target audience. Then I might investigate a bit more.
It has made me a better software team leader than I would have been, and definitely set me on a path to reach the next levels of management in a company, which is my particular interest and skill set.
I vote for starting some reading of business IT. There are lots of good articles to start your reading list and which will point you towards other readings.
I'm not sure on landing the job, but a CTO needs to think on that level, which is quite different from software development. Being familiar with the topics and able to sell yourself as a person who understands these topics will help you.
I recommend Cloudinary or 6px for doing any non-trivial image-based websites. Those services abstract away huge parts of the complexity of storing, manipulating, and delivering images online.