ajohnson1200 + software   81

Engineering Deadlines: How Engineers Benefit From Delivery Dates
Quote: "Deadlines help us stay focused, aligned and driven – and can be used to keep project scope in check"
roadmap  dates  deadlines  software  productmanagement 
10 days ago by ajohnson1200
Migrations: the sole scalable fix to tech debt.
Quote: "Lore tells us that Googlers have a phrase, "Running to stand still", to describe a team whose entire capacity is consumed in upgrading dependencies and patterns, such that it can't make forward progress on the product/system they own."
engineering  programming  development  devops  software 
april 2018 by ajohnson1200
Security and privacy, startups, and the Internet of Things: some thoughts (31 Oct., 2017, at Interconnected)
Quote: "Building your own artisan stack feels like an expensive indulgence in most cases. The line to keep in mind is Werner Vogal's maxim - Vogal the CTO of Amazon - his maxim of no undifferentiated heavy lifting. That is, don't put significant engineering resource into stuff that isn't your core business."
security  privacy  architecture  software  amazon  wernervogels 
november 2017 by ajohnson1200
Products Over Projects
Quote: "Traditional enterprise IT has followed the two-pronged city model of permanent “run” teams and on-demand “change teams” i.e. the “projects” approach, and have paid the price in terms of responsiveness to the business. Digital-age business can ill afford to be sluggish in responding to feedback from business stakeholders or the market. Business-capability aligned teams need to have the level of funding, staffing and authority to switch focus or pivot their approach to a problem on the fly...
agile  development  software  product 
november 2017 by ajohnson1200
Software 2.0 – Andrej Karpathy – Medium
Quote: "Software 2.0 is not going to replace 1.0 (indeed, a large amount of 1.0 infrastructure is needed for training and inference to “compile” 2.0 code), but it is going to take over increasingly large portions of what Software 1.0 is responsible for today. Let’s examine some examples of the ongoing transition to make this more concrete..." The ".. increasingly large portions of what Software 1.0 is.." seems like a stretch since the vast majority of code in the world isn't doing speech recogn...
ai  programming  software  machinelearning  future  ml 
november 2017 by ajohnson1200
GitHub - kamranahmedse/developer-roadmap: Roadmap to becoming a web developer in 2017
Great infographic illustrating the complexity of being a front end / back end / devops engineer in 2017.
career  software  complexity 
june 2017 by ajohnson1200
44 engineering management lessons
First bookmark in years... takes 10 minutes to read, could spend 30 minutes on each point.
engineering  management  software  leadership 
may 2017 by ajohnson1200
The Stack That Helped Medium Drive 2.6 Millennia of Reading Time — Medium Engineering — Medium
Interesting rundown of the tech behind Medium, interestingly it looks like they only do about ~1m page views per day (assuming ~1 page view per unique user which seems like what the average would be). Interesting to note the use of ELK (Elasticsearch, Logstash, Kibana), which is the second time I've heard that recently.
elk  amazon  medium  scalability  engineering  software 
november 2015 by ajohnson1200
Office, messaging and verbs — Benedict Evans
Lots of great stuff in here, excerpt: "Just as today we make web app copies of software models conceived for the floppy disk, so the first PCs were often used to type up memos that were then printed out and sent though internal mail. It took time for email to replace internal mail and even longer for people to stop emailing Word files as attachments. Equally, we went from typing expense forms (with carbon copies) to entering them into a Word doc version of the form, to a dedicated Windows app that looked just like the form, to a web page that looked just like the form - and then, suddenly, someone worked out that maybe you should just take a photo of the receipt. It takes time, but sooner or later we stop replicating the old methods with the new tools and find new methods to fit the new tools.  

Hence, channeling Marshall McLuhan, new tools start out being made to fit the existing workflows, but over time the workflows change to fit the tools."
productivity  software  collaboration  work  workflow  tools 
july 2015 by ajohnson1200
Post-Mortems at HubSpot: What I Learned From 250 Whys
Some great points here:
- Let's Plan for a Future Where We're All As Stupid as We Are Today
- Less Root Cause, More Broadest Fix
- Err on the Side of MTTR, Not MTBF
- Never Let "Slow Down" Be The Answer
failure  management  software  root-cause-assessment  rca  problem-solving 
april 2015 by ajohnson1200
f.lux: software to make your life better
Trying it out now at 8:30pm, *feels* better already.
health  osx  mac  software  sleep  life  lifehacks 
february 2015 by ajohnson1200
Coordinating technological change in large software organizations
Quote: "Part of what distinguishes great infrastructure teams is a sense of empathy for those that depend on them. When attempting to move an organization forward with a new technology, such a team will reduce the barrier to entry by addressing any likely concerns and minimizing the amount of work that developers have to do to make the switch. By going the extra mile to ease the lives of others, the team initiating the change improves the likelihood of success and greases the wheels of forward progress."
startups  infrastructure  management  software  development 
july 2014 by ajohnson1200
Twitter / pamelafox: PSA: You can toggle browser ...
Command Option I for Chrome Developer Tools... money.
chrome  tools  software  tips 
june 2014 by ajohnson1200
Disk Inventory X
Exceptional little tool for figuring out where you're using disk on OSX.
mac  osx  software  tools 
june 2014 by ajohnson1200
illumos developer > 2013 > May > need reviews for..
Quote: "Empathy is a core engineering value.

This is especially true when it comes to backward compatibility, even
moreso when targeting environments in which your product is used to make
money. There are plenty of situations in which it's easy enough to say
"don't do that, then" and leave it at that. Like most engineers, I have
little patience for people who refuse to read the manual, make
assumptions about the system's behaviour from unreasonable bases, or
engage in obviously retarded diagnostic procedures that serve only to
worsen the original problem. All that said, there are also plenty of
instances in which it's essential to at least attempt to understand the
plight of our users. This is one of them."
culture  development  empathy  engineering  software 
january 2014 by ajohnson1200
PeteSearch: Things users don't care about
Quote: "How long you spent on it. How hard it was to implement. How clean your architecture is. How extensible it is. How well it runs on your machine. How great it will be once all their friends are on it. How amazing the next version will be. Whose fault the problems are. What you think they should be interested in. What you expected. What you were promised. How important this is to you."
software  development  priorities  ux 
january 2013 by ajohnson1200
Rands In Repose: Stables and Volatiles
Quote: "Your Stables are there to remind you about reality and to define process whereby large groups of people can be coordinated to actually get work done. Your Stables bring predictability, repeatability, credibility to your execution, and you need to build a world where they can thrive.

Your Volatiles are there to remind you that nothing lasts, and that the world is full of Volatiles who consider it their mission in life to replace the inefficient, boring, and uninspired. You can’t actually build them a world because they’ll think you’re up to something Stable, so you need to create a corner of the building where they can disrupt."

engineering  software  entrepreneurship  management 
november 2012 by ajohnson1200
Play Offense When Predicting Revenue
Same thing can / should be applied to bigger software releases: instead of asking if the release will go out on time, ask which features are 100% done and bug free and which features need more work.
sales  management  engineering  software 
november 2012 by ajohnson1200
Call Me Fishmeal.: Success, and Farming vs. Mining
Lots of quotable stuff in this article but I liked the close: "The secret of success turns out to be so incredibly simple: Work your ass off. Really care about what you're creating, not the fame or fortune you'll get. You'll succeed."
business  culture  entrepreneurship  software  startup 
april 2011 by ajohnson1200
OmniTI ~ On the Engineering of SaaS
Great article on the difference between on prem and SaaS software, excerpt: "An upgrade process, for example, is an entirely different beast. Making it robust and repeatable is far less important than making it quick and reversible. This is because the upgrade only ever happens once: on your install. Also, it only ever has to work right in one, exact variant of the environment: yours. And while typical customers of software can schedule an outage to perform an upgrade, scheduling downtime in SaaS is nearly impossible. So, you must be able to deploy new releases quickly, if not entirely seamlessly — and in the event of failure, rollback just as rapidly."
saas  engineering  software  deployment  qa  agile  testing 
april 2011 by ajohnson1200
Notes from the Agile UX Retreat at Cooper - Anders Ramsay.com
Quote: "... The idea that UX should be more a competency and less a role resonated strongly. Alan likened the software team to a sports team on a field, in which everyone has set roles but their actual work can be fluid across the field/project."
ui  ux  agile  softwareengineering  software  design 
june 2010 by ajohnson1200
ongoing by Tim Bray · HTML5 and the Web
Quote: "HTML5 promises to broaden the class of application problems you can solve with HTML, providing a good user experience while saving time and money. But that’s all; it’s not better because it’s “Web Technology”, it’s better because it’s better.

Except when it isn’t. Right now, there are certain classes of applications, particularly on mobile devices, where you’re going to get a better result by building a native app. Maybe even by building two or three native apps, for iPhone and Android and webOS. This is entirely orthogonal to the “Webbiness” (or not) of the technologies.

And another point: building a really hot HTML5 application that takes advantage of the nice new features is not exactly easy. Even assuming that you’re using one of the dozens of clever toolkits, it’s still not a slam-dunk. In fact, compared to the level of support and tooling you get from XCode on the Apple side or the various pieces of Android IDE-ware, HTML5 development is a major pain in the ass."
mobile  html  html5  software  ria 
may 2010 by ajohnson1200
The end of the killer feature « Scott Berkun
Quote: ".. But today, with websites, iPhone apps, and web browser plugins. new feature additions are cheap(er) and can roll in at any time: the feature set matters, but it matters less. What matters more are the overall user experience and the quality and depth of the plugins/apps available for people to use."
software  innovation  upgrades  appstore  plugins 
april 2010 by ajohnson1200
Thunderbird in 2010 @ david ascher
Quote: If we have an idea for a change to an existing Thunderbird feature, we’d like to roll it out first as an add-on, so that we can get feedback on early versions of the idea without having to incur all of the up-front costs of landing that change into the “trunk” builds. This should allow us to validate (or reject) ideas much faster. A great example of how this can work is the Personas feature, which matured as an add-on, and is now a standard (and awesome) feature of Firefox 3.6.
innovation  mozilla  software  plugins  iteration 
march 2010 by ajohnson1200
ongoing · Doing It Wrong
Quote: "The community of developers whose work you see on the Web, who probably don’t know what ADO or UML or JPA even stand for, deploy better systems at less cost in less time at lower risk than we see in the Enterprise. This is true even when you factor in the greater flexibility and velocity of startups.

This is unacceptable. The Fortune 1,000 are bleeding money and missing huge opportunities to excel and compete. I’m not going to say that these are low-hanging fruit, because if it were easy to bridge this gap, it’d have been bridged. But the gap is so big, the rewards are so huge, that it’s time for some serious bridge-building investment. I don’t know what my future is right now, but this seems by far the most important thing for my profession to be working on."
enterprise  software  business  web  web2.0  agile 
january 2010 by ajohnson1200
Semantic Versioning
I propose a simple set of rules and requirements that dictate how version numbers are assigned and incremented. For this system to work, you first need to declare a public API. This may consist of documentation or be enforced by the code itself. Regardless, it is important that this API be clear and precise. Once you identify your public API, you communicate changes to it with specific increments to your version number. Consider a version format of X.Y.Z (Major.Minor.Patch). Bug fixes not affecting the API increment the patch version, backwards compatible API additions/changes increment the minor version, and backwards incompatible API changes increment the major version.
development  software  api  specification  versioning 
december 2009 by ajohnson1200
The Duct Tape Programmer - Joel on Software
*Great* blog post by Joel Spolsky, quote: "At the end of the day, ship the fucking thing! It’s great to rewrite your code and make it cleaner and by the third time it’ll actually be pretty. But that’s not the point—you’re not here to write code; you’re here to ship products."
programming  development  softwareengineering  software  process 
september 2009 by ajohnson1200
.: Fail Fast, Debugging and Systems that Never Stop
Quote: There are two advantages to failing fast. First, easier debugging and analysis. ...Second, ability to build "systems that never stop".
concurrency  design  distributed  programming  software 
august 2009 by ajohnson1200
Nick Bradbury: If You Want to Write Useful Software, You Have to Do Tech Support
Quote: If you really want to write useful software, stop spending all your time keeping up with technology. Don't worry if your resume isn't filled with the latest buzzwords. Instead, invest your time in talking with your customers. They don't care what programming language you use - they only care whether your software meets their needs, and the best way to ensure that is by breaking out of your cone of silence and opening the lines of communication.
business  development  support  customerservice  software 
august 2009 by ajohnson1200
Fabulous Adventures In Coding : Future-Proofing A Design
Quote: Premature generality is expensive. Designing code to be future-proof without a clear understanding of what the future holds often leads to excess generality; generality has very real costs, and they might be higher than the benefit accrued.
software  programming  architecture  change  future-proofing 
january 2009 by ajohnson1200
Anatomy of a Software Development Role: Development Manager II
Great series (thanks Gato!) on the roles / titles of a software development organization.
software  development  management  roles 
january 2009 by ajohnson1200
HTTP Client - Mac Developer Tool for HTTP Debugging
Still not as amazing as Fiddler, but a nice substitute if you're not on Windows.
software  http  debugging  osx  tools 
december 2008 by ajohnson1200
Coding Horror: The One Thing Every Software Engineer Should Know
Quote: "Just because you're a marketer doesn't necessarily mean you're a marketing weasel. Sure, the two things are highly correlated -- but at its core, marketing is little more than an intermediate level course on fundamental human communication. Not something us programmers have historically been so great at. "
software  programming  marketing  engineering 
october 2008 by ajohnson1200
Product Parenting
Mostly about product management. Quote: "Unlike your coworkers, software products deserve to be treated very much like children. They're rebellious and wayward. They need to be given strict boundaries and lots of guidance."
productmanagement  management  software  business 
october 2008 by ajohnson1200
Rands In Repose: The Culture Chart
Quote: "Unlike the org chart, you’re not going to find the culture chart written down anywhere. It doesn’t exist. The culture chart is an unwritten representation of the culture of your company and understanding it answers big questions that you must know: * What does this organization value? * Who created this value system? * Given this value system, who contributes high value? * Who is most aware of how value is being created?"
strategy  software  culture  value 
october 2008 by ajohnson1200
scottberkun.com » How to run a bug bash
Good stuff on bug bashes. Funny though: we started bug bashes on Clearspace last year, I had no idea that bug bash actually has it's own wikipedia page.
testing  software  quality  qa 
october 2008 by ajohnson1200
Apple Developer Connection - Bug Reporting
Extremely thorough guide to reporting bugs on Apple products.
testing  support  software  troubleshooting  bugs 
september 2008 by ajohnson1200
Rail Spikes: Testing is overrated
Quote: ...the truth is, no single technique is effective at detecting all defects. We need manual testing, peer reviews, usability testing and developer testing (and that’s just the start) if we want to produce high-quality software.

Great article BTW.
usability  software  testing  quality 
august 2008 by ajohnson1200
Coding Horror: Quantity Always Trumps Quality
Quote: Rather than agonizing over whether you're building the right thing, just build it. And if that one doesn't work, keep building until you get one that does.
software  quality  programming 
august 2008 by ajohnson1200
MSFTextrememakeover: Eight Years of Wrongness
A *long* blog post about Microsoft underperforming. Props to Writer at the end.
business  microsoft  software  strategy 
june 2008 by ajohnson1200
Unit Structures: Productive Unit Structures: Introducing Freedom
Quote: "Freedom is a Mac application that disables your computer's networking capabilities for a selected time interval." I've found the 1.5 hours I spend on the bus everyday to be the most productive time of my day.
productivity  apple  mac  osx  software  networking  time 
april 2008 by ajohnson1200
Manageability - How To Build Damn Good Software
Graham Glass (Mind Electric fame) and John Wiegand and Erich Gamma (both of Eclipse fame) share a few morsels of wisdom on how to build good software.
management  software  development  java  process  methodology 
january 2008 by ajohnson1200
Coding Horror: Sharing The Customer's Pain
Quote: "Many Amazonians have to spend some time with customer service every two years, actually listening to customer service calls, answering customer service e-mails, really understanding the impact of the kinds of things they do as technologists."
amazon  customerfocus  engineering  software  culture 
december 2007 by ajohnson1200
A great plugin for iPhoto that gives you the ability to plop your photos right into Flickr.
iphoto  flickr  photos  photogallery  plugins  mac  osx  software  tools 
august 2007 by ajohnson1200
Ted Leung on the Air » Blog Archive » OSCON 2007
"... automated/numerical reputation metrics [are] of little value."
reputation  social  status  software  people 
august 2007 by ajohnson1200
Get Vanilla!
"... open-source, standards-compliant, multi-lingual, fully extensible discussion forum for the web...", built in PHP.
forums  community  free  opensource  php  software  mysql 
october 2006 by ajohnson1200
JSMIN, The JavaScript Minifier
A filter which removes comments and unnecessary whitespace from JavaScript files
javascript  optimization  ajax  software  hacks 
october 2006 by ajohnson1200
MF Bliki: CustomerAffinity
Struck a chord with me: "The real intellectual challenge of business software is figuring out what the real contribution of software can be to a business. You need both good technical and business knowledge to find that."
business  software  customer  affinity 
july 2006 by ajohnson1200
Virtual desktops for mac os x.
mac  software  osx  virtual  apple 
july 2006 by ajohnson1200
Deliwin - A del.icio.us bookmark manager client
Stores all your del.icio.us bookmarks in the system tray, pretty cool way to see the tags you're using.
del.icio.us  software  free  bookmarks 
july 2006 by ajohnson1200
La Chose - Doodim
Cool mac os x application that dims the background of the foremost application.
osx  free  software  gui 
june 2006 by ajohnson1200
Test Run: Home
A cool tool for QA people: free for single users, also a hosted or a downloadable versions.
qa  testing  software  php 
november 2005 by ajohnson1200
Reading List: Fog Creek Software Management Training Program - Joel on Software
Great list of books to read over the Thanksgiving holiday weekend...err... maybe the next 12 Thanksgiving holiday weekends.
books  toread  software 
november 2005 by ajohnson1200
Joel on Software - The Joel Test: 12 Steps to Better Code
We're trying to get pass the Joel Test at at work, quiet working conditions is going to be the hardest to pass.
software  quality 
october 2005 by ajohnson1200
Bogle’s Blog » Jobster Tools and Technology
Phil Bogle lists out the various technologies they use over at Jobster.
jobster  opensource  software 
september 2005 by ajohnson1200
Paparazzi: Quick and Dirty UAV
An attempt to build a cheap fixed wing autonomous MAV (Micro Air Vehicle)
uav  software 
june 2005 by ajohnson1200
« earlier      
per page:    204080120160

related tags

affinity  agile  ai  ajax  amazon  api  apple  appstore  architecture  blogs  bookmarks  books  bugs  business  career  chandler  change  chrome  cloud  collaboration  community  complexity  concurrency  crowdsourcing  culture  customer  customerfocus  customerservice  dates  deadlines  debugging  del.icio.us  deployment  design  development  devops  distributed  documentation  elk  empathy  engineering  enterprise  entrepreneurship  failure  flickr  forums  free  functionaldesign  functionalspec  future  future-proofing  google  gui  hacks  health  hme  html  html5  http  idea  ideas  infrastructure  innovation  interview  iphoto  iteration  java  javascript  jobster  law  leadership  life  lifehacks  mac  machinelearning  management  mapping  marketing  medium  methodology  microsoft  ml  mobile  mozilla  mysql  networking  onprem  opensource  ops  optimization  osx  patents  people  photogallery  photos  php  pim  plugins  presentation  presentations  pricing  priorities  privacy  problem-solving  process  product  productivity  productmanagement  programming  qa  quality  questions  quotes  rca  reference  reputation  requirements  ria  roadmap  roles  root-cause-assessment  saas  sales  scalability  security  shits-easy-syndrome  sleep  sliderocket  social  software  softwareengineering  specification  startup  startups  status  strategy  streams  support  terraform  testing  time  tips  tivo  tools  toread  troubleshooting  uav  ui  upgrades  usability  ux  value  versioning  videos  virtual  web  web2.0  wernervogels  work  workflow 

Copy this bookmark: