gbvb

7 ms·

31.
by gbvb 14y ago
The interesting part about timestamping change to records is essentially "effective dating" and it is bread and butter in any transactional system that needs to record employee info. This is done varying degrees to columnar values or entire
32.
Buy vs. Build: An eternal Dilemma(yetanothersoftwareguy.com)
1 points by gbvb 14y ago|0 comments
33.
Ambient Theme : Sets your theme's background based on ambient light(vim.org)
1 points by gbvb 14y ago|0 comments
34.
by gbvb 14y ago
I thought 140 characters making or breaking relations was somehow frivolous. I did not realize that those clients had a relationship weight associated with them as well.
35.
by gbvb 14y ago
You can hold Option button and click on battery to see the remaining time on battery. Interesting project though..
36.
Is Agile architect an Oxymoron?(yetanothersoftwareguy.com)
1 points by gbvb 14y ago|0 comments
37.
by gbvb 14y ago
I guess this is software's version of security theater. Make the users feel like the website is secure because there is a javascript running on the login screen to prevent you from pasting, never mind that you can probably not use pass phra
38.
Font that creates charts(fontfont.com)
321 points by gbvb 14y ago|61 comments
39.
Are APIs precious?(stackoverflow.com)
1 points by gbvb 14y ago|0 comments
40.
by gbvb 14y ago
To the martians, of course. Don't you think they will have tax payer concerns like the rest of us? why do you think they have not visited us in such a long time. :)
41.
Evernote founder interview.. (guardian.co.uk)
1 points by gbvb 14y ago|0 comments
42.
by gbvb 14y ago
I agree. I was commenting on Facebook "the social network" and not Facebook the "technology".. :) Anything that can be made to support such large transactions (be it with duct tape and glue) has to have a core capability to support such usa
43.
by gbvb 14y ago
And his point still stands. :) Could not resist.
44.
by gbvb 14y ago
That is Beautiful!Now, can we get that on emacs..:)
45.
by gbvb 15y ago
Ok. I was making a point but I guess you are right about lint. I was trying to point out that it is easy have developers write code that can easily be O(n2) vs O(n log n) because this did not use the right kind of the maps when they were
46.
by gbvb 15y ago
I believe Any senior engineer worth his salt should be able to do lint style verification of someone else's code quickly. When I am expecting someone to be a senior enough engineer, they should be able to look at someone's code during Code
47.
by gbvb 15y ago
IMO, many times the ugliness of the code reflects the brittle thinking of the architect/designer of the application. If it is designed to expect [rigid design] certain set of rules and not accomodate new and changing requirements, or if it
48.
by gbvb 15y ago
I am really not underestimating the effort. But there are multiple pieces to what you just talked about. There are complexities in time measurement (or computing how much work was done) and in payroll calculation. When systems of this sort
49.
by gbvb 15y ago
I totally agree. but, It is not impossible. The problem with Payroll is that it is like Security. When everything is working, no one notices its presence. Any issues are incredibly important to fix. That said, there are ways to develop payr
50.
by gbvb 15y ago
Actually, it is feasible. It is possible to do this still. Solve it with a model to start and chain the calculation events. You can re-iterate based on the different situations. The design, when thought through, can be accommodating such va
51.
by gbvb 15y ago
:)
52.
by gbvb 15y ago
Actually, Payroll systems can be structured. In the end, there are only 3 things that you need to provide: - compensation (money employee makes) - deduction (money employee gives for some service) - taxes (employee owes the government) Ever