elliotchance

9 ms·

31.
Implementing Repeatable Read and Serializable Transaction Isolation(elliot.land)
2 points by elliotchance 10y ago|0 comments
32.
Parameterized/Data-Driven Tests in Swift(elliot.land)
1 points by elliotchance 10y ago|0 comments
33.
Flow-safe Enums in JavaScript(elliot.land)
1 points by elliotchance 10y ago|0 comments
34.
CollectionFactory: JSON and Objective-C(elliot.land)
1 points by elliotchance 10y ago|0 comments
35.
7 Reasons to Use Concise on Top of PHPUnit(elliot.land)
1 points by elliotchance 10y ago|0 comments
36.
How to Write Your Own Recommendation System(elliot.land)
1 points by elliotchance 10y ago|0 comments
37.
by elliotchance 10y ago
One of my biggest pet peeves is code duplication from lazy copy/pasting. I find it's a good exercise for myself to sometimes pretend like the copy/paste key are not available to me. I had to think about the first one for a mo
38.
by elliotchance 10y ago
That is a fantastically comprehensive list - I was racking my brain for a while to try and think of something before I replied. Not sure if this one is covered already but maybe... Student; is able to ask for help. A lot of these are hard t
39.
by elliotchance 10y ago
Yep, here it is for everyone that doesn't want to waste a browser tab: "I find that when someone's taking time to do something right in the present, they're a perfectionist with no ability to prioritize, whereas when som
40.
by elliotchance 10y ago
#974 is great! I know I have been guilty of #1319, when I really should of just done the repetitive task instead of spending so much time thinking it would save me some time in the future.
41.
by elliotchance 10y ago
Totally agree. I think when people hear the word "lazy" they think "incompetent", like "they didn't know how to solve the problem, so they took a lazy route by not doing it very well" when this is not what
42.
by elliotchance 10y ago
You should totally turn this into a xkcd-like comic ;)
43.
by elliotchance 10y ago
Actually, this is the kind of complexity and misunderstanding that makes software more difficult to maintain. If you step back and understand that the problem is the method name is not clear, creating more code to get around that is totally
44.
by elliotchance 10y ago
For me this falls in to the "understanding" category. The problem your trying to solve and what the client wants are often mixed up as the same thing - but they seldom are. You shouldn't expect that the client will know what
45.
by elliotchance 10y ago
That's great, I'm totally using that: https://twitter.com/elliotchance/status/751926458658852864 . I couldn't find your twitter?
46.
by elliotchance 10y ago
I'm a software engineer. If that's not clear from the article, you should be able to tell from the bio at the top and bottom of the page.
47.
by elliotchance 10y ago
Yes and no. I think we read these things in textbooks and either don't truly understand why they exist until we've made the mistakes or we go too far the other way and start dictating best practice on to everything. It's best
48.
by elliotchance 10y ago
Cheers, great article. Left my own comment ;)
49.
by elliotchance 10y ago
Spot on in my opinion ;)
50.
by elliotchance 10y ago
I'm generally not a fan of recruiters simply because the vast majority of them are sales people first, and tech people second (or often no technical experience at all). Compounded by the fact some people interview very badly but are go
51.
by elliotchance 10y ago
Fresh eyes on the problem is always good, usually after lunch or you have slept on it. I find when my brain starts to grind to a halt I just go an do another un-related task to force myself to completely forget about the original task. It d
52.
by elliotchance 10y ago
Thank you for the kind words :)
53.
by elliotchance 10y ago
Thanks, I've fix it up.
54.
What Makes a Great Software Engineer? Just My Thoughts(elliot.land)
121 points by elliotchance 10y ago|66 comments
55.
Go 1.6 on Elastic Beanstalk(elliot.land)
1 points by elliotchance 10y ago|0 comments
56.
Go: Subtests and Sub-benchmarks(elliot.land)
42 points by elliotchance 10y ago|2 comments
57.
Godoc: Tips and Tricks(elliot.land)
2 points by elliotchance 10y ago|0 comments
58.
Using Reviewable.io for Code Review(elliot.land)
8 points by elliotchance 10y ago|1 comments
59.
Incrementing the Xcode Build Number – Like a Boss(elliot.land)
3 points by elliotchance 10y ago|3 comments
60.
Working with JSON in Go(elliot.land)
1 points by elliotchance 10y ago|0 comments

More ›