Not to mention you've now greatly increased the surface area for merge conflicts. I mean what if someone else added a 5 letter variable?
62 karma · joined July 6, 2012
Not to mention you've now greatly increased the surface area for merge conflicts. I mean what if someone else added a 5 letter variable?
There is one clear justification OP can provide for this style element. HE/SHE/THEY THINKS IT LOOKS PRETTIER! Just say so, call a spade a spade. If OP is honest with themselves then they can seek help for their terrible editing choices. Otherwise you just end up with the the tired cycle below.
1. Trot out your aesthetic preference.
2. Speciously connect it with something that has merit(e.g. lining up numeric values in spreadsheet, which BTW has value because those numbers are in an nXn space delimited grid where position implies meaning.)
3. Use the 2 steps above to make a pitch for forcing everyone to use your tool du jour or to shove this as a style guide element down your dev team/projects/friend/significant other's throat.
From my experience this silly style element serves one purpose making that one person with OCD feel better. For everyone else its a headache. It causes source control to lose its mind, it makes block editing trickier, all while simultaneously providing no tangible benefit.
I would consider hard to find a decent software engineer that would introduce 20 unproven tools to for something allegorically related to "plumbing" like say your web server.
Additionally, a lot of this is based on perspective. If I suggested standing up a web infrastructure on "nginx" am I an Albert or a Zip. I mean "Apache" has a much longer track record...right? By this article's logic we should write everything in FORTRAN and use single-tasking operating systems. Those have been around since the 50's ... rock solid.
Net out is "proven track records" and "best practices" are convenient stop gaps for ignorance. They are a way for people that don't know any better to manage risk. "I don't get it ... but it worked for her". Being competent and knowledgable, having good risk management skills, and understanding the problem will serve an organization much better than being conservative in your choice of tools.
1) There are room for both boring and cutting edge technology in any business. Albert didn't drop the ball by choosing cutting edge tech. Albert exhibited poor risk management skills. Alice wouldn't be complaining if Albert took a controlled risk and installed a next generation flash fryer that gave a clear competitive advantage over Zola in terms of personnel and order-to-delivery time.
2) Good ideas require both Albert and Zip. Zip keeps the lights on and the costs down for all the mundane BS required to run a business. Albert is the disrupter. He is the reason starting the business was a good idea. He is an iconoclast that looks at the state of the world and said "I can do this better".
The title of this article should be Boring Systems Build Benign Businesses
Have you ever had an argument that was just mediocre? But later you think of a witty retort that would have been just perfect. Thats what rebasing is. Its re-structuring the conversation the way you would have liked it to go.
> Not everyone wants to get to the "top" sure, but how about you let them make that decision rather than taking the liberty of handicapping them in advance.
>They certainly sound better than environments full of mental/emotional abuse. Why can't we create abuse-free environments in the real world, too?
Sure but they will need to compete against the environments filled with vicious, agogi-bred cutthroats who are there by choice.
We are a newly minted startup in Center City, Philadelphia. Our goal is to help consumers make better decisions about where their energy comes from. We have an excellent, seasoned leadership team and we are hiring developers.
A few details: - Our code base is tiny. Lots of room to make a big impact
- Our stack is Backbone, Python/Flask, MySQL deployed on Ubuntu(AWS).
- Our need is a few passionate software engineers who want to work in a lean software outfit in the city.
If that sounds like your bag we can offer competitive salary and benefits plus we just moved into a great spot in the heart of Old City.
more details: http://www.clear-switch.com/careers
contact: careers@clear-switch.com
We are a newly minted startup in Center City, Philadelphia. Our goal is to help consumers make better decisions about where their energy comes from. We have an excellent, seasoned leadership team and we are hiring developers.
A few details:
- Our code base is tiny. Lots of room to make a big impact
- Our stack is Backbone, Python/Flask, MySQL deployed on Ubuntu(AWS).
- Our need is a few passionate terminal ninjas who want to work in a lean software outfit in the city.
If that sounds like your bag we can offer competitive salary and benefits plus we just moved into a great spot in the heart of Old City.
contact: careers@clear-switch.com
There is simple and then there is too simple.
And wasn't the thought that checked exceptions would be better for critical code because the compiler guaranteed that they were handled.
I'm no fan of java's error handling, but I think that the insinuation that the lack of any formal error handling makes you write less error prone code is bordering on the absurd.
Detail oriented individuals write robust code given the constraints of their environment. If its arbitrary strings that indicate error state they use strings if its integer return codes they use integer return codes.
Step one to a good rebranding effort. Change what it is your selling. You can rebrand a turd as a chocolate lollipop and expect me to drop what I'm doing to rush to the candy store.