brettlangdon

12 ms·

61.
by brettlangdon 11y ago
I rather like the one quote that is used for this post: > If you tell the truth, it becomes a part of your past. If you lie, it becomes a part of your future. Cultivating an "I don't know" environment is really just helpin
62.
Encouraging an I don't know culture(particular.net)
3 points by brettlangdon 11y ago|2 comments
63.
by brettlangdon 11y ago
This is a great article. You don't usually think about all the engineering tasks behind a company rebranding.
64.
Why It Took Us Two Months to Rebrand ChallengePost to Devpost(blog.underdog.io)
6 points by brettlangdon 11y ago|3 comments
65.
by brettlangdon 11y ago
I threw this document together quick trying to break down the "unit" (per week) price of each coding school mentioned in the article. https://docs.google.com/spreadsheets/d/1wKfEzO860nn_2AuKx5fD... The m
66.
Before You Learn to Code, Ask Yourself Why(blog.underdog.io)
13 points by brettlangdon 11y ago|3 comments
67.
A look inside engineering at Plated(blog.underdog.io)
5 points by brettlangdon 11y ago|1 comments
68.
by brettlangdon 11y ago
Yeah, I agree. As developers most of us want to develop the best that we can all the time, either new features or cleaning up technical debt, but the pressure from the business to always push to get things done as quickly as possible is ver
69.
by brettlangdon 11y ago
Interesting post, there is however one main point about the agile process missing from the post, and maybe this just goes to show how many organizations are doing it wrong, but retrospectives are a large part that makes not just agile work
70.
by brettlangdon 11y ago
Was mostly just how it turned out. A lot of the decisions were mostly arbitrary, I wanted something that look/felt like an nginx config but was more generic (didn't have application specific directives), it just so happened to end
71.
by brettlangdon 11y ago
Thank you. This does a great job of summing up the article. It was exactly what I hoped people would take away from it.
72.
by brettlangdon 11y ago
If we are always expected to write new, different, useful, quality code that solves real problems, then no one would ever start programming in the first place. Everyone needs to start somewhere and maybe for a veteran coder the expectation
73.
by brettlangdon 11y ago
I totally agree with this. And is actually a really good point I missed in my article. You cannot, and should not, force yourself to sit in front of the computer non-stop just because you "should". You need to take those breaks to
74.
Facette.io Time series data visualization and graphing software(facette.io)
2 points by brettlangdon 11y ago|0 comments
75.
Write code every day(brett.is)
65 points by brettlangdon 11y ago|63 comments
76.
by brettlangdon 11y ago
I like to take walks. Sometimes when there is too much going on, I'm a little too restless or I just can't focus. I'll just get up and go for a short walk, try to clear my head, maybe tire myself out a bit. Usually gets me a
77.
Write code every day(brett.is)
3 points by brettlangdon 11y ago|1 comments
78.
Facette.io Time series data visualization and graphing software(facette.io)
2 points by brettlangdon 11y ago|0 comments
79.
A metalsmith plugin that outputs the time elapsed between calls to it(github.com)
1 points by brettlangdon 11y ago|0 comments
80.
by brettlangdon 11y ago
Great post, thanks for sharing.
81.
by brettlangdon 11y ago
Speaking from experience as one of the two current software engineers at Underdog.io. This is a great team to work with, we all strongly believe in the product and being so small (only 4 employees right now) we all get a lot of say in the d
82.
GothamGo early bird tickets on sale now(gothamgo.com)
1 points by brettlangdon 11y ago|0 comments
83.
by brettlangdon 11y ago
Seconded, really great book, super easy read.
84.
by brettlangdon 11y ago
The project can be found on github here: https://github.com/brettlangdon/forge
85.
Forge golang configuration parser(brett.is)
5 points by brettlangdon 11y ago|1 comments
86.
by brettlangdon 11y ago
I can speak from my own experiences reviewing engineering candidates. Sometimes when you see someone's resume and they have great work accomplishments, like "last 4 years at [successful, engineering focused company], building thei
87.
by brettlangdon 11y ago
Obviously everyone is different in how they review resumes, but I am Software Engineer and whenever I see a resume with a github, I'll usually visit that first before even reading the rest of their resume. Since I work in and around Gi
88.
Microcomitting development methodology(theworstprogrammerever.com)
1 points by brettlangdon 11y ago|0 comments
89.
Golang config syntax and parser(github.com)
2 points by brettlangdon 11y ago|0 comments
90.
by brettlangdon 11y ago
Neat. I have used a few different tools in the past. https://code.stypi.com/ - shared code editor in the browser Just use hangouts (we are using https://appear.in/ now, much better) and have them screenshar

More ›