<rant> Unfuddle is a grate application. I use it daily. But one thing i really hate about it is that it requires you to use unique public keys. So you can’t use the same public key in two user accounts. Its all OK until you get work in a client’s unfuddle project. Where you will have a different account on the client’s unfuddle app. Boom! now you got to use another different key file just to work with any repo hosted in the client’s unfuddle app. This sucks big time. But the solution is not that complicated. </rant>
To use multiple key files with SSH (Git uses ssh internally),
- Login to the machine/server from where you want to use git/ssh
- Generate a key file (if you don’t already have one generated. But keep in mind you need a key file per account with unfuddle).
- enter a name for the key
- remember the name you entered!
- Edit the ssh client config file
- nano ~/.ssh/config
- enter in the following lines (without the bullets of course!)
- Host whatever.the.host.you.want.to.connect.to.here
- The key file you specify in the Identity File directive is the private key (ie: not the key file with .pub extension).
- Enter you public key to unfuddle
- you can add your key in “Personal Settings”
- your public key is the key that has a “pub” extension
Hope this helps. Even if no one else benifit from this i know i will someday
I did some work on our handheld application framework, which was pretty interesting. And then i had to get this framework feature to be used throughout the whole application. Which is a bit of a boring thing for me to do. And after all i have some other stuff that i need to attend to. So i asked one of my team mates to do it. A relative new comer to the team. He was still learning about our internal application framework and everything else. After working on it for sometime, this what he told me in chat.
4:26 PM *******: mchn i will do this in outlet and and the other supplier list.. give pantrychk and compintl to somebody else.. really boaring(boring) mch doing same thing here and there..
4:27 PM me:
Wow… i wonder how would my boss reply to this if i told him what my teammate told me . But then it must be killing him to work on all the boring stuff. I tried to give him something that is pretty interesting, but… he will have to wait till tomorrow until he gets a external GPS device.
I love OO for a reason. i don’t go around saying that i love OO so that everybody think i know a thing or two about software architecture. but because it have dividends. when you have a good design in your software, things become easy. some planning and some structure can make a lot of things very easy. if you follow OO principals you will have better and simple code. its very simple! you don’t follow OO principals, or any other principal(that have some acceptance, or that you knows to work well) you will end up with UGLY CODE! it might be easy to write ugly code. it might feel very ‘efficient’, ‘high performence’, ‘robust’ code at first. but in the end you will not have much performance gains(well may be about 0.001%, because you decided not to use setters and getters, to save method calls!!!). it will only make thing look bad an ugly. and that’s not all. i can assure you that your code will end up so complicated and full with ‘booby trap type bugs’ waiting to surface and explode.
believe me i know that gut feeling you get when you are writing ugly, unstructured code. when you are writing stuff your mind will be ‘hot enough’ to handle all the complications that arise. so you will be able to wire up things, and put a few FLAGS! here are there and get things working smoothly. and you might feel smart too! but think for a minute. you are not supposed to write code to show how deep the ‘stack of your brain’s cache’ is. it will be hard to understand in the future for your self. and what about others who look in to it? do you really think they want to read complicated code? it is not good to write complicated code. source code is supposed to be human friendly. you don’t need to become a machine. we have more than enough machine’s! think in a higher level people! we have enough processors/RAM and shit! brains are more precious than that stuff!
wow you want to write micro code? no i am not talking about short and straight forward code. i am talking about micro code! why would to want to write something in one line if it takes 2 minutes for someone to understand it, while the same thing could be written in 2 lines, making it easy for people to read. i mean sure it will be the same for the machine(in a given context). i think you should write code that is readable. making it too short while compromising human readability is bad.
every tiny nano/1000000000 second that you TRY to save for your compiler will cost the programmers 5 mins. think about it. is it worth it?
so now all of you(who are stupid and jobless to read this! ) know that this is a rant. now why i am ranting like this? well today i had to do some debugging in a project whose code was ‘tightly coupled’. yeah like really tight!!! the bug was in the UI layer, but i had to go thought the custom controller code(UI), UI code that uses the controllers, business logic… to understand how the “UI” works! the business class that was related to this incident had a property setter that was there just to support a certain feature in UI :O i am so shocked! this is so tightly coupled. but what can i do. i got to debug it anyways
huh… if you have to debug tightly coupled code my advice to you is… first of all claim down. and tell your self that sometimes you got to do things that you don’t like. and start debugging.
As a bored kid(at times) at school i used to draw on any paper that i can find lieing around. or in the back of my books. of which i had a lot of blank space left for stuff that i had yet to do(missed home work…etc). i drew so many stuff on them. mostly i think i drew just random stuff. it was kinda fun and good for passing time. the funny/intresting thing about this is that i liked to draw swirls. i like the way they go around and come around… they can be drawn as deep as you wanted them to be… although if you draw it really deep taking many rounds it will be harder for you to recodnize between the lines… anyways the point is i liked that stuff…
and its no big secret that i am a huge LINUX FAN! there is a very popular distro call debain. i like debain for many reasons. the main reason is that it have a very usable pakage managment system(i love APT!!! <3). most of the distro that i have used in the past and the ones that i am using right now are debian baised ones. and apparently debian have a swirl as it’s logo!
i think this gets even better, been a programmer i always like to sperate concernes when i code stuff. for ex if there are two objects in my program. i would try to make them as independent as possible(less coupling). i do it mainly because it make my work easy and it let me concentrate on sperate pieces of logic at a time. so its easy well this got nothing to do with a swirl… but i tend to use recursion a lot! (they say its bad ) and recursion is what swirls feel like!
well of course this is a rant, some random stuff that was in a coner of my mind…. i think i kinda like speration of concerns + recursion…