10 best practices from top coders at Google, Pinterest & more

At VentureBeat’s DevBeat conference next week, we’re doing things a little differently. You won’t be invited to speak on stage if you can’t code, and we’re setting up practical workshops so you’ll actually learn something and not just be lectured to.

In the spirit of collaboration, I asked some of the most talented web and mobile programmers in my network for their tips. You don’t become a great developer overnight; it takes tenacity, skill, and a willingness to spend many an evening glued to a computer screen.

The most talented programmers have made plenty of mistakes. Here’s what they learned along the way.

A special thanks to Altay Guvench, founder of Silicon Valley tech talentagency 10x Management for helping me compile some philosophical and hands-on advice!

1. Think carefully before you choose your first language

“Programming languages differ, but not a lot. The people who use a programming language differ much more. When you choose a language, you’re choosing a community.”  – Sam Kaufman, a freelance iOS developer represented by 10x management

“If you want to prototype fast (especially for founders, who want to iterate on a product), go with either Ruby or Javascript.” – Erin Parker, founder and lead developer of Spitfire Athlete 

2. You’re no code monkey!

“Great developers can architect and build applications. Amazing developers do it with an eye focused on the business. Most people on the business side of the house can’t code, but you certainly can understand the motivations behind a particular feature.

“Too often developers just build what they are told without understanding why they are building it resulting in missed opportunities on both sides.” – John Coggeshall, a freelance web developer represented by 10x Management; a core contributor to PHP

“Becoming great at programming is a noble professional goal. Once you’re there, don’t forget to think about yourself. Do not become any company’s serf or otherwise trade your time on Earth for tchotchkes.” — Greg Sadetsky, a Quebec-based Python and Javascript expert represented by 10x Management; founder of Abri.co, a co-working space

“To meet a deadline, do project communication work ahead of doing technical work (even if it isn’t a prerequisite), because there’s more variance in how quickly other people are able to respond.” – Andrew Wilcox, a web application developer and core contributor to Meteor, represented by 10x Management

3. Stay agile and don’t stop shipping

“Release early, often, and with rap music.” – Max Nanis, a San Diego-based freelance web developer and bioinformatics expert; represented by 10x Management

“Always be testing.  A good test suite is a cross between an insurance policy and a canary in the coal mine.  It can help you find bugs much earlier in the production cycle, and early bugs are usually easy bugs.” – Jeremy Green, freelance web developer who specializes in Ruby on Rails represented by 10x Management

“Fail Fast. In coding (and in life), I want to know at the earliest possible point that something is broken or not working, rather than let it sit and propagate further. Go all in, fail quickly, fix what’s broken, and keep on keeping on,” – Stephanie Volftsun, cofounder and CTO at Knotch

“Write automated tests for all your code! Practice test driven development as much as possible.” – Zoran Kacic-Alesic, R&D Supervisor at Industrial Light & Magic

“Always be shipping. Don’t ship shit.” – Chris Garvis, former lead software engineer at Moveline and former director of backend development for iVillage; represented by 10x Management

4. Stay in control of the testing process 

“Many of the projects suffer from multiple cycles of testing. This adds to delays of projects and causes high-level issues for the organization as a whole.

“Programmers should focus on unit testing their code and semi-regression testing of their code. They know the codebase better than anyone and what changes they impact. Sometimes such changes are missed because QA is testing limited scope, and in turn causes issues in production which can be of significant import.” – Sanjib Sahoo, chief technology officer at tradeMONSTER

“To build defect-free code as quickly as humanly possible, never, ever, say you’ll write the tests later. We know better. Measure test coverage and keep it at 100 percent.” – Seth Purcell, VP of Engineering at Signpost

5. If you’re a freelancer, learn to say no, even to money

“Take any reasonable estimate of time and cost, and double it. If anyone says, ‘This should be straightforward,’ run.” – Ryan Waggoner, freelance web application and mobile developer; represented by 10x Management

6. Don’t rest on your laurels — theory matters, but practice matters more

DevBeat logo

High level but hands-on

Our upcoming DevBeat conference, Nov. 12-13 in San Francisco, will have a lot more on this topic. Featuring hacker legends like Stallman, DHH, Rasmus Lerdorf, and Alex Payne, it’s a hands-on developer event packed with:

  • workshops
  • teck talks
  • live Ask-Me-Anything
  • hardware hacking

It’s all aimed at boosting your code skills, security knowledge, hardware hacking, and career development. Register now.

“The best way to improve at building software is to build software. Many ambitious, junior-level engineers spend their free time reading about it: the latest tools, development processes, and the like.

“This is an essential way to spend a fraction of one’s time, but it easily creeps into procrastination territory. Instead, strengthen the part of your brain which builds software by using it as much as possible.”  –James Cropcho, a Ruby on Rails expert and instructor at General Assembly

“Always be hacking. Many great coders I’ve met have multiple ongoing side projects. Doing side projects forces you to explore new technologies and learn all aspects of creating an application. You might need to do front end HTML/CSS, backend API integration, database optimization, a mobile app, and set up your own servers.” – Andrew Waage, CTO and co-founder of Retention Science

7. Peer review is your secret weapon

“Peer programming is very essential. Two programmers working on the same module can vet each other’s code. Also the development team should do weekly code review sessions where every other developer gives feedback on others code and explains how it can be better in a positive way. This actually fosters a culture of collaboration and throws away developer egos!” – Sanjib Sahoo

8. Avoid premature optimization like the plague

“Only refactor when the problem and the solution are both staring you in the face – premature refactoring is a huge waste of time. Don’t invest in perfecting anything that might conceivably be dropped in the next six months. And premature optimization is the root of all evil.” –Seth Purcell

“Don’t optimize early! I see engineers over and over again worrying about scaling for one million users when they don’t even have one thousand.” – Mariya Yao, founder and creative director at Xanadu Mobile; mobile developer and designer

9. You write your code once, but people will read it thousands more times

“You’re writing code that a machine will interpret and run, but other people will have to read your code, understand it, work with it. You have to be cognizant that your code will have a future audience. Code is a form of written communication, too.” – Tracy Chou, software engineer at Pinterest

“It may sound strange, but always be considerate of your future self. Ask yourself: If you had amnesia, would you still understand the code you wrote?” – Wai Ching Jessica Lam, cofounder and CTO at Sugarbox

“Do thorough and separate readings of your documentation. Designs change a lot, and sometimes it’s easy to leave outdated comments in your updated code. By keeping it current, you make it easier for people in the future, and yourself. I can’t tell you how many times I’ve gone back to my own code and thought, ‘What the hell was I doing here?’ Any time I write good comments, I save future me a lot of headaches.” – Kitt Vanderwater, software engineer atGoogle

10. It’s a noble profession. Use your skills for good.

“Helping others is a deep human need. Find a way to use your work towards the betterment of humanity, and you’ll have it made.” – Greg Sadetsky


Editor’s note: Developers! If you’re good and want to be great, our upcoming DevBeat conference, Nov. 12-13 in San Francisco, is a hands-on event packed with master classes, presentations, Q&As, and hackathons, all aimed at boosting your code skills, security knowledge, hardware hacking, and career development. The show starts next Tuesday and seats are limited, so register now.

JFM7VX690T型SRAM型现场可编程门阵列技术手册主要介绍的是上海复旦微电子集团股份有限公司(简称复旦微电子)生产的高性能FPGA产品JFM7VX690T。该产品属于JFM7系列,具有现场可编程特性,集成了功能强大且可以灵活配置组合的可编程资源,适用于实现多种功能,如输入输出接口、通用数字逻辑、存储器、数字信号处理和时钟管理等。JFM7VX690T型FPGA适用于复杂、高速的数字逻辑电路,广泛应用于通讯、信息处理、工业控制、数据中心、仪表测量、医疗仪器、人工智能、自动驾驶等领域。 产品特点包括: 1. 可配置逻辑资源(CLB),使用LUT6结构。 2. 包含CLB模块,可用于实现常规数字逻辑和分布式RAM。 3. 含有I/O、BlockRAM、DSP、MMCM、GTH等可编程模块。 4. 提供不同的封装规格和工作温度范围的产品,便于满足不同的使用环境。 JFM7VX690T产品系列中,有多种型号可供选择。例如: - JFM7VX690T80采用FCBGA1927封装,尺寸为45x45mm,使用锡银焊球,工作温度范围为-40°C到+100°C。 - JFM7VX690T80-AS同样采用FCBGA1927封装,但工作温度范围更广,为-55°C到+125°C,同样使用锡银焊球。 - JFM7VX690T80-N采用FCBGA1927封装和铅锡焊球,工作温度范围与JFM7VX690T80-AS相同。 - JFM7VX690T36的封装规格为FCBGA1761,尺寸为42.5x42.5mm,使用锡银焊球,工作温度范围为-40°C到+100°C。 - JFM7VX690T36-AS使用锡银焊球,工作温度范围为-55°C到+125°C。 - JFM7VX690T36-N使用铅锡焊球,工作温度范围与JFM7VX690T36-AS相同。 技术手册中还包含了一系列详细的技术参数,包括极限参数、推荐工作条件、电特性参数、ESD等级、MSL等级、重量等。在产品参数章节中,还特别强调了封装类型,包括外形图和尺寸、引出端定义等。引出端定义是指对FPGA芯片上的各个引脚的功能和接线规则进行说明,这对于FPGA的正确应用和电路设计至关重要。 应用指南章节涉及了FPGA在不同应用场景下的推荐使用方法。其中差异说明部分可能涉及产品之间的性能差异;关键性能对比可能包括功耗与速度对比、上电浪涌电流测试情况说明、GTH Channel Loss性能差异说明、GTH电源性能差异说明等。此外,手册可能还提供了其他推荐应用方案,例如不使用的BANK接法推荐、CCLK信号PCB布线推荐、JTAG级联PCB布线推荐、系统工作的复位方案推荐等,这些内容对于提高系统性能和稳定性有着重要作用。 焊接及注意事项章节则针对产品的焊接过程提供了指导,强调焊接过程中的注意事项,以确保产品在组装过程中的稳定性和可靠性。手册还明确指出,未经复旦微电子的许可,不得翻印或者复制全部或部分本资料的内容,且不承担采购方选择与使用本文描述的产品和服务的责任。 上海复旦微电子集团股份有限公司拥有相关的商标和知识产权。该公司在中国发布的技术手册,版权为上海复旦微电子集团股份有限公司所有,未经许可不得进行复制或传播。 技术手册提供了上海复旦微电子集团股份有限公司销售及服务网点的信息,方便用户在需要时能够联系到相应的服务机构,获取最新信息和必要的支持。同时,用户可以访问复旦微电子的官方网站(***以获取更多产品信息和公司动态。
标题“100余款高清原厂车标开机logo”所指的是一份资源集合,其中包含了超过100个汽车制造商的高清品牌标志,这些标志是专为开机画面或车载娱乐系统的启动界面设计的。在车载信息娱乐系统中,车标的开机logo通常会在车辆启动时展示,增添品牌形象,提升用户体验。 描述中的信息告诉我们这份资源提供了三种不同的分辨率:1024x600、800x480和222x124。这些尺寸对应了不同车载屏幕的常见分辨率,确保了在各种车型上都能有良好的显示效果。"任你选择"意味着用户可以根据自己的车辆屏幕尺寸选择合适的logo。"还等什么快上车"是一句促销用语,鼓励用户立即下载并使用这些高清车标。 标签“车机logo”明确了这个压缩包的内容是与汽车相关的开机图形标识,主要应用于车载信息系统。 至于文件名称列表中提到的“drawable-hdpi-v4”,这是Android开发中的一个目录名,用于存放不同密度(hdpi:高密度)的图像资源。在Android系统中,为了适应不同屏幕密度的设备,开发者会将图片资源按照ldpi(低密度)、mdpi(中密度)、hdpi、xhdpi、xxhdpi等分类存储。"v4"可能表示这些资源兼容Android 4.0(API级别14)及以上版本的系统,以确保广泛的设备兼容性。 这份压缩包是一个丰富的汽车品牌开机logo库,适合用于各种车载信息娱乐系统,提供了适配不同屏幕尺寸和分辨率的选项,并且遵循了Android应用开发的标准,保证在多数现代Android设备上可以正常显示。对于汽车电子设备开发者、UI设计师或者车友来说,这都是一份极具价值的资源
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值