iAn`s WEB BLOG

As for this chapter, The Organization, the first topic is about unity, this factor is one of the most important thing to help / survive the whole organization / company on its path. Most organizations have diffuculties in having their full untiy, for the team, its an important factor, because if you have unity, you get your team trust and everything, all will flow on your way, everything will be fine and everything will be on time. There’s nothing to worry about if you get to be as ONE, because your not working alone here, your a team! that’s why, there’s this word “UNITY” in which it emphasize the bond! the strenght! the closeness.

For the second chapter, the Alone Time, this factor can be very effective for people who maybe they prefer to work alone just by their selves only, to some extent its good, because working alone can make you be in focus always, you can visualize your own concepts, BUT! there’s a counter part on this, working alone can be too boring at times, eventhough you can focus more, still there are some factors that might affect you to work, like, turning to dizziness, getting bored, go crazy! and etc. this are some crucial factors, it can almost affect your productivity. On this topic, the chapter emphasize that its not 24hrs. that were working with our team, officemates, colleages, etc. if that’s the case, we should be more productive and efficient eventhough we work alone after the hours that we spent working with our team, because working alone can make you also more comportable, because your now working on your own way, your rules and your style, there’s no limitations as long as you do it on time, there’s nothing to be worried about.

For the third chapter, Avoid Meetings, this factor is also an important thing to be avoided, too much meetings with no exact agenda! this can be too crucial on your part, because the time you spent to that meeting and there’s nothing too important to talk about is a mess! because there are so many ways on how you can create a meeting without even wasting too much time looking for the rigth venue and so on, you can do e-mails, chatting, etc. this are some effective ways for you to be comportable with even its a meeting to start with. Meetings should not be too long, its should be limited maybe for about 30mins. only, in this sense, you can do more things without wasting any time.

Lastly, Celebrate some small things, for an organizations, team, they do this as a part of giving insentives to their employees, for example, their been given a big project and their almost half on it, they try to celebrate what’s done. Its very effective because in here, this is the time to talk with what you guys doing, gets to relax eventhough topic is all about the project, its natural for some professionals, because they are more focus on it. Eventhough you all work too hard, always remember that you need time to set yourself relax to be more focus and productive at all times.

For this chapter, Process, its all about how you manage things on your work,how you prepare your needed resources, how you get your clients needs and wants, how you understand the details and etc.. At first, if your going to build something or a system, make sure that it can run fast and complex, as an experience, most people gets to demand a much faster system that can accommodate the time they have for their works, because nowadays, people especially the professionals whose always on call and really value the time, they are more demanding due to the fact that more resources are beneath in our environment.

Do less, skip details, do shortcuts and etc.. this factor is a very effective tool, IF and ONLY IF, you can make it ran faster than everybody expect. Its good if your that type of developer, that even using shortcuts or anything that can make your work simple, they can still met the fast run action of their system. Its true that if you do less, of course, it lessen everything, it lessen stress on your part as a developer, less the works and revising actions, and lastly, less argument with your co-workers / team, if your not alone to the project. As an open-eye everything that you make should be more real, true, no jokes, all professional works. As everybody expects, if your creating something, expect that at the first time you run it, 80% of the program or the system will exactly shows errors, and because it happens, its normal, because errors are the guides for them to be debug. As time goes by, if you see improvement?, let it evolve, morph! and something good will return. For some developers, they don’t even take part for perfection, and because they don’t after for it, then its really much easier to develop, its like free loaders who always want to just go to the flow, no directions.

There are so many tools or things that you can do to start up what’s first to do, as an example, you first do the natural thing, do brainstorming! its very effective because you collaborate your ideas, you gain insights, bond with your workers / team, share knowledge and thoughts. Next is, you make sketches, you do drafts, because at least, if you make this, you can share it to your team and start to argue on your designs which is very effective because they could get a hint on what the plan should stick into. Next is you make HTML designs, do UI stuff, it deals with things that can modify your solutions. Lastly, the bloodiest part, “for some” the CODING! @_@, for some professions, who hate code but love to analyze things or bugs errors, they are the one with the anti effect.

For your own benefit and for your customers sake, at first, if they give details on you, try to advance yourself, make some little decisions on the details so that when you and your client gets to reside about how things will go, they can visualize what you think is better for the system / project. For choosing which is which to do, let your customer to be the one to get a decision, then if you think there’s something bad you saw if its the thing that should be followed, then, just do a second demotion, don’t be bias to them, just comment on it. When its all done?, now is the time to shine, do the implementation and let the world knows what’s new to the society, then now is the time to get comments on the people who uses it and that is the time to do revising action, and upgrades, until it gets to be good. Last action, after you implement it, do the breakdown, of the whole projects, how long it takes, the cost, and etc. its just a documentation for the whole project for you to have basis, on which part you take too long actions, etc.

As to start this chapter, Feature Selection, this first indicates that, in building a project, we should first do the half of it, don’t just build and build, as the chapter says “we want a HALF product, not a HALF-ASS” it only signifies that, its better to come up first with half of what you develop, you take chances, and do it all over again, not the usual thing for some developers, they just want to build and build with no direction at all, your just wasting so many time and effort, its like shooting a fly using a gun. Always collaborate for ideas, don’t just stick on the resource on hand, be creative, be an explorer and etc. its always best to get some resources on wider informations, because you could still develop what is half made.

Do what ever you visualize, what you want to see after you made things in a BOOM!. As an open-eye, if your doing something, always make a track on what you’ve done, because if you track it, you can easily know which part you should focus on or you can discard, after you do it, now is the time to make the solid foundation of what your doing, what you start. As everybody says “focus on the real thing” this saying are normal and in fact, effective, because focusing on the real thing can make your work more faster than ever, you wont waste anytime because you have the track, the direction, don’t waste time on junk things, be practical, be direct, always focus on what really matter most, not on what doesn’t matter, time is gold, every wasted time has its own destination.

To some extent, and to some professionals comment, its better to build a new program than to adapt something and upgrading it, because  the difference between the two is that, in a adapted system, your going to study what they build and get yourself crazy in understanding what they do the system, rather than a newly build system, which is the YOU who made it, discover, develop, etc. although having a start is more complicated, but its good to know that if you build and launched a system which is your the one who made it, its more intense to the feeling that you’ve develop something that everybody can use it.

If to some extent, your clients gets to demand more, about the feature and stuff, for the book, its much better for them to say NO at the first place or NOT YET before you do the YES, because as a developer, you first want to build your own vision for the system so that you can apply what you learn, rather than just agreeing on their wants and demand, its not the feeling of being rude or to hurt or to counter their thoughts, its just, you have your own standard in doing things, your a professional, then your customer should be the one to agree on you, although their thoughts can be helpful, maybe on the last part.

Build products, do services are examples that can help you mark and create your name in the industry, but wait!, its not the bottomline! what’s really the point is that, how you keep promises to your customers / clients, its always the more important factor for you to be more competitive to any other. In terms of problem phase, don’t ignore problems, always fixed it, because if you just ignore them, at times your finally having your rest because your almost done with the system, then the PROBLEMS you ignore at the first place will be the one that gets your mind blowout and turns you crazy!

Giving suggestion is not bad, in fact its good, but always bear in mind that suggestions are just suggestions, they are guidelines for some, don’t just agree, collect suggestions then when time comes your getting out of vision, that’s the time to put suggestions on your part, to help you, to remind you things that are important.

First and foremost, as I read through this chapter, I’ve read that, before you start something or doing something, you should know first or answer first these questions: What is your application / project for? Why are you creating it? What is the purpose of your product? Will it scale in the next 5 years? Your vision. Its existence. The details. Etc. this are some of the questions you need to answer to set up all the things you need.

Knowing what your application for is, for you to know what should you focus on, if its environmental use only, for kids, teens, business, etc. of course if you know what it is for, you can easily direct yourself on the right track and go through it. Why do you need to create this? Of course knowing the existence of what you’re doing is important, if it’s because, your boss told you to do it? Does it help make something grow, is it safe?, thinks also more deeper, thus your product or project will scale in the next following years if you have been launch it already in the market and let somebody uses it? Things like that, you should think BIG! Visualize the big feature. Vision should follow after you figure out everything you need; every company organization has their own vision and mission, its very important because it helps you in making your decisions, but everything must be concise, clear, direct to the point and etc. if everything goes straight, now is the time to make an outline, you should start from the beginning, don’t think first its end, just visualize it and everything will follow. Know the details of your project, understanding it and doing what’s written to it can do things much faster because, you have something to follow, but in case there’s a thing you want to revise, do it as soon as possible for you not to missed something, because for some professionals, they just do the revising at the end, but for some, that’s the thing that can make out of a problem, forgetting it or being focus on something else, work smart! Do things that can make your life easier. Flexibility of your product should be in mind as possible, because for some users, they don’t care how good this product looks like, for some they’re after for the functionalities, is it flexible anywhere? Good connections? Is it user friendly? Stuffs like that. As of some professionals experience, they say that, don’t waste your time on the problems that is not there yet, focus on what is out there, what is present, always have your backup! It’s safer to think in advance for you to mind solutions fast, than it’s too late. Lastly, know your customer, your target, your focus, because if you know who your customers really are, it is easily to think where you can start it as soon as it’s been launch already.

Less Mass is very important for doing things, it helps you to do thing compress, simple but quality is there, being practical is just one form of how you can organize things, doing change direction quickly, focus on good ideas and integrate things. Lowering cost is a good factor, because if you can build something, doing changes by having a low cost on your part, then it’s really good news for everybody or in your team. Doing thing simple and keeping it small is also good, as long as you can make spirit and quality out of it. There is this topic to do the Magic 3, it only indicates to first have at lease 3 members on your team, a designer, developer and a sweeper, the advantage Is that the more lessen you are, the more easier to motivates a team or the more clearer a communication can be, but then, the disadvantage of this is that, if you don’t have the perfect team on your hand, the bad chances you can have in building a good harmony. Knowing your constraints/limitations should also be prioritized for you to know what decision you can make if something bad happen or whatever worst thing may pop out in the middle of the work, don’t be freak out, used them as a guide. Meeting the deadline and knowing your clients need is really a must, most importantly for some companies who are just starting to make a name in the industry. It’s very important to steak with the client’s deadline for them to know what your company can do, and if that factor is in you, it’s a good start.

First of all, Getting Real is about facing the reality of the real world; it tackles so many topics that may help every programmer, developers, designers, company and etc. to make their works more competitive than others. Getting Real is also a web based practice, it talks about how you will lessen your resources but at the same time it fits the quality and the requirements needed. It also creates a distinction between other types of based, where in it comply to be much advantageous if a web based is done, because as Getting Real says and other professionals experience, a web based is more competitive, first of all it is been updated into a day to day basis, second is its an open source, where in everybody can react on, although at times, for someone whose not familiar or just getting started to use a web based, they found it more harder. Getting Real also wants as to realize that being concise or direct to the point is more advantageous than doing thing in a very hard manner, because Getting Real wants us to know what the difference between working harder and working smarter, because for some users or developers, they do it on the way they want to it to happen but still they know their limitations and what their clients really needed them to do.

Build Less is also one of the good practices for every developer, designers and etc. because building less but the quality is still there, the better, because not all programmers are very industrious in making things, they just sometimes doing the trial and error for them to come up with an idea or for them to know what is better for the program their working. It also tackles how can you be one step ahead with your competitors, if you know that your competitors do much than you do, then doing less is much advantageous, less people, less options, less features and etc. the better it creates than your competitors. Knowing your competitor is really a good start for you to know where you should start and where your track should be. For some professionals experience, they encounter shortage of money or budget for the work, but then, even they face obstacles like that, they are still require to do their best whatever cash is on hand, because, they cannot just trash whatever they started into because of some shortage, for some factors, it’s a trial on how good they are in terms of making good decision. Managing your staff is really a good investment, on how you motivate them can create a more good harmony for them to: first, work smarter/harder, second, to do what they can, third, give their time and dedication for the project and lastly, on how they can give a good output out of whatever is on hand.

This is my first time to discover this site, and its a very interesting, .hehe. .i would like to learn more in this course, because i know, there`s a lot more out there. .

Hi guys! just want to pop up my newly build store! its already been launch and named ™-DM`s SpicE-™ its more of clothing and apparel!. .its COOL and VERY AFFORDABLE, go visit my site now, at http://adrian17zero.myshopify.com