Austin Startup

SEPTEMBER 18, 2017

Even when someone is aware of what a CTO does, they often have limited context due to the wide variety of CTO roles. They will manage the steps necessary to identify, select, and integrate your software and IT vendors, including third party product dependencies, email, network, wiki, intranet, project management, and telecommunications.

Fractional CTO 54

Fractional CTO CTO Hire CTO Technical Review 54

Startup Professionals Musings

OCTOBER 30, 2010

Wikipedia started this, but it is also used for technical support, software, and product reviews. Wikis are used to create collaborative websites on a given subject, maintain corporate intranets, and build simple data bases. You can use it for your business.

Internet 224

Internet SEM Wiki Entrepreneur 224

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Bring your questions.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

APRIL 4, 2010

Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Bring your questions.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did).

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

OCTOBER 20, 2008

If engineers want more time to spend making their old code more pretty, they are invited to do so on the weekends. The idea is that once we move to the new system (or coding standard, or API, or.) The current code is spaghetti, but the new code will be elegant. Its become "legacy code" and part of the problem.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

NOVEMBER 22, 2013

And here’s a “ timeline of incidents ” on the GeekFeminism Wiki dating back to 1973, plus a list of sexually objectifying presentations from the past decade. We’ve published our code of conduct , which lays out the conditions for participating in the conference for all us: speakers, sponsors, attendees, staff and volunteers.

Software Review 167

Software Review Lean Hosting Ruby 167

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Both Sides of the Table

NOVEMBER 1, 2009

He published our first wiki where the whole list of potential features were outlined. I know that their are independent software companies now focused on this like UserVoice and Get Satisfaction. Our team lead build a very elegant piece of code for inputting tasks, assigning them, tracking them and reporting on past-due work tasks.

Customer 280

Customer Technical Review Software Review Mexico 280

View from Seed

MAY 14, 2020

We set goals in standup for the day, and monthly goals that we review 1:1 and as a team. Org chart software and setting rules over Slack (like everyone needs to add their real headshot of their face and include their Title/Team and Location) is critical to helping new members get up to speed.

Management 219

Management Hiring Wiki Employee 219

Startup Lessons Learned

OCTOBER 5, 2008

Each specialist takes up his part of the spec (UI, middleware, backend) and cranks out code. So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. In exchange, the team agrees to show each piece of working code to the product manager for his approval.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. For software, the easiest batch to see is code. Every time an engineer checks in code, they are batching up a certain amount of work. This is easiest to see in deployment.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. When a developer wants to check-in code, this is a very scary moment.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.

Software Review 87

Software Review Design Software San Francisco 87

Feld Thoughts

JUNE 22, 2012

I’m a huge fan of William and his writing as you can see from my review of his book Avogadro Corp. There seem to be two schools of thought on how to predict the future of information technology: looking at software or looking at hardware. By day he works on web and social media for HP. Take a look – and take your time.

Artificial Inteligence 182

Artificial Inteligence Technical Review Bandwidth Software Review 182

Both Sides of the Table

AUGUST 23, 2010

And to give credit where it’s due (in addition to the content that Fred producers) a lot of the discussion works well because of the Disqus commenting platform. Only later did I realize that this was part of Dharmesh Shah’s larger blog and that the software was based on the popular “stack overflow&# software.

Silicon Valley 301

Silicon Valley Pre-Money Valuation Technical Review Software Review 301

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Three concepts I found particularly helpful: Process = discipline.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Up and Running

NOVEMBER 5, 2010

I called it A Cool New Tool For Presenting Slides on the Ipad in my positive review on Small Business Trends. I went from there to the apps store to buy the app, which, as you see if you read the review, I like. There’s the idea and then the code, the company and the marketing. And I do like the app, called NonLinear.

Intellectual Property 72

Intellectual Property Software Review Wiki Technical Review 72

Startup Lessons Learned

FEBRUARY 23, 2013

I refined our sketch into a more formal wireframe and workflow and he began to write the infrastructure code necessary to get the data we needed to the presentation layer. Some companies use wikis for their style guides, which allows the collection to stay current and accessible to everyone on the team.

Lean 167

Lean Software Review Wiki Design 167

Startup Lessons Learned

JULY 29, 2009

But there is more to technical debt than just the interest payments that come due. In particular, try these three things: Invest in technical debts that may never come due. Yet there is one silver lining when it does happen: we wind up throwing out working code , debt-riddled and elegantly designed alike.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

AUGUST 2, 2008

Your natural tendency when an investor says yes will be to relax and go back to writing code. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. When an investor says he wants to invest in you, or an acquirer says they want to buy you, dont believe it till you get the check. Bring your questions.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

dontbesoanalytical.blogspot.com

MAY 13, 2012

Consider how firms today confront Web 2.0 – the combination of blogs, wikis, and social networking technologies sprouting up. Of course, this draconian measure does not work; employees can blog under another name, or contribute to a wiki pseudonymously. But if it’s wrong, the CTO has solid documentation to review.

CTO 40

CTO Technical Review Technology Software Review 40

Software By Rob

SEPTEMBER 29, 2009

My Experience Back in 2002/2003 I spent hours writing a sales letter and emailing it to 15 local design firms, offering my services as an outsourced development staff (I coded in PHP,NET and Java at the time). I increased by rate nearly 30% in 3 months due to the amount of work coming my way. 9 comments ↓ #1 Robert on 09.29.09

Software Review 53

Software Review Developer RSS Software Developers 53

ConversionXL

JANUARY 12, 2017

For example, a key principle of Web accessibility is designing Web sites and software that are flexible to meet different user needs, preferences, and situations. site authoring, multimedia authoring, blog authoring, wiki authoring) more accessible. Expert Web Accessibility Reviewers. Reflect the reading order in the code order.

Web 48

Web Software Review Technical Review Canada 48

bizthoughts.mikelee.org

MARCH 8, 2012

Active software engineers probably get two offers a month or more. I was able to hire phenomenal software engineers and grow a strong team culture. Learn to write code yourself. link] # 4 hours ago Going #lean and testing with imagemaps, cuz concepts are cheap and code is expensive. # YHOO ) in its second act.

Technical Cofounder 40

Technical Cofounder Cofounder Technical Review Software Review 40

Startup Lessons Learned

MAY 31, 2010

And a special thanks is due to all of our presenters, panelists, and mentors. Kent Beck is deservedly famous for his many contributions in the software industry. Unfortunately, the video of our sllconf conversation is not online (due to technical problems), but we have a physical tape backup which we are endeavoring to get online soon.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JUNE 17, 2010

I was the junior guy on a project team; I was called in to do some technical due diligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it. And like feedback on a simple microphone sound system, this would occasionally boil over into screeching.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

FEBRUARY 22, 2009

See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding? We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. Can I send you a review copy?

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Andrew Payne

MAY 29, 2009

And, a review of the email trail has settled more than one “you never told me!” We each have shared calendars, one calendar for each of the kids, and a “guest/vacation/family activity calendar” Private wiki (access controlled). The key here is a good scanner and simple software to scan and file.

Management 40

Management Technical Review Wiki Software Review 40

Startup Lessons Learned

MAY 14, 2009

Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. This shift allowed us to crank out working software quickly as a service. It was a disaster.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

SEPTEMBER 15, 2008

Code To make split-testing pervasive, it has to be incredibly easy. The only change you have to get used to as you start to code in this style, is to wrap your changes in a simple one-line condition. Now, it may be that these code examples have scared off our non-technical friends. October 4, 2008 10:33 AM Amitt Mahajan said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

JULY 5, 2010

When I wrote a review of Four Steps on this blog in November, 2008, I did my best to be candid and warn of a few shortcomings: And Steve is the first to admit that its a "turgid" read, without a great deal of narrative flow. Four Steps primarily centers its stories and case studies on B2B hardware and software startups.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

AUGUST 26, 2009

Im also excited to share two long-form reviews from actual attendees. More recently it's skewed to software & web. Revisiting the Software Design Manifesto (and what. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. There used to be a ton of storage startups here.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

NOVEMBER 13, 2008

A new bit of code contained an infinite loop! why did that code get written? Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Most engineers would ship code to production on their first day.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

AUGUST 24, 2009

When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. For example, the best book reviewers only review books published by the best publishers, which only accept manuscripts from the best agents. And how could they possibly review a blog? Is that a lot? Is that good?

San Francisco 113

San Francisco Lean Technical Review Distribution 113