First B Notice Form Download: Fill & Download for Free

I sucked at my work.I failed to complete most tasks on time. My peers would joke about how me to sticking to a deadline was akin to a politician living up to his word.I would put in 10 — 12 hours each day. But I never moved forward.One day, my boss emailed me asking for a list of tasks I perform during that day. I freaked out. Surely I was going to lose my job.I sent him my list after 3 days — after all, I had to live up to my reputation of missing deadlines.I didn’t sleep that night.The next day, my boss called me into his cabin. This is it, I thought. I’m gonna get fired for the first time in my life. I should start preparing for the handover process.But that didn’t happen. He made me sit down and offered a glass of water. Then he said, “Vishal, I noticed you cannot perform important tasks. You do a hundred things, but I can’t see any results.”“I try sir, but I keep getting burdened with additional work,” I said. Beads of sweat formed on my brow despite the cool temperature in his cabin. “Team members tell me their work is urgent. I know I get distracted. But I want to help everyone. When I try to say ‘no’, it doesn’t work. Yesterday Nishant scolded me for turning down his work.”The last sentence was a (harmless) lie. But hey, I was trying to defend myself.The ABCD of the Professional WorldI think my boss saw through the lie. Because he smiled and said, “Vishal, today I’ll share a piece of wisdom with you, which I got from the boss I learned the most from. It’s this:When you work in the corporate, prioritize your work as ABCD.A — Apna kaam (your own work)B — Boss ka kaam (your boss’ work)C — Company ka kaam (your organization’s work)D — Doosron ka kaam (others’ work).”How to Apply ABCD1. Apna KaamPrioritize the work which you’ve been hired for first. Ignore everything else. When your boss gives you a task, she won’t let you off the hook for not completing your work because you were doing hers.2. Boss ka kaamHowever, it’s smart to take time out and complete your boss’ work even when you’re busy with yours. Hence, prioritize your manager’s work along with yours. Put everything else on the back burner. It’s also a good excuse to turn down favors which team members ask of you.3. Company ka kaamAfter this, prioritize any work the company has given you. For instance, a report which another department has asked for, or a meeting which another business unit wants with you, and so on.4. Doosron ka kaamFinally, once you’ve taken care of A, B and C, you can take on others’ work in your spare time. Until then, learn to say no in ways your peers won’t find offensive.I implemented this technique from that day. My productivity skyrocketed. I could do much more. I also got noticed by the right people within the company. When I left the firm, my boss dropped me a message saying he felt like his oxygen supply had been cut off. It was one of the best compliments ever.ABCD — As simple as thatP.S. Today, writing has become a crucial skill that will make you distinguish yourself in the corporate world. If you want to sharpen this skill, you can download this free guide.

In the beginning, it feels “Insanely intense”. Here is my perspective:I reached the campus a couple of days before the beginning of the course. During the initial interactions with a few seniors, staff, alumni and professors, everyone slipped a common line “If you can survive the first six months at IIMA then you can survive anything in life”. I didn’t understand it back then. I thought it must be tough but I had no idea what I was entering into.After the registration on the first day, I collected my course content for the first slot (1st half of the 1st term), I got 6 casemates (an average of 200 pages each) and 8 books (an average of 500 pages each). We also got the class schedule for the first term. In term of the number of classes, it is just 3 lectures per day of 75 minutes each. But for each of these classes, We had to read 70–80 pages of theory, understand it completely and solve a 20–30 pages case. We were expected to read and understand everything and present it in the classes. On average, we had to read and understand 300 pages/day.In one of the first few lectures, a professor said: “We make sure that you have enough work for 24 hours in a day and it is up to you to accommodate your sleep, hygiene, and other activities in your daily schedule”.Also, one of the seniors who was institute rank 1 told us on the first day, “Never procrastinate, if you have to study something today, finish it off, you won’t get time to do it during rest of the term”The grill was on which continued for the next 5 months, without any break. No term break or something.Apart from the daily classes and preparation, there are additional academic and non-academic activities which make the first term at IIM notorious:WAC: This a dreaded name on campus, every wimwian (IIM A is also called WIMWI within the campus) will remember it for his/her life. It is an excellent course which changes the whole thought process of your writing. You need to write an analysis of a case (Written Analysis and Communication (WAC)it is a different subject altogether). It takes at least 20 hours effort complete the assignment. I remember in our batch, there were just 13 students (out of 360) who got the best grade “B+”. For your information, the order of grades at IIMA is A+, A, A-, B+ and so on.Surprise Quiz: Once the classes are over at 1:10 pm, everyone heads for the mess for lunch. But till 1:30 pm, everyone keeps on looking at the mess noticeboard because that is where the surprise quiz notice is put-up for a quiz at 2:30 pm. If there is a quiz, almost everyone throws plates and run to the hostels so that they study in those 50–55 minutes to get good enough marks in these quizzes. If there is no quiz then you can peacefully have your lunch.T-NITE: A breather after the rigor of slot 1, an intersection (for first years only) cultural events competition is organized over a span of 4 days.That Dreaded clock: Deadlines at IIMA were different. For an 8:45 am class, you need to enter before 8:44:59 am, 8:45:00 is late.During the first term, you need to prepare for your summer internship interviews which create additional pressure. Resume making, resume verification, recruiter form filling, preparing answers for 50 personal questions with the sacrosanct deadlines, make sure that your toes all the time. Also, you need to prepare for your choice of recruiting firms as well.The exam time is the most peaceful time, where you need to think about only one thing which is “Study” and everyone at IIMA is very good at it.There are other perspectives as well like it is not easy to fail at IIMA, given that you are at IIMA, you are smart enough. A very few people at IIMA fail but those who fail do not work hard enough when everyone else is slogging their ass-off. It is a conveyor belt, where you begin at the starting point and with the flow, you move out of it at the other end.Anyone can withstand such grueling schedule for a week or two but doing it for 6 months is what makes it insane. People make their own coping mechanism to deal with this kind of pressure where you sleep just 4 hours a day, study for 8–10 hour and write assignments for another 5–6 hours a day. Some people go for a refreshing run of 15 minutes, some people go to play Frisbee at midnight at LKP, some people have a smoke to relieve the pressure. But, everyone learns that their limits have been pushed and now nothing is impossible.And you learn after the first 3 slots at IIMA: “If you can survive the first six months at IIMA then you can survive anything in life”All the bestKamlesh ChauhanNote: CAT aspirants can download the Bfactory app from playstore to chat with my team/me and to get access to best CAT prep free content/courses.

DLL Hell mostly arises when you have two (or more) different programs each of which requires a different version of the same DLL.For example, you get some program A that uses a “bitmapped_button.dll”. Then you get another program B that uses an older version of “bitmapped_button.dll”.If you load Program A, then Program B, everything may be fine (if the newer version of the DLL is backward compatible with the older one). But if you try to run Program A when Program B is already running, Program A tries to use the older version of the DLL (since it’s already loaded), and won’t load because it uses a feature that’s missing from the older DLL.In a few cases, a newer DLL may both add some new features *and* remove some old features that an older one provided—in which case either Program A or B can run by itself, but trying to run both at once fails.This was exacerbated by the fact that early versions of Windows not only allowed but even *expected* programs to install DLLs into directories that were shared system-wide. That would probably be difficult to manage well (even at best), but many installers didn’t bother checking version numbers—they just copied *their* copy of a DLL into the system directory, without bothering to notice that they were replacing a new DLL with a much older one (and in the process, breaking lots of other programs that depended on the newer one, of course).There are quite a few more possibilities, but I think that’s enough for the moment. Let’s get to the real question: how does Linux solve this? The short answer is that Linux itself mostly doesn’t even try to fix the problem.Linux programmers do two things that help ameliorate the problem though. The first (which Jesse Pollard already mentioned) is adding version numbers into the names of most shared object files. This is handy and useful, but it’s not (even close to) the whole story.The second (and much bigger) step that’s taken depends heavily upon the fact that most software for Linux has source code available. When you install a copy of some program on Linux, you’re normally installing a program that was re-compiled specifically for that version of Linux.When I buy a program for Windows, I’m typically buying a license to one specific pre-compiled binary (and possibly patches that get released for it). I run that binary as-is on whatever version of Windows I’m using. It’s entirely possible to run (for example) three or more different versions of exactly the same program on the same machine, each requiring different versions of the same DLLs at the same time. This makes managing dependencies quite difficult at times.Rather than trying to fix the problem, more often than not Linux simply eliminates it. If I want to run Libre Office on Ubuntu 16.04, I use APT to install a copy of Libre Office that has been built specifically for Ubuntu 16.04. If I download an update to Ubuntu that (for example) fixes a security bug in some shared object file, APT keeps track of the dependency, so I also update my copy of Libre Office to one that’s been built against the new version of that shared object file.If I later upgrade to Ubuntu 18.04 (or 18.10 or whatever), I don’t (at least typically)continue to run my old copy of Libre Office on the new version of Linux. Rather, I end up installing a new copy of Libre Office, built specifically for the new version of Linux.So, any given installation of Windows will typically have what started out as a few (potentially quite a few) different dependency trees. When you install a program, you need to figure out how much of its original dependency tree needs to be grafted into the current system for it to work. You might easily have pieces that were originally built for Windows 95, a few for Windows 98, some others for Windows 2000, a couple for Windows XP, one for Windows 7, all running under Windows 10.In Linux, at least under normal circumstances, you really have one huge tree. Every program you install on a particular version of Linux has been built against exactly that copy of Linux. So, we don’t usually need to use things like version numbers to sort out which shared object is needed by which program—because they were all built to depend on the same shared object in the first place.Now, it’s certainly true that I can download source code, and a newer version of a shared object that may be shared system-wide, without updating every program that depends on it. When/if I do that, version numbering the object files can certainly be awfully handy—but for an awful lot of ordinary users, this situation simply doesn’t arise in the first place.