phomer

6 ms·

1.
by phomer 6y ago
http://theprogrammersparadox.blogspot.com/ Nearly 15 years of writing about most aspects of software development. Not really awesome, but it is my attempt to make some sense out of 30 years of software development.
2.
by phomer 6y ago
Location: Toronto Remote: Yes, preferred right now. Willing to relocate: Maybe, later, at some point. Technologies: Go, Java, C, C#, Unix, Windows, etc. Résumé/CV: https://www.linkedin.com/in/paulhomer/ Email
3.
by phomer 7y ago
Location: Toronto Remote: Yes Willing to relocate: No Technologies: Go, Java, C Résumé/CV: https://www.linkedin.com/in/paulhomer/ Email: paulwhomer@gmail.com 30 years of experience. Looking for something new
4.
by phomer 7y ago
It is mentioned a couple times explicitly, but I think most of the readers for this blog would know that the border line for tractable is polynomial growth. Still, it is an interesting observation, worth investigating.
5.
by phomer 7y ago
Yes. Theoretically the algorithm is tractable, but the exponent is so large that it wouldn't be practical to run it in a real environment.
6.
by phomer 14y ago
Interesting. The boss gives a very specific set of requirements, then the programmer disobeys this direct order, goes behind his back to do it differently and has essentially been lying to him or her for months. It doesn't matter if it's th
7.
by phomer 14y ago
Personally I think it is sad. FB tricks people into paying too much, and then some wealthy guy who should have been able to evaluate the offer properly gets fooled, but because he can afford the loss he tries to justify the whole thing, so
8.
by phomer 14y ago
And I have a tail-bone, but no tail ...
9.
by phomer 14y ago
http://theprogrammersparadox.blogspot.ca/2012/02/software-cl...
10.
by phomer 14y ago
The world doesn't need 7 billion programmers, and if people really do want to learn programming then they should learn to do it correctly since the world doesn't need anymore badly written software (we have enough already). Paul.
11.
by phomer 15y ago
When I get paid to work I really care that the work I do is worth the money I am paid. That is, if I'm paid for 40 hours, I feel its important to give my employer 40 hours of good solid work. From time to time, I don't mind going above and
12.
by phomer 16y ago
These were really neat machines. When I worked with them, the dominate language was Pascal and I think they were running a version of X Windows (or at least a similarly powerful windowing system). The funnest part was that we had these util
13.
by phomer 16y ago
I tried at one point to port some software to Amix, way back when it was released. Mostly the OS was OK, but there were some issues with the floating point handling that stopped the port from working properly.
14.
by phomer 16y ago
A designer breaking the rules will generally enhance their work. A coder violating an architecture will often just create long-term technical debt, at the expense of some short-term gain. That is, they'll get their piece done faster, but le
15.
by phomer 16y ago
Actually it is deeper than that. It's really teaching you how to see... (and then draw what you see).
16.
by phomer 16y ago
There are "rules of thumb" which nice people have put together, but they are just a starting point. If you follow the rules pedantically or even closely, the results won't be good. They're just hints to get you going. It's not about obeying
17.
by phomer 16y ago
Programming and Graphic Design are opposites. Logic, reason and lots of self-discipline makes for good programmers. Art on the other hand is grounded in emotion and perception. It's more about escaping discipline, while allowing yourself to
18.
The Effects of Computers(theprogrammersparadox.blogspot.com)
1 points by phomer 16y ago|1 comments
19.
The Decency Manifesto(irrationalfocus.blogspot.com)
1 points by phomer 17y ago|0 comments
20.
by phomer 17y ago
I'm not actually trying to say that programming is the same as typesetting. I just wanted it as an example of a 'profession' that came and went purely because of technology. That's why I went on to describe a model that could minimize progr
21.
Things Every Software Architect Should Know(theprogrammersparadox.blogspot.com)
2 points by phomer 18y ago|0 comments
22.
Code Normal Forms(theprogrammersparadox.blogspot.com)
1 points by phomer 18y ago|0 comments
23.
by phomer 18y ago
The stuff I've always liked is usually really obvious. For example, if it's complex tree code, you don't have to spend a lot of time digging into the details; what the code is trying to do is obvious by its steps. Clean, clear, simple and c
24.
by phomer 18y ago
Oddly, good communication is nearly the complete opposite from good code. Your code should be boring, consistent and obvious. It makes it easier to fix that way. Writing should vary, be inconsistent, approach things from different angles, a
25.
by phomer 18y ago
The deformations are there on purpose, I was trying to give it an edgy style, otherwise it just doesn't appeal to the audience I am trying to reach. I fixed the other typos, as there were unintentional, just a byproduct of fast sloppy editi
26.
by phomer 18y ago
(but read my other articles, you know, the longer ones with more detail :-)
27.
by phomer 18y ago
Generally, I try to write more formally, but then I often get complaints about being too stiff and too long. The crazy bit about blogging is that there is at least one complaint for everything you write. Just proves that you can't make ever
28.
by phomer 18y ago
Yep, it should be wisened. Funny enough, I think my stupid spell checker changed it on me on my last round of proofing. Can't trust these stupid computers, can you?
29.
by phomer 18y ago
CTO's come in a couple of different favors, generally ranging from being very technical to be very 'executive'. At worst they're just an extra layer of management, at best they're the visionaries behind the products. Some code, some just ta
30.
Software Blueprints(theprogrammersparadox.blogspot.com)
1 points by phomer 18y ago|0 comments

More ›