Growth Stages of a Programmer:

Whether you learn to program in school or at home, you’ll go through these 5 stages.

  1. The Hand-holding Honeymoon – text books and online courses will make you feel invincible while they hold your hand throughout the process of programming a cool app.
  2. The Cliff of Confusion – but once you face the proverbial “blank page” you’ll find you have no idea how to go about actually program anything.
  3. The Desert of Despair – you desperately jump from one online course or text book to the next. They are all either too basic or too advanced. But you continue your search – anything to avoid facing the “blank page”.
  4. The Upswing of Awesome – after building some basic apps you finally start to regain the confidence you got from early tutorials.
  5. Job Ready – you’re finally confident enough to go out and start applying for jobs. You have a portfolio of apps to get your foot in the door, and have coded enough to pass coding interviews.

Sooner or later, no one will be there to hold your hand. That’s when the true learning begins.

Source: Quora

Advertisements

How can I get a job at Facebook or Google?

featured

If you have ever wondered about landing a job at either of these Tech Titans at any point of time (even for a fleeting second before the inevitable feeling of self doubt rushes in) , trust me while I say this, in all seriousness – It IS possible!

If you are yet dubious, I’m sure this answer will convince you 🙂

I completely understand how you’re feeling. I graduated about three years ago with a BS in Computer Science and the only thing I wanted to do was work for Google. Before I graduated, I did well on a phone interview and was invited to interview on-site at YouTube for a Software Engineer position. I did the interview, walked out feeling great about my performance, and not too long after I got the dreaded rejection message. It took a long time and a lot of reflection to realize what went wrong.

It was my very first on-site technical interview. I literally had zero experience with it. Thinking back, I did everything embarrassingly wrong.

Get solid interview experience. Interviewing itself is a skill, and you don’t want to be honing that skill when it matters most. The more you interview, the more comfortable you will get. Everything else will follow when you just chill out and convey your thoughts clearly.

Think about how you’ll answer the generic “tell me a little about yourself” question. After many many interviews, I finally learned that this question is less about me and more about the interviewer. Frame your answer around what they’re looking to see from you (hint: brevity and relevance to the job). Make your pitch and sell it.

A year later, with more interview experience, I reapplied for the same position in a different office. Again, I did well on the phone interviews and got invited on-site.

I spent the next two weeks with a whiteboard and textbooks trying to sharpen my skills. Hours into the night I’d work on algorithms and data structures, trying not to make the same mistakes.

I came in to the interview and gave it everything I had. I was proud of myself for studying so hard and answering the tough questions. But again, I got rejected.

Wield your passions as strengths. This is one of the most important things I learned on my way to joining Google.

What did I do wrong? I interviewed for the wrong job. Like you, I’m very passionate about web development. I thought that with my CS degree, my natural career path was software engineering. I was forcing myself to become a developer that would program in C++ or Java everyday when my interests were actually in the front-end technologies like HTML/CSS/JavaScript.

I took this as a sign that I needed to realign my focus on web development and make that my career path. I read professional blogs, bought books, attended meetups; anything to learn more and become a better web developer.

A year later, I applied to the same office as last time, but for the position of User Interface Engineer. Again, I did well on the phone interviews and got invited on-site. My recruiter told me that he almost never sees anyone invited back for a third on-site interview.

Again, I studied for weeks, did the interviews, felt like I knocked them out of the park, and at the end of the day my interviewer came back in to wrap up and handed me a Google mug “for completing my third on-site interview”, like a trophy. Well, it turned out to be more of a consolation prize because again, I got my third rejection.

At this point several things happened. I wanted to give up. I wanted to change careers. Instead, I stopped focusing on getting one job at one place and I focused on self-improvement. I’ll never know exactly what went wrong in the interviews or how I could have answered better. It doesn’t matter anymore. I need to make the best of what I’ve got.

I made two figurative career-changing decisions: I started working on open source projects in areas that I care about and I also tried to learn everything possible about web performance optimizations. Through the meetups that I was already attending, I chose to stick with the New York Web Performance Meetup Group. I changed jobs to one that focused specifically on web performance, I got a speaking opportunity at the NY meetup group, and as a result I was offered a speaking opportunity at the mother of web performance conferences (Velocity). Things were great.

Maintain a healthy amount of optimistic persistence.

Out of the blue, I got an email from my very first recruiter from YouTube. A position opened up for a web developer, for which she thought I was a good fit. I pursued the opportunity, took the phone interview, and advanced to the on-site round.

I was back in California and went through the familiar gauntlet of tough questions. Like the three times before, there was one interview of the five that I really wished I had done better. Like a rerun, I’ve seen this play out a few times before and so I started to get worried.

Contrary to my anxiety and the emerging pattern of rejection, I actually got the job.

So, for anyone chasing their dream job:

  • Don’t rush into it. Do a hundred interviews for jobs you may not even want to prepare you for the one you actually want. Learn to sell yourself before you try to sell your technical skills.
  • Find your niche. Identify how you can best give back to the company. Hone your technical skills and do everything you can with what you’ve got to keep learning and push your career forward.
  • Don’t give up on it. Put yourself on a trajectory that leads to your success and ride it out.

Source: Quora (Read the others since there are a lot of incredible answers that will guide you to prepare for interviews )

Career Advice to the future Software Engineers

Gayle Laakmann McDowell on Quora –

Let me explain what awesome careers look like.

They don’t look like nice linear graphs, where you’re moving up a little bit each month. (Heck, even so-so careers don’t look like that. You don’t move up every month. You get a bit better at your career every month, but you move up in big steps.)

Great careers look more like this. They have some periods of slower growth and some “turning points” where your career shoots up.

The color changes? Those are career changes: software development to product management, sales to cofounder, etc.

They also have some setbacks. Because you know what? Being great requires taking some risks. And taking enough risks means you’ll fail a bit too.

So with that said…

Coding:

#1: Code. A lot. Schools are great at theory, but not so much at practical stuff. This is especially true at the top universities. Professors are academics and are often actually hostile to more “practical” forms of education. The best way to be a great coder is to just practice – a lot. It doesn’t matter so much what you code (open source, iPhone apps, etc.) as long as you’re coding and pushing yourself. If you are looking for guidance in learning how to code, we can help you out 🙂 Check our website to know more.

#2: Be language agnostic. Language is just a tool. It’s valuable to know a language deeply, but it’s also valuable to be learning new things. The best developers tend not to identify as a ____ developer.

Career choices:

#3: Prestige helps. Having a strong name on your resume helps open doors and show competence. If you can get a name like Google, Facebook, Amazon, Microsoft, Dropbox, etc, do it. (But don’t stay long. See #4.)  If youre looking for work at one of the top MNC’s in India, visit our placements page for more information.

#4: Leave the big companies quickly. If you want to build your career at a big company, then by all means, stay and build your career there. But if that’s not what you want, leave quickly. One or two years post-college at a company like Google is great. 10 years? Not so much. You will continue to learn, but there are diminishing returns of sticking around. (Unless you want to be a big company person.)

#5: If you want an A+ career, come to San Francisco bay area. I love Seattle and began my career there, but I have to be honest: there are so many more opportunities in tech in the bay area. You will limit yourself as an engineer (or product manager/tech business role) if you live elsewhere.

#6: If you don’t want an A+ career, don’t come to the bay area. It is extremely expensive here. Seriously. That’s worth it if you want a ton of career options. But if you just want a cushy career, there are more affordable cities with enough tech (like Seattle). A good software engineer can buy a nice house in Seattle. It’s a stretch in the bay area.

#7: If you don’t want to be a developer forever, then move on quickly. There is a lot of value in getting really deep technical expertise. But it doesn’t matter that much whether you spent two years as a developer or seven years. Within a few years of college graduation, make a choice. Do you want to be an engineer for the next 10, 20, 30 years or not? If you don’t, start trying to move on now. More time as an engineer won’t help you that much.

#8: Quit quickly. If I look at my friends who have switches jobs, almost all of them were thinking about quitting for the last 6 – 12 months. Some stayed for 2 or 3 years after they start saying that they want to quit. They’ve wasted so much time because of just a resistance to change. If you’re thinking about quitting, take action now. Start applying elsewhere – or possibly just quit outright. You probably won’t be very successful if you’re unhappy anyway, and there is a big opportunity cost in staying.

Dealing with others:

#9: Integrity matters. If you try to cheat and cut corners, it’ll haunt you. Do the right thing in life. It’s not only the good thing to do, but it’s also the smart thing to do. People will trust and like you more. More doors will open – and those doors might just be the breakthrough moments in your career.

#10: Be helpful. When possible, help people who ask for help. This is a nice thing to do as well as a smart thing to do. These people who ask you for help right now will be much more likely to help you in the future. That “help” might be introducing you to their friends who can help you more directly. So even if you don’t see how that person will be helpful, you don’t know who their buddies are or will be.

#11: Make friends. You actually can’t really be successful by yourself. If you’re an entrepreneur, you need employees and business connections. If you’re an employee, you need a job. Either way, it’s friends who will be key to opening up these opportunities. It’s friends, distant and close ones, who form the important part of your network, not that one person you met at a meetup and never talked to again.

Being awesome:

#12: Realize – no, internalize – that we’ve all got impostor syndrome. Even the most successful entrepreneurs and engineers (with very few exceptions) feel like they just got lucky and aren’t nearly as good as people think, and that one day soon they’re going to get “caught.” Truly internalizing just how widespread impostor syndrome is can help you realize that feeling like you’re a fraud doesn’t mean that you are.

#13: Start stuff. Show initiative. Good things come to those who don’twait. Seek out new opportunities. Start stuff – a hackathon, a club, a project, a company, a new running group, whatever. You will learn so much from doing this and it will open doors.

#14: Take risks. Seize opportunities. When you notice that little flicker of opportunity, seize it. Run with it. See where it goes. Don’t walk away just because you don’t know exactly where it’s going to go.

#15: Bias towards “yes.” A great career hinges on the “breakthrough” moments. The problem is that you often can’t identify those in advance. You don’t know where that coffee meeting that you don’t see the point in is going to lead. You won’t know that, two months down the line, that person will end up introducing you to a guy who needs some advice and winds up as your business partner. Maintain a strong bias towards saying yes.


All of these have a reason – usually multiple stories – behind them. They are things that I, or my friends/clients, have lived.

  • Lots of coding projects (#1) plus some friends (#11) resulted in my landing an internship at Microsoft after freshman year.
  • That paved the way to eventually landing a job at Google, which has opened countless doors (#3).
  • Initiative (#13) and seizing opportunities (#14), as opposed to careful planning and research, led to my launching two companies, both of which are profitable and just amazing experiences.
  • In fact, both of those companies also started as an unpredictable result of agreeing (#15) to do a favor for a friend (#10).
  • Acquisition consulting (now a core part of my business) started because someone asked me to help them. I didn’t really feel like it at the time, but I said yes (#15) because I’ve seen over and over again how valuable this philosophy is.

But I made mistakes, too.

  • I love Seattle (where I used to live), but being in the bay area has been so much better for my career. More opportunities and better opportunities, hands down (#5). It is a lot more expensive here though (#6), so if you’re not going to use those opportunities, go elsewhere.
  • I also stayed at Google too long probably. The extra time didn’t earn me much (#4). I eventually left because I realized I didn’t want to be a developer for my whole life (#7) and because I just wasn’t happy (#8).

Two more pieces of advice were “automatic” for me, but I’ve seen the consequences when other people don’t do this.

  • I’ve never identified too closely with languages and it’s enabled a lot of flexibility. When I’ve coached people who do, they get much more limited in their career (#2). Fewer companies to pick from and the language-specific developers are often stigmatized as being weaker.
  • As for integrity (#9), two stories come to mind. In both cases, someone’s drive for success caused them to ultimately hurt themselves.In the first situation, a colleague tried to take advantage of a legal loophole to back out of a very important commitment. He eventually backed down, but I would never work with him again. I also won’t help him if it’s any sort of help that requires trust. (That is, I’ll fill out a survey for him, but I won’t connect him with anyone.)In the second situation, a fellow author posted some fake negative reviews of my book in some stupid, short-sighted attempt at winning. When I confronted him, he made up all sorts of lies and accusations. Now, he periodically asks me to connect him to someone I know or if I want to work with him on something. I refuse. Again, it’s not revenge, it’s protecting myself and my friends.

If you’ve been tracking, you might notice that there’s one left: Impostor syndrome (#12).

I’ve known what impostor syndrome is for years, but it wasn’t until the last year or two that I realized that almost every successful person experiences it. This was an “a-ha” moment for me. It told me that not feeling good enough to do something didn’t mean that I wasn’t. As a result, I have more confidence and am more likely to launch something (#13), run with an opportunity (#14), or just say yes (#15).

Visit Quora

What would happen if Bill Gates, Mark Zuckerberg, or Steve Jobs appeared for an interview at a top Indian IT company?

Interviewer: Write a simple program to print “Hello world” in C.

Steve: Ok. First tell me what compiler am I using? What is the resolution of the screen on which my program will execute? Does it support Comic Sans? Will I like the keyboard that I will be typing the program in? Or is it some bullshit useless keyboard designed by mediocre loser people like you who just follow the motions and templates to push a design through so that you can forget about your end user and live a happy blissful life while I loathe my life typing into your pathetic attempt of making a consumer eyesore you call a keyboard?

Interviewer: Get out! Next!

Bill Gates: Sure. But do you only want to write “Hello World” on the screen? I mean you could print it on  command prompt which is cool for me, but for a person like you i would prefer printing it on a web browser which you can fathom easily. I think all computers should have browsers, don’t you? Just think of the time and effort we would save if everyone could write “Hello world” by just clicking a button! Then we could probably use the rest of their time to help other third world countries get rid of life threatening diseases and…..

Interviewer: Please forgive me…. next

Mark: Sure dude. I can do that for you. But wouldn’t it be better if someone saw me doing it or i could tell everyone I am doing this right now so that everyone knows that I can write a “Hello World” program? Wouldn’t you like it? I mean you can do a lot of cool stuff about it like other people can suggest you how to improve on the code or how they feel about it…..

Interviewer: I don’t feel good about you. Next.

Source: Quora

PS – If you like the content we post on our blogs, be sure to visit our website 🙂

What is Programming really about?

tumblr_nkmxc8XxmE1tpyjj8o1_400

A programmer was asked an interview question – If you had to construct a swimming pool for Mark Zuckerberg and had no budget limit to your project, describe the pool you will make?

Now this guy didn’t have a clue about how swimming pools are made or what are the requirements for one. But his answer was what you can expect out of a programmer.

His answer – 
Let’s consider the components here – A pool, a fountain nearby, a changing room, a bar, a resting/sunbathing area, and some other stuff rich people have by their pools. Since here we are referring only the pool, I will only describe the pool. Also since Mark loves Star Wars, this would be a Star Wars themed pool.

Let’s consider the pool to be rectangular with a standard size of 16ft by 32ft.
Now for lights, there will be one  at every 4 ft along the perimeter. The colors of the lights will change if Mark decides to select Sith theme or a Jedi theme. On a closer look at the each of the light you will see a distinct star wars character on each of them, which will only be visible when you are close enough. The lights will also ….. **gets interrupted by the interviewer**

Interviewer – Let’s move on to another question.

Programmer – But I haven’t finished my answer sir……. in fact, I had barely started.

Interviewer(who was a wise man) – You don’t need to, you’re shortlisted for the next round.

Programming is about taking a problem (making the pool) and defining a solution to it(size of pool, lights, right down to each light) where every small detail is elaborated cause you are trying to convey it to the dumbest thing on a planet(a computer)

If this article interested you enough to advance your skills in programming or begin your career in the IT industry, visit Swabhav Techlabs.

To see the answer on quora

Never heard an explanation on Object Oriented Programming from anyone so well.

bicycle-for-the-mind

Here, in an excerpt from a 1994 Rolling Stone interview, Jobs explains what object oriented programming is:

Jeff Goodell: Would you explain, in simple terms, exactly what object-oriented software is?

Steve Jobs: Objects are like people. They’re living, breathing things that have knowledge inside them about how to do things and have memory inside them so they can remember things. And rather than interacting with them at a very low level, you interact with them at a very high level of abstraction, like we’re doing right here.

Here’s an example: If I’m your laundry object, you can give me your dirty clothes and send me a message that says, “Can you get my clothes laundered, please.” I happen to know where the best laundry place in San Francisco is. And I speak English, and I have dollars in my pockets. So I go out and hail a taxicab and tell the driver to take me to this place in San Francisco. I go get your clothes laundered, I jump back in the cab, I get back here. I give you your clean clothes and say, “Here are your clean clothes.”

You have no idea how I did that. You have no knowledge of the laundry place. Maybe you speak French, and you can’t even hail a taxi. You can’t pay for one, you don’t have dollars in your pocket. Yet I knew how to do all of that. And you didn’t have to know any of it. All that complexity was hidden inside of me, and we were able to interact at a very high level of abstraction. That’s what objects are. They encapsulate complexity, and the interfaces to that complexity are high level.

You can check out the video on: https://www.youtube.com/watch?v=2kjtQnPqq2U

To read the entire Interview: http://www.rollingstone.com/culture/news/steve-jobs-in-1994-the-rolling-stone-interview-20110117

Tips to Master Programming (Shared by own experiences of Coding, Great answer written on Quora)

Iterate. Successive refinement is how we get to great code and great products.

Simpler is usually better. Watch Rich Hickey‘s talk Simple Made Easy, and read Kent Beck‘s Xp Simplicity Rules.

Don’t be clever. Don’t try to write complicated code on purpose to show how smart you are. Write simple, clear, reusable code. Think Simplicity, Clarity, Generality. Read “The Practice of Programming” by Brian Kernighan and Rob Pike. Speaking of Brian Kernighan, also read “The C Programming Language” by Brian Kernighan and Dennis Ritchie.

SRP (single responsibility principle) and DRY (don’t repeat yourself)principles go a long way towards clean code. Read “Clean Code” by Uncle Bob Martin (Robert C. Martin)

You ain’t gonna need it (YAGNI) applies most of the time. In general, just design for today’s requirements, to prevent over engineering. Having said that, sometimes it’s necessary to design for future growth. There’s a balance – it’s up to you to find it.

Code with obviously no bugs is immensely better than code with no obvious bugs.

Being able to reason about your code is paramount to high quality.

Requirements are rarely cast in stone. As an engineer/programmer, you have a responsibility to question things that look unclear, in doubt and questionable.  Sometimes when people don’t like the questions, you really need to question more intently, though possibly with careful discretion. (Courtesy of Bryan Kelly)

Start with why. Watch Simon Sinek‘s talk How great leaders inspire action

Clients don’t really know what they want, and that includes your manager. It’s your job to elicit their true needs.

Despite what process you follow, some amount of up front design is required – how much should be proportional to complexity. Read “Domain Driven Design” by Eric Evans.

Recognizing common Design patterns is important. Don’t treat patterns as a hammer looking for a nail. Read “Refactoring to Patterns” by Joshua Kerievsky. Read Steven Grimm’s answer to What are the most important design patterns that software engineers should know to work at Google, Amazon and Facebook?

SOLID principles (Single Responsibility Principle, Open/Closed Principle, Liskov Substitution Principle, Interface Segregation Principle, Dependency Inversion Principle) are far more important than design patterns. Read Uncle Bob’s article Principles Of OOD

Beware of dogma. There’s usually more than one way of doing things. The term “best practice” is overused. There are some good practices in software development, but beware someone telling you that something is the “best” way of doing something.

No one has it all figured out. Some know more than others. Always try to be the worst member in the band. Read “The Passionate Programmer” by Chad Fowler.

There’s no such thing as perfect. You can always be better. “The perfect is the enemy of the good” – Voltaire.

If you don’t design for scalability, your code won’t scale. If you don’t design for security, your code won’t be secure. Same applies for all -ilities.

Learn multiple paradigms. OOPFunctional, etc. Your OO code will improve after studying functional languages such as Haskell and Lisp.

Watch OOPSLA 97 Keynote by Alan Kay, “The Computer Revolution Hasn’t Happened Yet”.

Never stop learning. Read as many books as you can, but not only technical books. Read “Zen And The Art of Motorcycle Maintenance” by Robert M. Pirsig.

Read “The Pragmatic Programmer” by Andy Hunt and Dave Thomas.

Read “Code Complete 2” by Steve McConnell

Care about your work. Care about your customers. The code we write allows the users of our code to get their shit done, without our software getting in their way.

Always ask “what problem am I trying to solve”? 

In general, stick to solving one problem at a time. When you spot other problems, note them and come back to them later.

Be where you’re at. This is a life lesson that applies to software development. When you commit to doing something, focus on doing it. When your washing the dishes focus on washing the dishes – forget all the things that stressed you out that day. If you are spending time with your family, be there – turn off your phone, forget that tough problem you’ve been wrestling with. When you’re in a meeting, participate – focus on the conversation and forget about the work that’s piled up. Read “Zen Mind, Beginner’s Mind” by Shunryu Suzuki

Ask “what’s the simplest thing that can possibly work?” Read “eXtreme Programming Explained” by Kent Beck. First version is supposedly more extreme than the second.

Be OK with you. You will never know everything – that is impossible. Keep learning, but don’t get caught up on what you don’t know. Watch Kent Beck‘s talk Ease at Work 

Be humble. Everyone is at different points of learning in their career. Help others on their path. Ask for help when you need it. Give back to the community. Watch Leon Gersing‘s talk “Truth, Myth and Reality in Software Development”

It’s OK to be average –  Read the article In Praise Of The Average Developer – Why the myth of the “10x” programmer is so destructive by Matt Asay. Matt Asay references Jacob Kaplan-Moss‘s keynote at PyCon 2015.

Multi-tasking is an illusion. Computers get away with it because they can context switch really fast (most of the time). Context switching for us mere mortals has a high cost. Do one thing at a time, and do it well.

There is no spoon. Just a reminder to lighten up a little bit. Have fun.

PS – To check the answer on quora : http://www.quora.com/Computer-Programmers/What-are-the-greatest-programming-tips-and-tricks-you-have-learned-on-your-own-by-years-of-coding

Chapter 1: The Tipping point in the life of a B.E Comp/IT Graduate

Heyy there! 😀

How have you been? What has been going on lately in your life? Oh! I know what have you been thinking about!

Let me guess – “I have just passed out. My last semester grades have been pretty good. I need a nice job now. I have to start supporting my family.  What I would want to do with that money? Oh! May be I could buy that watch or perhaps that perfume”

If your thoughts are somewhere along these lines, Welcome Aboard 🙂

These thoughts are currently going on in the minds of all those 8000 graduates along with you, who are actively looking to fulfill that same aim.

But behind these thoughts go –

Applying in way too many companies, sitting for countless number of rounds handling the rejection, that feeling of being disappointed trying to meet parents expectations and in trying to re-motivate yourself to continue the same cycle.

It’s exhausting. We know it. But does it end once you get the job? Does it really? What comes next is worse!! What you read before was “The calm” before “The chaos”.

You got the job. Congratulations: D But, Hey what’s the job position? Testing, Maintenance..? What Technology? Do you have the required skills? The pay is decent but how are your Team Leaders? Is your boss a motivator or one of those stereotypes? How are your colleagues? Do you feel a team member or are you lonely? Office politicsssss!! Don’t even get me started on that!

Am I painting you a nice picture? 🙂

You would start to think the entire process sounds like a messed up maze. Well, lucky for you – it has an exit route 🙂

Lets start walking on it, shall we? 😀

We begin by taking a deep breath.

Alright, hear me out on this one – your 4 years of college life not really been too fruitful. I mean yes, those 1400 days were  epic when it came to bunking classes, going out with friends, troubling the teachers, spending 80% of your time in canteens :’) But out of those 30 subjects that the college was supposed to “teach” you, only 5/6 matter when it comes to applying it in the real life and by that I mean using it in the INDUSTRAAYYYY!!

(Sorry for being so cruel. Trust me on this one though. Seriously)

Does this mean that you should probably feel gloomy and cry somewhere in the corner of your room? You could if you want to, I wouldn’t suggest it though 😛 Where exactly is the solution to the problem then?

Here it is – Dont hurry yourself when it comes finding a job with a good pay. Just because it satisfies your temporary dream of being placed, dont rush into the trap. 

 As Magnus Carlsen, the world chess champion said “I consider the first move to the most strategic way kids can live up to their full potential”

THIS is going to be YOUR first move in the Industry. Consider on making it big for the future, not for the present. Be smart. Be sensible. 

Learn what differentiates you from the rest of the crowd. What is it that is unique in you from rest of those 8000 BE Comp/IT graduates?

Learning Java, .Net, C# from the training institutes and paying for 2 month courses is fine. But that is something what everyone does.

What is it that is booming in the market, that has a crazy demand for but only a very few amount of people in the Industry know? Geniuses or Mavericks as we would call them. They know the secret, the hidden treasure, the wonder that needs to be learnt by each and everyone one of those in the IT field. It lays out the brightest future for the one’s who know it and for the ones who don’t .. Well, they don’t even know that they don’t know it. (Take a minute to get the hang of it)

It’s changing the industry. It’s imbibed in the cultures of Google and Facebook. THAT is what you should learn. That, which came right from the birthplace of Technology – The Silicon Valley.

Okay, I won’t keep you in a mystery anymore. ITS… hang on… its legend..Wait for it..daryyy…its.. *Drum rolls* DESIGN PATTERNS AND DESIGN THINKINGGG!! 😀

I’ll give you factual info so that you don’t think I’m crazy 😛

Here, have a look – http://www.thehindubusinessline.com/features/smartbuy/tech-news/infosys-changes-strategy-to-train-workers-in-design-thinking/article7275444.ece

Why is design patterns and design thinking such a mystery though? Why isn’t it that anyone knows about it much? Is it that important that you should stop running behind a job and those tech courses and focus on this first?? What is it in the first place, these design patterns and design thinking?

Wait for my next post to find out more 😉 Or even better, Google it out and may be you could help me figure out what it’s all about 😀

Till then, signing out. Cheers!! xx