190 karma · joined March 12, 2011
leaning toward functional techniques has probably had the biggest impact on my productivity in the last 10 years. some of the highest cognitive load in code comes from storing the current state of objects in ones limited memory. removing state and working with transparent functions completely changes the game. once i write a function that i trust does its job i can replace its implementation with its name in my memory and move on to the next one.
one could also mention the electronic scene in there. aphex twin released ventolin in 1995 which was the same track remixed multiples times with different edits.
i was screwed out of over 6 months of pay north of $50k. i wasn't keep tabs on the payments and i wasn't keeping detailed records of my work. both things i no longer let slide in any way. i spoke to many people and lawyers, but decided to move on and let it go.
in the end how much money and time and energy do you want to spend on another lousy human being or entity? it only hurts you emotionally and takes up valuable time to focus on more productive things. ten years later it's a blip in my life that forced me to learn and be better about picking clients and billing, etc. don't let the 10% ruin your work with the other 90%.
;P
oh and loops constructs are not composable...
i would say just a couple of years of vim isn't enough to really become one with the software. think it took me around 5 years to really understand why vim is amazing. took me at least one year just to get the hang of it properly and be highly productive. i can't even type in a normal editor anymore as my brain is wired to vim commands. and i still to this day learn new commands which make my life easier.
that being said i totally understand why people love emacs. but i get a decent amount of the window management stuff just using the tmux.
and vi is installed almost everywhere as an editor which makes editing in 90% of environments a breeze. even when in windows gvim does pretty good.
// pull traits dictionary out of tokens
const extractTraits = R.pipe(
R.map(R.pipe(
R.last,
R.prop('attributes'))),
R.reject(R.isNil),
R.reduce(R.mergeWith(concatValues), {}),
R.map(R.pipe(
R.unless(R.is(Array), R.of),
R.groupBy(R.identity),
R.map(R.count(R.identity)),
R.toPairs,
R.sortBy(R.prop(0)),
R.map(R.zipObj(['name', 'count'])))));but not a fan at all of writing html in clojurescript. it's extremely ugly to look at vs raw html/jsx. and became cumbersome really fast for me as my app grew in size... maybe there are better alternatives now, this was around 5 years ago.
using react with libraries like ramda/redux/rxjs in affect achieve the same thing but with 10x more libraries and references online.
the philosophy behind clojure will completely change how you code and visualize problems if you embrace it. honestly can't remember the last time i wrote a for loop...
Master generalist with 30+ years of hacking experience, 15+ years coding professionally with a dozen languages on over half a dozen platforms. Highly adept at understanding business problems and architecting proper solutions. All development is well documented to ensure easy handoff. We know processes can be important as code. Linkedin has up to date recommendations from our clients. Links available in profile section and contact form at the bottom of website.
We charge day rates of $1,200 w/ a minimum contract of $12k (10 days).
a version of try and either, with a decent do notation taking advantage of for comprehension... https://github.com/papaver/pyfnz
bingo. that is the lesson to be learned. it's all about the journey, not the destination. it really matters zero if you actually ship or release any side projects. all that really matters is the enjoyment working on it.
not sure i agree one way or another, but penny for your thoughts.
libfreetype is an example of a great library, clean and well documented...
beautiful coding isn't a myth, it actually works... write code like poetry and it pays off 10 fold... less errors, easier to reason about, malleable... the benefits are extreme... try to actually experience something before making unfounded claims... i've been writing beautiful for over a decade now... once you realize code is written once and read 100 times, you'll come to the realization of doing it clean and right the first time pays of in the future, which means less work and bullshit...
but once you have other avenues of creativity and life, suddenly working in an office is little more than mundaneness... i've been working remote for over 5 years, and usually do my best to hang out with my team ever few months, mainly to bond on a more personal level which can only be achieved in real time. but a week or two every few months is enough to gain that perspective. working remote is blissful.
there are two major problems. most companies are scared of remote workers because they don't have the trust that remote workers can integrate into the culture, and a large portion of people just can't handle working remotely. it's an art to be able to work without a definite schedule (like being at the office for x hours).
open space work environments are bullshit, read the actual studies done and all of them point to more controlled settings, which allow devs to get into the flow which allow them to produce some of their best work and allow the to be the most fulfilled by their work.
my dollar goes way father than the devs living in sf. i can visit when i want and then bail. i'd rather invest in my family, my house, and my hobbies than paying rent in sf or nyc. and yes there are plenty of cities that offer similar awesomeness for way lower price.
why using a throwaway account? if you are going to dis someone, at least stand up and don't hide.
most all companies ignore emails upon rejection (at least in my exp), don't take it personally.
my experience with svb has been the complete opposite. the initial programming test was short and sweet, shouldn't take much more than an hour. they reached out a bit after i submitted the quiz.
i've had a chance to speak with the crew and they are a great bunch.