4 ms·
Thow every best software practice out of the window. It is administration growing more administration. Peer programming is just dividing productivity by two. T
by 1996 8y ago
Thow every best software practice out of the window. It is administration growing more administration. Peer programming is just dividing productivity by two.
To be productive: start vi, code, run the code. No source control. No planning. Just do until you reach your objective.
My way is to iterate and improve. I get in one day what a team gets in a month if they are lucky
And when I don't feel like working, I don't. I wait until I feel the need.
- todd3834 8y agoDo you work primarily alone? How is source control slowing you down? No planning? I would normally never ask this but since this is such a radical suggestion I’d love to see some of your work. I’m guessing no open source without source control. Would you mind sharing some of your public projects so we can see the kind of results to expect from this mindset?
- 1996 8y agoSure, you can check cryptomarketplot.com - but no open source sorry. I work in small team because I like productivity. Why no source control? Same for why not updating the operating system or tweaking the keyboard shortcuts on your editor. Extra things take extra brain power. Remove everything extra to concentrate on the core. No planning is important to concentrate even more on important features: the right moment dictates what you should do right now.
- fouc 8y agohow do you test out changes and revert them easily? (basically how do you backup? git makes this trivial, and doesn't get in the way of anything
- 1996 8y agoThe old way: cp -adr program-v3-withnewfeatureX program-v4 Then work on program-v4 with test deploy until you are happy. Then when ready, change your production deploy scripts to use program-v4, and the "emergency-revert" scripts to use program-v3 Editing 2 scripts is not more complicated that running git commands. That said, I like git. git is nice. But unless you are writing the new linux kernel with tens or hundreds of people you may not need it. I try to remove everything I do not absolutely need and use the simplest hardware I can get away with. Complexity for complexity sake is not productivity.
- tom_ 8y agoI've always been disappointed by people that say they work without source control - because it always turns out they do something like this. Always. And this differs from source control in no meaningful fashion. Once again, my hopes of finding out some interesting new way of working, that I couldn't even imagine: dashed!
- 1996 8y agoThe ways are not so different. The tools are, a bit. As you wisely said, this differs from source control in no meaningful fashion.
- rorykoehler 8y agoCertainly not a team productivity hack haha
- jt2190 8y agoI’ve upvoted you because clearly you’ve expressed an unpopular opinion. ;-)
- dmurray 8y agoYes, pretty much the only responder to have an unpopular opinion. "You can be more productive if you're well rested" and "meetings suck" really don't count.
- 1996 8y agoYes, the post asked for unpopular opinions so I give my very unpopular opinions. I do not understand, why not speak the truth? We all have some unpopular opinions! It is not a beauty contest! Let's be honest with eachother!! Ok, before I go to bed, another unpopular opinion just for you: shell scripts beat more advanced tools. Because with a simple syntax and limited set of tools, there is less room for error. Now time for me to sleep.
- aklemm 8y agoWere you born in 1996?
- gaze 8y agoSo your productivity hacks boil down to doing all the things that most people complain make a developer difficult to work with.