asalazar

4 ms·

1.
How to Win at White Elephant(stormpath.com)
1 points by asalazar 12y ago|0 comments
2.
by asalazar 12y ago
In either Scrum or Kanban, it's important to separate your development cycles from when you release or deploy cycle. For example: In Kanban, our developers work in a flow model to get anything and everything they can get done as fast
3.
by asalazar 12y ago
Good point. I think it's wise to due your diligence on the APIs you're considering. Do they have a good track record of availability? Supporting backwards compatibility when they release features? Are they secure? Is it well do
4.
by asalazar 13y ago
If you're following up and are not getting a response then set a limit to the number of times you'll try again. I personally do 3 follow-up email over the course of a 3-6 weeks. On the last email, I let them know it'll be t
5.
by asalazar 13y ago
Hi folks. Author here. Happy to answer any questions if you like.
6.
Hitched to a Start-up Cowboy(siliconvalleytales.com)
1 points by asalazar 13y ago|0 comments
7.
The Art of Irresistible Email(blogs.hbr.org)
1 points by asalazar 13y ago|0 comments
8.
by asalazar 13y ago
Well, at least you now you know we take data very seriously :)
9.
by asalazar 13y ago
Here are three potential reasons. 1. It could just be a random drop in the numbers. The VC world is VERY small and there are VERY few players. Equally, VERY few deals get done every year. Moreover, megadeals can really skew the numbers.
10.
by asalazar 13y ago
Ok here's an analysis on job satisfaction that I found interesting. 1. very weak relationship to high compensation. Not completely surprising and in-line with much of the research. 2. Here's a hard one. No significance of consumer device
11.
by asalazar 13y ago
This just in-- there is a strong and significant relationship between age and years of experience. Who knew?! Also, job satisfaction and new feature dev!
12.
by asalazar 13y ago
More exprienced developers spend more time refactoring code? Does that mean that they're working on crappier code, established code bases, or higher end applications where tech debt really matters? Conversely, are the younger guys spending
13.
by asalazar 13y ago
Meritocracies are great sometimes but they have the nasty side affect of promoting people into jobs they suck at. Just because you're the best at being an individual contributor, it doesn't mean you're going to be a good manager, and being
14.
by asalazar 14y ago
Something the article didn't cover but should is the upkeep over time of whatever algorithm you use. We can argue about todays algorithms. But what do we do when those algorithm are superseded? Or when the minimum complexity factor needs
15.
by asalazar 14y ago
Assuming the attacker has access to your password store is NOT a big assumption for most sites. In fact, 94% of data breaches are to the user DB. And 42% of those attacks are targeting the password store specifically. Check out the Veriz
16.
by asalazar 14y ago
In the words of the great philosopher, Homer-- "Doh!",
17.
by asalazar 14y ago
Love it.
18.
by asalazar 14y ago
This also works with Drupal. Gotta love Cloudflare.
19.
by asalazar 14y ago
I love google, but let's be honest-- it's about time.
20.
by asalazar 14y ago
Hot damn I love when companies open source their code! If its not a core competency or a competitive advantage, open it up and see if the community will help you maintain and advance it.
21.
by asalazar 14y ago
I think the problem is that the "right" way is completely subjective. Is Spring "bad" and Scala "good"? Depends on what you're building and for who. Overall, the best way to be a great developer (not just a good coder) is to: 1) Build a s
22.
by asalazar 14y ago
Good article on the dev side of the problem. Would love to see more on the IT side of the problem too.
23.
by asalazar 14y ago
You can't stop the Android steam roller. It's Windows vs Mac circa 1987 all over again