Search

I was reading this top ten list yesterday, and I thought I can problably come up with my own list of things no-one told me before I started developing software for money. This is my list.

  1. Object orientation is much harder than you think
    Maybe it’s just me, but coming from Computer Science class I thought that OO was easy. I mean, how hard can it be to create classes that mimic the real world? It turns out that it’s pretty hard. Ten years later, I’m still learning how to model properly. I wish I spent more time reading up on OO and design patterns. Good modeling skills are worth a lot to every development team.
  2. The difficult part of software development is communication
    And that’s communication with persons, not socket programming. Now and then you do run into a tricky technical problem, but it’s not at all that common. Much more common is misunderstandings between you and the project manager, between you and the customer and finally between you and the other developers. Work on your soft skills.
  3. Learn to say no
    When I started working, I was very eager to please. This meant that I had a hard time saying no to things people asked of me. I worked a lot of overtime, and still didn’t finish everything that was asked of me. The result was disappointment from their side, and almost burning out on my part. If you never say no, your yes is worth very little. Commit to what you can handle, and if people keep asking you for more, make it very explicit that this would mean not doing something else. What I did was to have a list of stuff that I needed to do on a piece of paper with me. When someone asked for something, I showed them the list and asked what I should bump to have time to help them. This allowed me to say no in a nice way.
  4. If everything is equally important, then nothing is important
    The business likes to say that all the features are as crucial. They are not. Push back and make them commit. It’s easier if you don’t force them to pick what to do and what not to do. Instead, let them choose what you should do this week. This will let you produce the stuff that brings value first. If all else goes haywire, at least you’ve done that.
  5. Don’t over-think a problem
    I can spend whole days designing things in front of the white board. That doesn’t mean it will be any better, it just means it will be more complicated. I don’t mean to say you shouldn’t design at all, just that the implementation will quickly show me stuff I didn’t think of anyway, so why try to make it perfect? Like Dave Farell says: “The devil is in the details, but exorcism is in implementation, not theory.”
  6. Dive really deep into something, but don’t get hung up
    Chris and I spent a lot of time getting into the real deep parts of SQL Server. It was great fun and I learned a lot from it, but after some time I realized that knowing that much didn’t really help me solve the business’ problems. An example: I know that at the table level, SQL Server will not take an IU lock – it will only take a IX lock. This is a performance tweak, since most of the time, the IU lock will have to be escalated into a IX lock anyway. To find this, I spent countless days experimenting, I read loads of material and talked to Microsoft people at conferences. Have I ever had any use of this knowledge. Nope.
  7. Learn about the other parts of the software development machine
    It’s really important to be a great developer. But to be a great part of the system that produces software, you need to understand what the rest of the system does. How do the QA people work? What does the project manager do? What drives the business analyst? This knowledge will help you connect with the rest of the people, and will grease interactions with them. Ask the people around you for help in learning more. What books are good? Most people will be flattered that you care, and willingly help you out. A little time on this goes a really long way.
  8. Your colleagues are your best teachers
    A year after I started on my first job, we merged with another company. Suddenly I had a lot of much more talented and experienced people around me. I remember distinctly how this made me feel inferior and stupid. I studied hard, reading book after book but I still didn’t catch up. They had too much of an advantage on me, I figured.
    Nowadays, working with great people doesn’t make me feel bad at all. I just feel I have the chance of a lifetime to learn. I ask questions and I try really hard to understand how my colleagues come to the conclusions they do. This is why I joined ThoughtWorks. See your peers as an asset, not competition.
  9. It all comes down to working software
    No matter how cool your algorithms are, no matter how brilliant your database schema is, no matter how fabulous your whatever is, if it doesn’t scratch the clients’ itch, it’s not worth anything. Focus on delivering working software, and at the same time prepare to continue delivering software using that code base and you’re on the right path.
  10. Some people are assholes
    Most of the time, most of the people around you are great. You learn from them, and they learn from you. Accomplishing something together is a good feeling. Unfortunately, you will probably run into the exceptions. People that because of something or other are plain old mean. Demeaning bosses. Lying colleagues. Stupid, ignorant customers. Don’t take this too hard. Try to work around them and do what you can to minimize the pain and effort they cause, but don’t blame yourself. As long as you stay honest and do your best, you’ve done your part.

133 Responses to “Top ten things ten years of professional software development has taught me”

    Very nice list, and #4 is nicely put.

    I really liked your idea of writing down your Todo list and showing it to people in #3. Thanks!

    I have to say that #9 is my favorite. If we write something beautiful that doesn’t do what it’s supposed to then what’s the point?

    I’d recommend reading “Extreme Programming Installed” by Ron Jeffries, et al.

    [Andres: Thank you for the tip. That was actually the very first agile book I ever read. Well worth reading.]

    [...] has a nice list of things that software development has taught him. Quite nicely put, especially points 2 and 4. 2. The difficult part of software development is [...]

    [...] inspired by The Top 10 Things They Never Taught Me in Design School to write his own piece titled Top ten things ten years of professional software development has taught me. Here’s his list — all of which I consider sound advice — with some excerpts of [...]

    As someone with over 20 years of experience both programming and managing programmers, this is a list that should be read every day. I was going to pick a few out, but I find I can’t rank any above the others.

    Very good advice.

    I wish I could relate with #8, but unfortunately, most of the time, there is nothing to be impressed about… And yes, we have merged already. The rest is pretty much spot on though.

    Each one of these itself a lesson that need to be grabbed. Very nicely put in and it does help others immencly without spending those many years at work.

    hear hear!

    Neil’s comment (comment #7) cracks me up, due to item #4. Neil says “I was going to pick a few out, but I find I can’t rank any above the others.” Item #4 says “If everything is equally important, then nothing is important.”

    Obviously in reality it’s not the same, but it’s funny enough for a larf.

    OO is only hard when you use it. But it is very easy not to use it, and you gain better programs, too! Simply choose the right language…

    See your peers as an asset, not competition.

    That’s a beautiful sentiment. Another reason “pay for performance” or “rank on the curve” shops put out all the wrong incentives.

    Great list!

    #3 If you have a project manager they should be the one saying no not you.

    Not that I’m condoning blind faith in project managers but they really should be the one to act as a gate keeper for new features or major modifications. If your manager does ask you to add something to your work list he/she should be taking something off.

    Learn to say no

    This is a great tip, I have been a victim of this when I first started my job. I never thought of carrying a peice of paper with a list of current projects with me but I will now.

    hi, nice post, I’d be happy if you share your experience on any topic . thanks..

    One of the reasons I took my current job is that I was very impressed with the people with whom I interviewed. I thought I’d be able to learn quite a bit (and I have). And I’ve been in the field for closer to 15 years, FWIW.

    Stan (#17) hits on an important point.

    Business in general (not just the programming shops) all like to blather about TEAMWORK but not a one of them has any clue about how to get people to perform as a TEAM. Since most of the HR weenies will install some supposedly “objective” ranking system where you have to measure your performance against a list of things you have to do, people will do whatever it takes to get those things done regardless of their impact on the rest of the people around them. They will do what they can and blame others for what they don’t finish. Nobody gets measured on what they do to help make their team members stronger. Nobody gets jack for what they do that isn’t on their objectives that meant that the organization as a whole succeeded.

    People have to see clearly how behaving as a team will benefit their bottom lines. Why else would you do it? But it is the fact that most if not all review systems don’t account for team-oriented behaviors…

    Great list. I think that #5 is really true in a lot more industries than just software. But so hard to convince people of it….

    [...] Andres Taylor via Jeremy Miller: Maybe it’s just me, but coming from Computer Science class I thought that OO was easy. I mean, how hard can it be to create classes that mimic the real world? It turns out that it’s pretty hard. Ten years later, I’m still learning how to model properly. I wish I spent more time reading up on OO and design patterns. Good modeling skills are worth a lot to every development team. [...]

    Guillaume (comment #8) says:
    “I wish I could relate with #8, but unfortunately, most of the time, there is nothing to be impressed about… ”

    If you can find nobody to learn from at your present job, then either:
    – You aren’t looking very hard.
    or
    – You don’t really want to enrich yourself professionally.
    or
    – You have an inflated view of your capabilities.
    or
    – If your workplace really is full of driftwood, you should seek a new job working with people who are smarter, more experienced, and can offer a challenging environment.

    I have been quite fortunate, working with many very smart and very experienced people in my 25 years of professional software development. Even after decades in the business, I still find people who can help me develop my craft.

    Open your eyes, find someone who does something well – even if it is a small thing – and learn from it. Find someone whose character and skills you respect and ask them to be your mentor. Make it an explicit goal to help you develop your professional skills. Once you have 5-10 years of experience, act as a mentor to others – but still seek out a good mentor for yourself.

    Top 6 List of Programming Top 10 Lists…

    Presented, in no particular order, for your reading pleasure: my top 6 list of programming top 10 lists. To keep this entry concise, I’ve only quoted a brief summary of each item. If any of these sound interesting to……

    “10. Most of the time, most of the people around you are great”

    Wow, i think that is about the most wrong thing i have ever read on the internet. If you believe that, there is something wrong w/ you.

    [Andres: I do believe that. And I find that I learn the most when I interact with people that I don't easily get along with, or that I don't agree with. So you must have lots to teach me! :) ]

    [...] nós demoramos a aprender algumas coisas, mas o Andres está coberto de razão em sua lista das 10 coisas mais importantes que 10 anos de desenvolvimento de software o [...]

    I’m now reconsidering the webdeveloppement as a carreer.

    Thanks!

    great tips to be in charge of your programming career

    A realy great article Andres. It was a pleasure to read.

    “I studied hard, reading book after book but I still didn’t catch up. They had too much of an advantage on me, I figured….I ask questions and I try really hard to understand how my colleagues come to the conclusions they do.”

    The efforts you touched on above remind me of how difficult being a developer was for me. Maybe #11 could be:
    Keep Learning
    You have chosen Software Development as your career; your craft. As with any craft, you will never been done learning. The technologies and techniques will never stop evolving. They are, after all, springing from the minds of your fellow craftspeople. If you can’t invest the time and energy necessary to keep up to your peers, chose another specialty.

    i’ve been doing this for 10+ years, too, and have learned most of the things here the hard way.

    one that you left off, although i suppose it is there by implication:

    KEEP IT SIMPLE.

    the path to disaster is paved with complexity. if you are able to manage the expectations of the client/business, you can deliver them a working product, on time, and on budget. if you do two things you warn against (overthink and fail to say no when you should), you will doom the project.

    every successful project i’ve ever worked on has had “keep it simple” as a mantra. every failed project was needlessly complex in a futile attempt to satisfy the client. the simple ones end up being satisfactory, because they actually get finished. need proof? see the 37 Signals apps and read their book. they are completely right.

    Top 10 óðîêîâ äëÿ ðàçðàáîò÷èêà…

    Âäîãîíêó ïðåäûäóùåìó ïîñòó – âîò åùå îäèí íóìåðîâàííûé ñïèñîê è, âåðîÿòíî, ðåáÿòà ñêîðåå âûáåðóò åãî – “Òîï 10 âåùåé, êîòîðûì ìåíÿ íàó÷èëè 10 …

    This will be seen as a troll, but it’s not.

    For an easy life, abandon Microsoft, abandon Java. Both have too much complexity, too much bloat, too many inconsistencies, too many bugs, too many bolt-ons to get something to work, too much nightmare. Program in PHP (or Ruby, or Python, or RoR, or C or something). I genuinely suggest this to make your life easier and less stressful. Forget how much that MCSE cost you (the one 20 billion other people have), or the years invested in MS or Java (or COBOL or whatever) – they will still stand you in good stead for getting your head round things.

    Seriously think about the tools you are using for your job, and explore options for other languages and tools. Don’t be dogmatic, or a fanboy, or closed minded. See what else is out there. It really doesn’t hurt sometimes and could revolutionise your working life.

    [...] My daily readings 03/24/2007 Andres’ thoughts » Top ten things ten years of professional software development has taught me [...]

    [...] from their experiences. With this thought in mind, I was pleased to discover a very compelling “top ten things I’ve learned” list from developer/blogger Andres Taylor. What Andres writes in his post inspired me to put together my [...]

    [...] Top Ten Things Ten Years of Professional Software Development Has Taught Me – spot on [...]

    [...] Top Ten Things Ten Years of Professional Software Development Has Taught Me – spot on [...]

    [...] of them for sure. I haven’t got as much experience as Andre, but I can already glimpse many of this stuff during my daily [...]

    great!!

    will help me lot…

    Excellent advice.

    [...] a fantastic article – “Top ten things ten years of professional software development has taught me“.  Read it.  And you should also check out his inspiration … “Michael [...]

    [...] shares with us some lessons learned in the software development world that only come with age.  After ten years of development, he’s got some great little nuggets [...]

    10 cosas que he aprendido como desarrollador…

    1-La orientación a objetos es mucho más difícil de lo que piensas. 2-La parte difícil del desarrollo de software es la comunicación. 3-Aprende a decir no. 4-Si todo es igualmente importante, entonces nada lo es.5-No pienses en exceso un problema. …

    can somebody trnslate this text to spanish? I think that it´s very ineresting but my english isn´t well enough and I don´t understand it completly

    Very succinctly delivered. All very unfortunate, but all very true.

    [...] Top ten things ten years of professional software development has taught me [...]

    [...] make it possible. Andrés Taylor’s 10 lessons every software developer should know: No matter how cool your algorithms are, no matter how [...]

    [...] Andres’ thoughts » Top ten things ten years of professional software development has taught me (tags: development programming lifehacks inspiration) [...]

    Egoless programming…

    [...] read Andres Taylor’s comments with this Top Ten, see his blog here [...]

    [...] Andres’ thoughts ? Top ten things ten years of professional software development has taught me Tagged as: development blog interesting software [...]

    Ten Things You Should Know As A Developer…

    Andres Taylor gives us his top ten things he’s learned about software development. The list is insightful…

    The ten things ten years of professional software development has taught me…

    Andrés Taylor has written an insightful list of the ” Top ten things ten years of professional software…

    [...] Top 10 Things Ten Years of Professional Software Development Has Taught Me [...]

    Nice list….

    [...] Andres Taylor drops some serious science with “Top ten things ten years of professional software development has taught me.” There are some real gems on this list, and if you’re a developer it’s a must [...]

    Amazing List, specially I have some experience with No.3 over the past year.

    Good Stuff!

    [...] things you should know as a developer I just found this wonderful link in Scoble’s Google Reader shared items. A wonderful piece of writing about the software [...]

    [...]Andrés Taylor has created a top ten list of very succinct maxims for software development:

    Top ten things ten years of professional software development has taught me

    I particularly like #2, 3, 8 and 10; especially #10 (can you tell it has started off to be a bad day?)[...]

    [...] 26/03/07 Via Javahispano me he encontrado con un interesantisímo post con una lista de cosas aprendidas por un desarrollador en sus 10 años de experiencia [...]

    [...] 10 things about software development that had to be learned on the job:http://www.taylor.se/blog/2007/03/22/top-ten-things-ten-years-of-professional-software-development-h… [...]

    Top Ten Things Learned as a Professional Developer…

    Andres Taylor at Andre’s Thoughts has put together a good “Top Ten” list of things he has learned as a developer that resounded in my chest when I read them. They are so true. Here is the abbreviated list (with my comments):

    Obj…

    Sometimes you may get a different kind of lesson from those around you. I led a Web development team at Lennox for two years. About a year after I moved on, about half the team was doing other things. Like Marketing! If that had happened while I was still there, I would get a very different message from my coworkers. I’m just saying that some peer learning may not be all about the software!

    [...] Ten things in software development. [...]

    Really nice article..i m just a year old in software development..but i think i got the article at right time..but i find ur 1st n 5th point contradicting..
    i think after reading this article i will b more prepared to take up chalenges..
    thanks..

    Fantastic article. It clearly portrays the facts going around the software world. Keep up the good work author :)

    The #1 and #9 is realy true, these two points is sufficient for success in software. It is the nice article, i thought #1 always while doing desinging. It is very useful article..

    Have you read Getting Real? http://gettingreal.37signals.com/toc.php

    All points good. Especially #1, #3, #8 and #9 are very nice.

    [...] Andrés, un desarrollador con diez años de experiencia a sus espaldas, ha escrito en su blog lo que esos diez años le han enseñado. [...]

    Awesome article..very nicely written..as I was going point by point …..seems like its jotting down what I have faced so far and seems so true especially #3 :)

    #3 and #4 are the best points which i have realized so early in my 1 year software development experience.
    last one also gud.

    Really nice listing. I like point#3 very useful.

    Design and Communication Considered Biggest Software Challenges…

    I just stumbled across this great top ten software lessons learned list. I was happy to see the first……

    [...] While surfing round the smart edges of the web, I halted on to the Andre’s article on “Top Ten Things Ten Years Of Software Development Taught Me“. Andre have neatly explained the things we need to do and not to do, while developing [...]

    Nice list. I can relate to every item and wished I had this when I was beginning my career.

    On #3 though, some companies are shifting more toward ‘self-service’ management. Where the project manager is not helping to balance your load, the expectation from management is that YOU balance your load. Which is what you had to do.

    However, I had an experience where I asked a Manager where I should take time away from to accommodate his request. His smug reply was that a professional developer should know how to prioritize. I guess that goes to #10 that you mentioned.

    [...] Top 10 things learned in 10 years of professional software development [...]

    [...] Top 10 things learned in 10 years of professional software development [...]

    select top 6 from (select top 10 from lists)…

    ha! i got ya! you thought this was a sql post, but it’s not =P jeff atwood of codinghorror.com fame has…

    Dude, You learnt all this in 10 years???? :S. T think its a bit late but your are right on the mark.

    I wish this list could be added to the course-curriculum of Colleges and Universities for studies in IT filed like Graduation and Post-Graduation (life of a IT porfessional is the same may it be any part of the world)…So y not leave a message to upcoming freshers in this field so that they dont end up in a situation as ours…

    By the way it is a nice post…Try working in Bangalore (INDIA) you will learn all these ten things (and many more) in just 10 months (or may be less time if you work in companies like ACCENTURE,INFY …… list continues)…

    Regards
    Sam

    Thats the perfect 10 list… I have started realising the things mentioned in the list are actually true lot of times. good effort to list down your experience and share it to all..

    They should teach this in EVERY SINGLE LAST UNIVERSITY Computer Science curriculum on the PLANET !

    In 20 years in the “business”, I have come across at one time or another, EVERY single last tidbit you mentioned in one way or another. Being back at the U now pursuing a Masters ( maybe, haven’t decided ), I can tell you, most kids ( yes, I’m old, get over it ) coming out from school today aren’t being shown any of these things. Rather, they’re being prepared by seeing how much of a theorem or algorithm they can regurgitate despite not being truly aware of
    how/what the “Process” of Engineering Software done/is about.

    Kudos…

    You forgot; To be good demands more than everything!
    Basically if you want to stay on top of your skills you need to invest 24 hours every day doing SW or reading books…!! ;)

    I’ve been at this for almost 30 years now and wish I had realized some of these things sooner. It’s much more about people than technology.

    I would add to number eight after ten or more years, be one of those people that less experienced programmers want to come to. It’s great for your career and helps keep you sharp. Sometimes you gain new insight or even learn something new while helping someone less experienced.

    Oh and one more! As Einstien noted “Things should be made as simple as possible but no simpler.” Or, the old NASA KISS principle (Keep It Simple Stupid). My own observation is if something looks too complicated, it is – find a better way.

    [...] este blog, Andrés, un desarrollador con más de diez años de experiencia, ha recopilado las diez cosas [...]

    Nice lessons.

    Awesome list, specially 3,4 and 5 are really outcome of lot of effort and I firmly follow them. If I were to compose such a list, most of my points would be the same.

    Regards,

    Thanks

    I luv 3,8 and 10

    Cheers mate!!!
    All in the game :-)

    Great work.
    Really needs to follow for better work from our side.

    [...] Top ten things ten years of professional software development has taught me [...]

    Amazing advice! I love this quote:
    ‘See your peers as an asset, not competition.’

    [...] Top Ten Things They Never Taught Me in Design School led to Andrés Taylor’s top ten things ten years of professional software development has taught me, which led me to Coding Horror’s Top 6 List of Programming Top 10 Lists, which inspired me to [...]

    Must Say ………FANTASTIC TIPS to Survive in Software Industry…Its really difficult for me to say which one is best…..

    Pls keep me posted for such interesting topics.

    [...] 5. Top 10 things Ten Years of Professional Software Development Has Taught Me [...]

    Nice points. Add to it “experience is the best teacher” There is nothing like a hands on approach.

    These must be one of the finest set of observations about software development. Many of them hold true not only for a software developer but for a software tester as well.

    You have wonderfully summarized the importance of good communication and setting priorities. You have very well suggested about learning from peers and performing even if the people around you are not the way as you expected them to be.

    It was enjoyable reading. I look forward to reading further good articles from you.

    #8 Is advice that appies to more than software. Unfortunately its a lesson that is usually learned through life experience.

    i really appreciate the points which r real truths. But i want to discuss one point more. pls tell how the team member should manage the whole project if his/her project manager/leader, TL dont have s/w devpt experience. in this case it’s v difficult to model the problem (OOAD). also it’s difficult to have discussion with the higher ups bcoz they cant realise the prob. and team member just pick the req & start coding – s/w quality suffers.

    [...] Top ten things ten years of professional software development has taught me [...]

    Quite honest and nice!

    #1 is really part of systems design in disguise, OOD is only the code side, systems are much more than just OO, coding and live use often look a lot different and messier than some idealistic OOD.

    #5 maybe true in some cases, however I recently had to
    provide a quote, with less research than I’d have liked, and discovered that I had to do a much more system design than I expected. I had to design a new multi-factor configuration file, which was easy for the users to maintain, had robust validation rules, had reliable lookup structures and provided all the necessary hooks for current and later scheduled changes, without breaking the current system.

    Designing reliable and maintainable systems is a lot harder than many people realize, often harder than some abstract and idealistic OOD.

    Even the arab programmers like your article Mr.Taylor and I’m one of them :)

    [...] I found one very interesting article about software development: http://www.taylor.se/blog/2007/03/22/top-ten-things-ten-years-of-professional-software-development-h... [...]

    You might want to read
    The Pragmatic Programmer: From Journeyman to Master
    by Andrew Hunt (Author), David Thomas (Author)
    It comes from people that have been there.

    #3: I will try to do the same thing. Thanks for pointing out this issue.

    #4: Now, I can understand better the importance of issues.

    Please keep doing research.

    Regards,

    M. A. Shah

    i really liked the list.Specially #2,which is usually ignored and lack on developers’ end,it needs to be worked on.#3 is a very nice idea to say ‘No’,in order to accomplish the priority tasks.

    Top ten tips for young software developers…

    A guy named Andrés Taylor, whose being working as a professional software developer for 10 years, put together a list of top ten things people should be aware of before programming for money. Based on my experience, I can agree to most of his points. …

    Very good list. Keep the good work going

    [...] surfing round the smart edges of the web, I halted on to the Andre’s article on “Top Ten Things Ten Years Of Software Development Taught Me“. Andre have neatly explained the things we need to do and not to do, while developing [...]

    [...] Top Ten Lessons of Professional Software Development Here is a very good list by Anders Taylor of his top ten lessons: http://www.taylor.se/blog/2007/03/22/top-ten-things-ten-years-of-professional-software-development-h... [...]

    [...] Taylor recently wrote an excellent article about 10 things he learned from being a professional software developer. He list was inspired by Michael Bierut’s list of things he wasn’t taught in design school. [...]

    [...] Top ten things ten years of professional software development has taught me The title says it all. [...]

    [...] it is nice to just have an aid, a simple helping function, instead of a core … More…Top ten things ten years of professional software development has taught meThings no-one told me before I started developing software for money. More… Tutorial: [...]

    Great list but #10 should really be #1.

    [...] Andres Taylor: Top 10 Things Ten Years of Professional Software Development Has Taught Me [...]

    [...] Top ten things ten years of professional software development has taught me Posted April 20, 2007 http://www.taylor.se/blog/2007/03/22/top-ten-things-ten-years-of-professional-software-development-h... [...]

    I agree, object oriented methodology is hard and sometimes overly complex. Sometimes its easier to just do your work in a non-oo fashion.

    I agree. Our colleagues are our best teachers. During the course of time we knowingly or unknowingly learn many things from our colleagues. Also # 10 impressed me a lot. We need to understand greatness of people around us.

    [...] Top ten things ten years of software development has taught me [...]

    [...] Top ten things ten years of software development has taught me [...]

    [...] April 30th, 2007 · No Comments Tag: ProgrammingRob Elkins over at Rise and Shout points to a great post by Andrés Taylor titled “Top ten things ten years of professional software development has taught me”. [...]

    プログラミングの6大10項目リスト…

    プログラミングの6大10項目リスト ジェラルド・ワインバーグの「エゴレスプログラ……

    プログラミングの6大10項目リスト…

    プログラミングの6大10項目リスト ジェラルド・ワインバーグの「エゴレスプログラ……

    Свадебный салон ?Этуаль? находится на рынке свадебных услуг с 1996 года. 服装ERPСалон обладает постоянно обновляющимся огромным ассортиментов свадебных платьев. Наличие свадебных платьев разных ценовых категорий, постоянное отслеживание последних тенденций в свадебной моде и уникальность каждого 服装ERPотдельного платья обеспечивают не изменяющуюся с годами популярность данной фирмы.

    ソフトウェアの開発は、 企業全体のシステム再構築と考えています。
    単なるソフトウエアでなく、ダイナミックに変化する環境の中で生きて使われ? 企業システムをより確かなものにしていくことをめざしています。新潟オープンソース協会が設立されて約3年、まだ新潟にオープンソースは定着せず、私自身も自社のことで手一杯で新潟オープンソース協会に協力的とはいえないが、オープンソースのイベントでもっと熱気を感じ取れるようにがんばって行かなくては。

    ソフトウエアは、それが単に動作服装ERPすればいいというのではなく? お使いいただいているお客様の役に立っているかどうかが最も重要なことです。
    コンサルティングを行い構築設計したソフトウエアであっても、服装ERP期待した結果を生み出すとは限りません。ソフトウエアも?使い方?使う人によって生きてくるものです。

    [...] Andres’ thoughts: Top ten things ten years of professional software development has taught me [...]

    Number 3 really speaks to me. I have adopted the same method of saying no – creating a job list and it definitely gets results! Good post!

    Excellent post! Can certainly agree with number 10!

    Bravo!

    Excellent post

    “When I started working, I was very eager to please. This meant that I had a hard time saying no to things people asked of me. I worked a lot of overtime, and still didn’t finish everything that was asked of me. The result was disappointment from their side, and almost burning out on my part.”

    Sharing experience Andrés Taylor the “Top ten things ten years of professional software development its a great learning experience Thanks

    Great post. Number; 3,4 and 5 are completely true!

    Very well put true!

    広範囲をの構造作動させるWindowsで使用されるホテルの管理システムC/Sはより多くの顧客ホテルの管理システム、機能モジュール、ケイタリング、酒店管理软件人員、賃金、出席、調達、目録およびホテルの受信を含む財政システムのリアルタイム制御私達の経験を共有するためにプログラムを達成でき、達成、特に、私達はユーザーにネットワークホテルを含む自由な試験を、酒店系统ダウンロードするために版を提供し、レストランの見通しは小-中型のホテルの顧客に、適用する。