I'm not really saying any of the advice around git workflow is bad. It's that too much time spent on process instead of development is. If you take the advice for what it is - a good starting point - I think it's great to use.
1,217 karma · joined January 15, 2016
I'm not really saying any of the advice around git workflow is bad. It's that too much time spent on process instead of development is. If you take the advice for what it is - a good starting point - I think it's great to use.
Having a defined workflow is not a bad thing. And it certainly wasn't the intention of the author for anybody to stagnate. Unfortunately, it's very natural for technical people to overthink and over-engineer process.
In my mind, when an organization is new to source control or is haphazardly using it, it's best to simply start using the tool. Each product is different, each organization is different, and each developer is different. You should mature into an organized development model based on what you know about your own situation.
If you develop on the develop branch and release on the master branch, but don't communicate that clearly to the new guy, I guarantee he's going to start working on master right out of the gate. The same goes for every model where there's a lack of communication around procedures and no workflow controls.
Git saw a rise in popularity because it was easy where every other solution was difficult. If you're having issues with code review, patches, release versioning, or whatever - address that particular problem. If the problems are multiplying to the point where it's significant, it's time to think through a process. Spending your time and energy ferreting out a process based on the fear of what might one day happen will result in a significant amount more time spent doing that then addressing the would-be problem in the first place.
As someone who also has visited that dark and twisted land... I completely agree with you (every post in this thread).
I don't think I ever once experienced the supposed benefits.
I also look at how friendly the project is to pull requests and outside development. If a bug is important to me, I will spend the time to code a fix, but if there's no hope for getting any changes made, that represents a large risk to me. It's not a bad thing if the team in charge pushes back for higher quality code, code style, or solutions practical for wider audiences.
If there's continuous integration in place with automated testing and static code analysis that is fantastic. It's not a deal breaker if it's not, but having it in place is a good sign.
Depending on the project, I may have a look at the source itself. I certainly don't look the source of every application I use.
I have found that online recommendations in developer communities are not always good. More than once I've tried out projects based on people evangelizing them only to find out that they are pretty far from acceptable.
There are differences in how I judge things that will be customer facing or that I'm going to have to support operationally. I'm a lot more critical at that point, but my top 3 points are:
1. Can I put it in a container. 2. Are the developers committed to long term support. 3. Will they give me a t-shirt.
I really hope they actually invalidated it instead of saying "Samsung didn't infringe". Because that means at some point soon we Android phone users can actually have slide to unlock (instead of swipe in any direction to unlock). Although who knows... at this point that feature might irk me. It was important to me back when I switched away from iPhones.
There is a solution - Cisco Jabber. They have a hosted solution now. I can't find a link currently and I haven't used it since we have it on-premise. But I did talk with someone recently who worked on their cloud product.
OK, so that was the one perk. That and the red carpet clubs used to actually be nice. I remember spending some miles on my wife's membership so she could enjoy a drink while waiting for me at the airport... then a month later the security lines being moved in front of the club so she couldn't get in.
All my miles were spent on other people. It's surprising how many people will hit you up when they need to fly somewhere but can't afford it. For the longest time I was saving up for a trip to Asia on one of those lay-flat seats in a private suite. I was close when my wife mentioned to me that she sent her brother, his wife, and their kids to Kansas. Freaking Kansas... oy. They might have said thank you.
In all the years I did it, I had one proper "free" vacation. It included a suite at a crazy nice hotel in Manhattan well above anything I could afford.
All that flying and being a 1k made me bitter. I hate traveling now because of the way they treat the no-ks. I'm bitter with the casual travelers who don't understand how to get through security with any efficiency at all. I'm bitter with security for it's intrusiveness that provides no security at all. I'm bitter with the airlines for putting their most jaded and customer service averse flight attendants on the planes that go wherever you want to vacation. I'm bitter with the guy who puts his bag in the overhead 3 seats back and has to swim upstream when we're departing the plane. The list goes on. Don't even get me started on the "$25 extra for a bag or a seat upgrade" I'm an angry old man in airports.
For anybody still putting in the time in the air - look into surfair. Chartered flights out of private airports for a monthly membership fee. No TSA, No lines. No last minute $2500 tickets. It's awesome. Limited range of cities though.
Question 2: How the F#*$ are you a software developer in Mountain View without a job?
For personal/private, I'm perfectly OK with whatever open source solutions are available.
I think it would be a good thing if GitLab or another project could compete with GitHub, but I think we're another year/product from really getting there.
I can't pinpoint it, but I'm much more likely to browse, review, and offer pull requests in a github instance. It's intuitive and I'm used to it.
Now I don't even need to scan my ticket in the app. It searches court records and auto-appeals for me.
The republicans like it because "business is going to be terrible if you elect a democrat" (or a commie!)
Sanders likes it because "big business hates me! A vote for me is a vote against the establishment!"
Clinton likes it because anything that makes Sanders a legitimate opponent means a longer and more active donation cycle, and more young people and black people voting come the general election (and despite what they say now... they are all going to be clinton supporters in a few short months.
That being said, if I see a pop-up dialog with an advertisement coming from my terminal application, I am going to uninstall it immediately and never think twice about it again.
I thought iterm was open source.
It has a range of 723 requests (CherryPy) for a plaintext hello world to 6.8Million (ulib) for plaintext. I looked at the Flask numbers and they don't compare with my own - I got between 3 and 4 times that when I benchmarked it myself on hardware that I'm sure was older and less powerful (and I didn't bother to turn off logging).
I looked at the node code and it does not use express - which could very well be the difference I am experiencing.
I'll tell you what though... I'm going to have a look at ulib for static files!
Flask/Python blows Node out of the water where performance is concerned. That shouldn't be a surprise to anyone.
Flask has a significantly faster ramp up time than Tornado as it is designed to be simple.
As far as load balancing/performance, you front end it with something like NginX.
You can process things out of band easily enough with Flask, but I wouldn't evangelize it so much to say that it's the best solution for every problem.
Personally, I like to keep things as simple and as logically separated as possible until it's absolutely necessary to change. Flask is one of those frameworks that doesn't present a lot of mystery.
My biggest problem with node isn't performance - for that it's fine for most use cases that I deal with. It's that you can get perl-level convoluted and sloppy very quickly and easily.
If you don't have confidence in someone's ability based on their experience and their interview but you did like them, give them a task to accomplish offline. See if their results are anything like your results would be, and bring them in to see how they respond to feedback both negative and positive.
I've seen too many interviews that go along the lines of "How would you rate your Java on a scale of 1-5?" "5" "So how would you fix the problem if your cache hit rate on SomeObscureCommercialProduct went from 94% to 82%?" "Forget that guy. Huge ego. Doesn't know anything."
I did run into one company that had an interesting process for technical validation. They actually hire people for two weeks as contractors and have them work with the team. Then they hold a vote and decide whether to extend an offer.
Of course more people are renting. If they have managed to save the down payment required, they have to question whether they could really afford that property again. Most haven't because rents are higher than their mortgages used to be. Who can save $100K+ in that situation? And if they could, where is that $500K house that you can buy with 20% down? Probably not in the same area where you have a job that allows you to save $100k.
The government is propping up the banks which are propping up the housing market. We'll see a little pop in the next 24 months, but it will be a quick one because it will release some of the hold backs that are in place today.
I take it that you are the author and I've completely derailed your thread by going off on my own tangent.
Apologies.
I will give it a second read and see if I can't come up with some more relevant feedback for you.