Yes Password can be rest by sticky key attack!

Here we all sometimes not be able to recall the login password of your computer, and also
who want to illegally login to someone's computer uses these basic attacks.

These attacks are more basic and more affective so, all of you have a knowledge about these attacks.

Sticky key Attack

Sticky Keys is part of Windows Ease of Access features that allows a user to tap the Shift, Ctrl, Alt or Windows key once to achieve the same effect as holding the key down.

and when you press 5 times SHIFT key it popups a Windows login screen, the Sticky Keys application (sethc.exe) will launch and ask if you want to enable sticky keys feature.

this method work with only when you replace some files ,this hacking method works by replacing the sethc.exe file with cmd.exe. 

 From the Command Prompt, you have sufficient privileges to reset a lost password without knowing your current password. This method works flawlessly with all versions of Windows XP, Vista, 7, 8, 8.1 and 10.

and then when we press 5 times SHIFT key then the cmd.exe open and then , have to type some cmds on it

net user user_name new_password

restore the sethc.exe file we overwrote. Enjoy!

Is Client Side Script is able to VALIDATE?

Programmers who design websites are always want to validate the data submitted by the user to any website.

there are may ways to validate the data by using server side , client side and in data servers methods.

Many of us who want to make website and take input for user with validating  it on client side is not good for site health if not properly used.

there are many ways by which we can alter the validating detail and submit some incorrect info to website and make able to produce result accordingly.

JAVASCRIPT ATTACK

These attacks are used to bypass a validating process of a site which checks the information from client side.

they just have to open that site and load on there browser

than just have to input some java scripts on that site to check weather it is vulnerable or not.

javascript:alert(1);

then it produce an alert message.

it means that you are done with javascript.

after that if the site is storing the data in there cookies ,than they change the cookies store by the site and make it true if required to proceed further. 

javascript:alert(document.cookie);

this display the cookie store in.

javascript:document.cookie.replace(current_value, your_value);

this change the current value of the cookies stored in.

FORM VALUES ALSO CHANGE BY THIS

javascript:void(document.form[0].value="your_value";

this makes the value of form according to yours.

these are the ways by which anyone can manipulate the values of client side script validation, so be aware before make use of these syntax.

USE PROPER VALIDATION TO BE SAFE FROM THESE ATTACKS.

Removal of Some PENDRIVE Virus | Shortcut | Application

There are many virus which are very harmful for our data , but antivirus work well to remove it, but what happen when they are not detected by some antivirus.

Some virus which come from infected Computer and damage our Data Traveler data are very dangerous ,some virus which convert all files to shortcut and some virus convert files to small .exe format or some specific format file which get copied to other devices.

These are not virus , but only some autorun script which run in computer and convert or modify our data which is only be understand by these script, so antivirus which do not check any autorunnig script are not able to detected.

Here are some solution to remove that virus or just correct that changes done by that script.

Removal of shortcut virus

=> just open RUN (wind+r)

=> open RUN as admin mode
=> type this cmd         
   attrib g:*.*  /d /s -h -r -s  (replace g with your infect disk name)
=> press enter.
:-)  you recovered from that small virus.

Recovery of folder to application Virus

=>open RUN (wind+r)

=> open RUN as admin mode
=>type this cmd           
attrib -r -h -s autorun.inf (open the folder which is infected)
=>press enter.
:-)

this means that these virus only covert the attribute or type of the present data and make new file according to the script, so these are recoverable changes, so don't be panic.

How they hack into a SITE ,Vulnerable for SQL injection?

SQL Injection Attack

Here is a hacking method which is done on site which Vulnerable for SQL injection.

HOW WE CAN FIND IF IT IS VULNERABLE OR NOT?
If we see in the website source code and if that source contain some <form> which send data to the server and produce result on input query, which connect to database, than by some wrong sql query inputs we can find if it is vulnerable !

than after that, have to find that how it checks the input field query which is coming from the user side by some input field to server.

like:
if the input by a <form> is check in server like this:

&user_name is the input coming from the user input form.

SELECT column_name(s) FROM table_name where user_name="&user_name";

 then

if we have to correct the input and produce , a always TRUE Statement
so ,the input be like this

" OR ""="

this makes the above query be looks like this

SELECT column_name(s) FROM table_name where user_name="" OR ""="";

this means that it is always TRUE no matter how the input is.

THIS IS USED BY THE HACKER to gain access without password and user name or user id of any user of that site, so be aware when you are writing the code which checks and produced the result from the sql database .

always check that the input coming from the user side  don,t contain special characters (=,(,),*,!,%,$,etc)  and the words like :or ,and ,select ,sql, like.

there are many tools which can find the vulnerability of this attack.
So,be aware of this attack , this is mostly used and most simple attack for attackers and very easy to find VULNERABLE sites for this attack.

Is the complexity of Google's search ranking algorithms increasing or decreasing over time?

I don’t work at Google, but I have worked on Bing search ranking and at other search engines, and have friends working on Google search. Given what I know, here is how I expect the complexity of Google’s search ranking algorithms to have changed over time.

The diagram shows long periods of time where the complexity keeps on increasing as you make small incremental improvements to the ranking algorithms. These long periods of increasing complexity are interspersed by periods of sudden reduction in complexity brought about by replacing complex heuristics by machine learning and other simplifications.

This diagram is obviously an oversimplification, but I hope it gets the main point across. Let’s dive into the details of why this happens.

Let’s start with what we know about Google search ranking publicly:

1. Google search ranking is a fairly complex beast. There are thousands of features that influence ranking, and quite a few of them are complex enough that they are best learned using their own machine learning algorithms to calculate them (E.g. search query embeddings).
2. Traditionally, Google has resisted using machine learning for their core search ranking algorithm. [1]
3. But more recently, there has been a shift towards using more machine learning in search, especially some of the stuff that the Google Brain team has built. [2]  [3]

Given this, I expect the current Google search to be a combination of heuristics, that are used at some places, and machine learning, that is used at other places. It’s still unclear whether the top level ranking function is machine learned or heuristic. My personal guess is that it’s still a heuristic function that combines a few machine learned and a few heuristic scores.

Here is a rule of thumb for the complexity of ML systems that is generally agreed upon by ML practitioners:

1. A simple, intuitive heuristic is less complex to understand and maintain than a Machine Learned system.
2. However, a well-designed ML system is less complex than a complex heuristic.

These closely match rules 1 and 3 from the rules of ML put forward by Google’s own Martin Zinkevich. For the complexity of search ranking specifically, read my answer on the complexity of heuristics vs. ML ranking here: What are the pros and cons of using a machine learned vs. heuristic / score-based model for search ranking?

Given this, I expect the arc of complexity for the Google search ranking algorithms to have adopted a sawtooth pattern as shown above:

1. You start off with some heuristics for ranking. Over time these heuristics get more complex, since you need to encode more rules in your search engine to make it better.
2. At some point, the system becomes complex enough that you need to take a step back and work on reducing the complexity of the system. You might do this by moving some of the heuristics to ML systems, or do other things like feature ablation or consolidation of existing ML systems. Usually these are deliberate efforts that lead to a sudden decrease in complexity of the system.
3. Once your system reaches the planned lower complexity state, you repeat steps 1 & 2 over and over. Given that the search engine needs to get more relevant for a wider range of queries over time, the overall complexity trend of the system, in spite of these “sawtooths” will still be slightly positive. Depending on how good Google is at this, they will try to keep the slope of this long term trend to a minimum.

Footnotes

[1] Edmond Lau's answer to Why is machine learning used heavily for Google's ad ranking and less for their search ranking?

[2] Google Turning Its Lucrative Web Search Over to AI Machines

[3] Now we know: Here are Google's top 3 search ranking factors

What does China make people promise to do when it lends them a panda?

When China gives a zoo a panda, it tends to be accompanied by the signing of a document usually called a "cooperative research and breeding agreement" pipeline.

The Smithsonian Institute sent me a copy of the most recent agreement, from 2011, in effect between China and the U.S. governing the two pandas at the  D.C. National Zoo. I've posted it here: http://web.mit.edu/mherdeg/Publi.... This agreement might well mirror other similar agreements that China has with other countries.

Here are some of the highlights:

1. The U.S. pays China $500,000 per year, of which 70% goes to conservation of the giant panda in China, 20% goes to the Wolong China Conservation and Research Center for the Giant Panda, and 10% goes to fees and expenses.
2. This contract took effect on Jan 20 2011, but the prior contract expired on Dec 6 2010! There was a brief period when there was no contract at all governing the pandas! Panda anarchy! (*This* contract says that, retroactively, the old one was in effect.)
3. The pandas belong to China and so do any of their offspring. If there are any offspring, they must be returned to China before they turn four years old.
4. The agreement expressly forbids panda cloning research:
   
   Without prior written approval from the Chinese Party, the American Party shall not conduct any activity beyond the term of this Agreement related to the above mentioned giant pandas or their offspring, nor shall the American Party collect samples such as genetic materials of the giant panda for scientific research or transfer any samples to a third party.
   …
   The American Party may conduct routine health examination or other necessary activity for emergency anesthesia without approval by the Chinese Party, however, it shall keep record of such activity and preserve any samples collected during the process, and return such record and sample to the Chinese Party upon expiration or termination of this Agreement."
5. America must buy a $1 million panda life insurance policy for each panda who is more than 180 days old. China is the sole beneficiary.
6. If a panda dies because of American misconduct and the panda is more than 18 months old, America has to pay China $800,000.
7. "If one of the giant pandas (not including their offspring) dies during the term of this Agreement, both Parties shall friendly negotiate whether to replace the dead one with another panda and whether to maintain the existing giant panda."
8. "This Agreement, written in both Chinese and English languages, both versions shall have the exact legal effect. If conflict exists in the two versions, the Chinese version overrides English version and shall be used as the basis for clarification."

----https://www.quora.com/What-does-China-make-people-promise-to-do-when-it-lends-them-a-panda/answer/Michael-McGraw-Herdeg#_=_

Want a Job At google in 2 years ?

1. Become fantastic at making software (end to end… coding, SW design, debugging…. )
2. Bring some sort of impactful results from your projects to the table when applying to any large tech company (including Google)
3. A potential path is:
   1. Study open computer science programs that mirror a reputable university curriculum. (MOOCs and free programming resources are plentiful). Learn to code in a couple popular programming languages as you go, usually by making simple things… web services, applications, etc. (This could be year one, but realistically it will be longer)
   2. When you get your coding skills up, start contributing to open source projects that matter to the companies you want to work for. (Projects that contribute to cloud platforms, machine learning, AI, operating systems, etc). Learn to interact with fellow programmers in a meritocratic environment in the process, and take a lot of feedback / lumps to become a better coder.
   3. Start your own open source projects / or your own online business that solve problems in the domain you're focusing on. (Assumption: by emersing yourself in a domain, you'll be better positioned to identify problems that others need solved, but lack support. If that domain is sought after by large tech companies, I'd claim your skills are more valued)
   4. Build a portfolio of amazing things you and others have accomplished from your contributions from 2 and 3. You might find this easier to do through working in a smaller startup environment that's equally focused on software that large tech companies are interested in.

The World In 2025

1. A $1,000 Human Brain

In 2025, $1,000 should buy you a computer able to calculate at 10^16 cycles per second (10,000 trillion cycles per second), the equivalent processing speed of the human brain.

2. A Trillion-Sensor Economy

The Internet of Everything describes the networked connections between devices, people, processes and data. By 2025, the IoE will exceed 100 billion connected devices, each with a dozen or more sensors collecting data. This will lead to a trillion-sensor economy driving a data revolution beyond our imagination. Cisco's recent report estimates the IoE will generate $19 trillion of newly created value.

3. Perfect Knowledge

We're heading towards a world of perfect knowledge. With a trillion sensors gathering data everywhere (autonomous cars, satellite systems, drones, wearables, cameras), you'll be able to know anything you want, anytime, anywhere, and query that data for answers and insights.

4. 8 Billion Hyper-Connected People

Facebook (Internet.org), SpaceX, Google (Project Loon), Qualcomm and Virgin (OneWeb) are planning to provide global connectivity to every human on Earth at speeds exceeding one megabit per second.
We will grow from three to eight billion connected humans, adding five billion new consumers into the global economy. They represent tens of trillions of new dollars flowing into the global economy. And they are not coming online like we did 20 years ago with a 9600 modem on AOL. They're coming online with a 1 Mbps connection and access to the world's information on Google, cloud 3D printing, Amazon Web Services, artificial intelligence with Watson, crowdfunding, crowdsourcing, and more.

5. Disruption of Healthcare

Existing healthcare institutions will be crushed as new business models with better and more efficient care emerge. Thousands of startups, as well as today's data giants (Google, Apple, Microsoft, SAP, IBM, etc.) will all enter this lucrative $3.8 trillion healthcare industry with new business models that dematerialize, demonetize and democratize today's bureaucratic and inefficient system.
Biometric sensing (wearables) and AI will make each of us the CEOs of our own health. Large-scale genomic sequencing and machine learning will allow us to understand the root cause of cancer, heart disease and neurodegenerative disease and what to do about it. Robotic surgeons can carry out an autonomous surgical procedure perfectly (every time) for pennies on the dollar. Each of us will be able to regrow a heart, liver, lung or kidney when we need it, instead of waiting for the donor to die.

6. Augmented and Virtual Reality

Billions of dollars invested by Facebook (Oculus), Google (Magic Leap), Microsoft (Hololens), Sony, Qualcomm, HTC and others will lead to a new generation of displays and user interfaces.
The screen as we know it — on your phone, your computer and your TV — will disappear and be replaced by eyewear. Not the geeky Google Glass, but stylish equivalents to what the well-dressed fashionistas are wearing today. The result will be a massive disruption in a number of industries ranging from consumer retail, to real estate, education, travel, entertainment, and the fundamental ways we operate as humans.

7. Early Days of JARVIS

Artificial intelligence research will make strides in the next decade. If you think Siri is useful now, the next decade's generation of Siri will be much more like JARVIS from Iron Man, with expanded capabilities to understand and answer. Companies like IBM Watson, DeepMind and Vicarious continue to hunker down and develop next-generation AI systems. In a decade, it will be normal for you to give your AI access to listen to all of your conversations, read your emails and scan your biometric data because the upside and convenience will be so immense.

8. Blockchain

If you haven't heard of the blockchain, I highly recommend you read up on it. You might have heard of bitcoin, which is the decentralized (global), democratized, highly secure cryptocurrency based on the blockchain. But the real innovation is the blockchain itself, a protocol that allows for secure, direct (without a middleman), digital transfers of value and assets (think money, contracts, stocks, IP). Investors like Marc Andreesen have poured tens of millions into the development and believe this is as important of an opportunity as the creation of the Internet itself.

Bottom Line: We Live in the Most Exciting Time Ever

We are living toward incredible times where the only constant is change, and the rate of change is increasing

Best Book for Writing Clean Code

While I agree with most of the answers that books are not (on their own), the best way to learn to write clean code, they are a great supplement to other things you might be doing (like reading code, getting your code reviewed, etc). If you’re anything like me, in addition to practice, you like having a broader reference where someone smart has spent a non-trivial amount of time figuring out cataloging and summarizing things. Even things that are intuitive make a lot more sense when someone has named them, structured them, etc.

Here are my favorites:

1. Uncle Bob’s Clean Code : A very opinionated take on why writing good code matters, and what constitutes good code. It clearly documents the pitfalls of what bad code can lead to, and minces no words (“[bad code will] bring an organization to its knees” and “programmers who satisfy themselves with merely working code are behaving unprofessionally”). It covers principles, patterns,

1. heuristics, and “smells”, and includes case studies so you can see, first-hand, how everything applies to real world situations. Most importantly, it helps frame your mind for what is, in my opinion, the most important part of writing good code: empathy (for others who will read your code, and even your future self). For instance, the “Boy Scout Rule” is a good principle to work by (“leave things in better state than you found them”). On the downsides, it is a bit less “structured” than Code Complete, but that didn’t bother me.
2. Code Complete : I was given a copy of this on my first day of work at Google. This is the definitive guide on writing code. The first downside, however, is its length (it’s about 900 pages long, and took me about a year to get through). It is also a bit dated. Don’t get me wrong, most of these principles are universal, but over time the software development process has adapted, and subtle tradeoffs like maintainability vs. speed can change. So I’d definitely start with Clean Code first.

It was once described to me that Code Complete is the Bible, and Clean Code is the handbook. If you’re just getting started, I’d start with the handbook.

A final note: A lot of people will point out that most of the content in these books is obvious and intuitive, but at the end of the day, a lot of times the problem isn’t not knowing, it’s not reminding. I’ve seen a lot of experienced developers (including myself) make bad trade-offs.

Best Ways to Learn Programme

                  Best ways to Learn Programming

1. CodeHS -- Personally graded, video-then-program format problems, starting with a toy language called Karel and moving up to Javascript, culminating in you making the game Breakout in your browser. Founded by two ex-CS106a TAs at Stanford from which the curriculum was largely adapted. They have probably 40 hours of really good content and, most importantly, provide you friendly, one-on-one help with like ~3 hours turnaround when you need it. Check out my version of Breakout I made after doing all of the content: EpicBreakout. (1)
2. Google's Python Class -- Unlike above, requires some set-up on your machine (i.e. you're not coding in-browser), but still good. About two days worth of lectures on Python with a handful of good problems, culminating in regular expressions (like a custom CRTL + F in a Word document) and a problem where you descramble an encoded image from a website.
3. CodingBat -- Python and Java problems. No frills, just the exercises -- probably better for someone with a little bit of background (meaning you know what a function/parameter is and can use The Google to figure out/find syntax/functions you need). The site was made by the same guy who taught the Google Python Class.
4. Khan Academy -- A few intro tutorials (mostly graphics/animation-focused) in JS using a well-regarded library (Processing.js) and then a wide-open project space for you to see programs other people have made (i.e. the end result and the code) and to make your own, potentially forking off of their work. Here's a game that some guy made that served as inspiration for my version of Breakout: Mercury Subspace. Pretty great, right?
5. Codecademy -- Solid read-then-write-code format of small problems broken into different subpieces. I used their HTML/CSS tutorials to get a basic background before making my personal website (http://www.thenickhuber.com/) and am going to use their stuff on more advanced JS and jQuery when I get to it. Still, their grader is a bit buggy and there's a large variance in course quality/overlap in material, since everything is written by different people.
6. Learn Python The Hard Way -- Read-then-implement exercises, starting from no assumed knowledge. Good, but still not as good as interactive problems; I gave up after doing ~20% or so of it because it's unapologetically repetitive, but have read lots of good reviews of it.

Other good stuff I want to check out:

1. Stanford iPhone course (all slides and assignments: http://www.stanford.edu/class/cs...) -- an iPhone app seems like such a good early project, because it's so easy to show your friends what you've made, but have to figure out how completeable it would be for me. Also, you can't get your problem sets graded if you're just working on your own from the material online.
2. K&R (http://www.amazon.com/Programmin...) -- Highly regarded intro book on C and implementations of the most canonical algorithms. (If you know of a website that tries to do something like this, would love to get it from you.)
3. The many CS courses on Coursera and Udacity. However, I think it's really important that you have someone grading your work so that you can get feedback (and that you actually do the problems rather than just watch the lectures). I'm not sure if this is possible if you take the course "off-cycle" and how good the problems are, but still worth taking a look.

After a month, I've now got a better idea of what I can make and this then informs things that I think would be cool to make. At this point, I'm most excited about continuing with this project-based learning approach as I think it's more effective/lasting/fun than more tutorials/classes, but it's still tough to get this outside of the university/work environment.

---

1. Note: it's unwinnable right now -- I need to refactor and expand it, including a bunch more powerups and the final showdown with our hero's final boss, The Brick King. FYI, my high score is like 550 and the game gets buggy at high levels. Switching to bullets helps and actually adds some unexpected difficulty. Would love to get your feedback/ideas.

A Bad Software Engineer

            Characteristics of a bad software engineer

1) The Stack Overflow bot: This person ran into an error, did a quick Google search and applied the first solution they found. The problem here is not that of copying from Stack Overflow. I think there are more solutions on Stack Overflow than any reference guide or manual. Don't get me wrong, it's a wonderful resource, if not the best. The problem is the robotic application of it without understanding the consequences. The problem is the application of it without fully understanding the context of it and whether it really applies to the current problem at hand. More often than not, I have seen people believe more of what they see on online forums than the code/system in front of them.

2) The I-am-not-a-tester: I don't need to test the code; that is the job of the testers. I don't think that even in this age of mature Agile methodologies, this attitude has waned. There is still an inertia against testing their code. Part of it comes from lacking the interest to set up a testing environment and partly from lack of coherent knowledge of testing. (Is it also partly due to an unspoken stigma against testers in the developer community.)

3) The I-hate-documentation: Some people believe that code documentation must be poetic and hence they lack the skill to do it, ergo not their job. In my opinion, these are the #1 foes of sustainable software. Good software is not software that provides a million cool features. Good software is one that has a few good features that are used consistently by many people and read/updated/modified by a thousand. This brand of developers who believes less in technical communication and precise and detailed documentation is the greatest weed to a company's success.

4) The ugly: My code works, but:

• I have variables named x, flag, str, arr, etc.
• Most of what I write is in one giant method.
• There is no indentation.
• No consistent coding convention or style.
• Global variables spewed all over the place, etc.

This is the most annoying thing for me personally. It's not the issue that the code is bad. It could potentially be the greatest piece of code written. But if a diamond necklace is buried in the debris of the Titanic, nobody will find it, and nobody will want to clean it, wear it, use it.

5) The short-term investor: He codes. He deploys. He moves on. No attempt to learn the problem. No interest in the domain. Just give this guy a piece of code, he will slog on it overnight and hand it over. You got a fix/working software. Nothing more achieved from it. Sometimes, it's important that you have certain selfishness in the developer, one who not only cares about the deadline, but also cares about what he/she got to learn from it.

6) The protester: "I didn't do this". "This looks bad". "Not my problem". "This isn't related really to my fix, but someone way over there made a mistake". "I hate this (loop this sentence 10 times a day)", "I can't fix this, get the person who made this code to fix it".
The person who coded that mistake has moved on, when will you?

7) The dictator: My way or the highway is their motto. It's their "ideas" vs "your ideas", not "project ideas". It's their solution vs your solution. I bet there will be an argument for sure. Somehow they will keep coming back to a part of code that you implemented. It somehow discomforts them even if it works, tests, and looks perfectly fine. This person is a big bottleneck to productivity and will be the first person to crumble under pressure and start pointing fingers. This person is not good for the team, however experienced/good a developer he may be.

8) The overcautious: The Java developer who just froze when he learned that he would have to write a Python script. The developer who panicked on learning that something in the registry needs changing. The developer who cringes at having to input things in the database. These people will do anything to avoid getting out of their comfort zone. They have weird superstitions related to having to touch certain parts of the system. I have learned, from personal experience, that this phenomenon is common with new developers. Good developers show a tendency to slowly/swiftly move out of their comfort zone in exploration.

9) The careless: Forgets to take a backup, snapshots, has multiple working directories of code, leaves system out, prints in production code, etc. Again, this is a newbie tendency and gets better with more professional exposure.

10) The lazy pseudo-hacker: They pride themselves at being able to trick the system into working. They find magical solutions to seemingly complex problems. My experience says that 9 out of 10 times, it's just a facade. The hack is bad and will crash sooner or later and will cost much more than having to deal with it, with extra time right now.

EDIT: Please drop in comments. Maybe we could start a new follow-up question as to how a managers/peers/colleagues could handle these cases because almost all of them can be helped to become better. A design pattern of sorts for fixing programmer smells. :-)

Life Advice

What can people start doing now that will help them a lot in 5 years.

• If you do anything, do this first one: learn how to work hard and stick with something. Learn how to turn off Facebook and control your addiction to social media. You'll instantly be ahead of a majority of your generation.
• Video games are a time sink. If you can play for an hour and say "That was fun, let's do something else" then you're ok. Otherwise, just get rid of them.
• Pick up an athletic hobby that you can do through the years, or your sedentary academic lifestyle will do horrible things to your posture, back, and gut.
• Learn how to deal with interpersonal conflicts. Read Crucial Conversations and practice - it's a lifechanger (shameless plug: Crucial Conversations Tools for Talking When Stakes Are High, Second Edition)
• Learn as much programming as you can. It's never a bad idea to learn a programming language (unless that language is COBOL—just kidding, you can even make money coding in COBOL). I've found Treehouse is worth the investment.
• Learn how to display data in R.
• Learn how to talk on the phone with people you don't know. It still terrifies most people. Get a phone sales job and quit after a few weeks.
• Start some kind of little side venture to learn entrepreneurial principles. Start a window washing business, buy and sell stuff on Craigslist, do anything. You might need them if you're in between jobs.
• Take a course on statistics and how they're misused, specifically how faulty causal arguments are made. It will change the way you approach almost any discussion, quantitative or not. (Read How to Lie with Statistics: Darrell Huff)
• Always have a private place where you can talk out loud to God every day. Even if you're not religious or don't believe in God. Talk out loud to the universe. Sort out your thoughts, verbalize them, and then write down what comes to mind. Something wiser than you is listening and responding, even if it's just another side of you.
• Use http://Mint.com to track your expenses. Make a budget and learn how to stick to it. Learn to live lean now while you can, so you won't be forced to later on.
• Learn a foreign language, but only if you anticipate using it. Sure, there are side benefits, but you'll forget it.
• Learn how to network. Read "Never Eat Alone."  Hint: it's about doing things for other people.
• Learn how to cook tasty, cheap food (If you buy one cookbook in your life, Cal Peternell: Twelve Recipes is a good one.) And make this bread. No really. http://www.steamykitchen.com/168...
• Find music that inspires you and makes you feel alive. Listen to it every morning and if it's something embarrassing just don't tell your friends about it.
• Save up a few thousand dollars and go somewhere crazy with a few friends. Live in a hostel for a few weeks. Get malaria if you have to. It will change your life and you will think about it forever (not the malaria part - you'll get over that.)
• When someone promises you easy money, run the other way. Yes, it IS a scam.
• Read a book a week (I listen to Audible.com the car). When you get ridiculously wealthy, read a book a day. Read fiction too.

What is a Full Stack developer?

Layers of the Full Stack:

1. Server, Network, and Hosting Environment.
   1. This involves understanding what can break and why, taking no resource for granted.
   2. Appropriate use of the file system, cloud storage, network resources, and an understanding of data redundancy and availability is necessary.
   3. How does the application scale given the hardware constraints?
   4. What about multi-threading and race conditions? Guess what, you won’t see those on your development machine, but they can and do happen in the real world.
   5. Full stack developers can work side by side with DevOps. The system should provide useful error messages and logging capabilities. DevOps will see the messages before you will, so make them count.
2. Data Modeling
   1. If the data model is flawed, the business logic and higher layers start to need strange (ugly) code to compensate for corner cases the data model doesn’t cover.
   2. Full stack developers know how to create a reasonably normalized relational model, complete with foreign keys, indexes, views, lookup tables, etc.
   3. Full stack developers are familiar with the concept of non-relational data stores and understand where they shine over relational data stores.
3. Business Logic
   1. The heart of the value the application provides.
   2. Solid object oriented skills are needed here.
   3. Frameworks might be needed here as well.
4. API layer / Action Layer / MVC
   1. How the outside world operates against the business logic and data model.
   2. Frameworks at this level should be used heavily.
   3. Full stack developers have the ability to write clear, consistent, simple to use interfaces. The heights to which some APIs are convoluted repel me.
5. User Interface
   1. Full stack developers: a) understand how to create a readable layout, or b) acknowledge they need help from artists and graphic designers. Either way, implementing a good visual design is key.
   2. Can include mastery of HTML5 / CSS.
   3. JavaScript is the up and coming language of the future and lots of exciting work is being done in the JavaScript world (node, backbone, knockout…)
6. User Experience
   1. Full stack developers appreciate that users just want things to work.
   2. A good system doesn’t give its users carpal tunnel syndrome or sore eyes. A full stack developer can step back and look at a process that needs 8 clicks and 3 steps, and get it down to one click.
   3. Full stack developers write useful error messages. If something breaks, be apologetic about it. Sometimes programmers inadvertently write error messages that can make people feel stupid.
7. Understanding what the customer and the business need.
   1. Now we are blurring into the line of architect, but that is too much of a hands off role.
   2. Full stack developers have a grasp of what is going on in the field when the customer uses the software. They also have a grasp of the business.

Other Pieces of the Puzzle:

1. Ability to write quality unit tests. By the way, even JavaScript can have unit tests these days.
2. Understanding of repeatable automated processes for building the application, testing it, documenting it, and deploying it at scale.
3. An awareness of security concerns is important, as each layer presents its own possible vulnerabilities.

Closing Thoughts:
It is very bad practice to tightly couple code to a specific implementation (library, OS, hardware, etc). Just because a full stack developer understands the entire spectrum doesn’t mean they have license to take shortcuts. Well, actually they do if it is a build and throw away prototype.
Technology start-ups need full stack developers for their versatility!  However, as an organization matures, it needs more and more focused skills.

 

Snapchat Parent Files for $25 Billion IPO

Snap Inc. has confidentially filed paperwork for an initial public offering that may value the popular messaging platform at as much as $25 billion, a major step toward what would be one of the highest-profile stock debuts in recent years. 

 

The company, formerly known as Snapchat, made the filing with the Securities and Exchange Commission in recent weeks, according to people familiar with the matter.
An IPO, expected as early as March, could value Snap at between $20 billion and $25 billion, one of the people said. The Wall Street Journal reported last month that the valuation could be $25 billion or more. The reason for the discrepancy isn’t clear.
If Snap pursues an IPO at the currently expected valuation, it would still be the largest U.S.-listed technology offering since Chinese e-commerce company Alibaba Group Holding Ltd. made its debut at a $168 billion valuation in 2014.

ENLARGE 

That could provide a boost for the IPO market, which has had a dismal year. Just 103 companies have listed their shares in the U.S. in 2016, raising $21.8 billion, according to data provider Dealogic. That is down from 165 deals raising $34.6 billion at the same juncture last year and marks the lowest year-to-date level for deals since 2009 and proceeds since 2010. Technology IPOs have experienced similar weakness.But bankers and investors are optimistic that a successful debut for Snap would convince other bellwether tech companies to tap the IPO market.The recent strong performance of the few tech-company shares that have started trading this year has given market participants confidence that the new-issue market is due for a rebound next year.Snap would become the first of a small batch of highly valued and closely watched venture-backed companies, such as Uber Technologies Inc., to test the public markets.The four-year-old company, whose Snapchat app lets users send disappearing messages from their smartphones, was eligible to file its IPO paperwork confidentially because it expects to have less than $1 billion in revenue this year. Under the 2012 Jumpstart Our Business Startups Act, companies with annual revenue below $1 billion have the option to file an initial draft of their IPO prospectus with regulators and make adjustments before unveiling it publicly.Morgan Stanley and Goldman Sachs Group Inc. would be lead underwriters of a Snap IPO, according to people familiar with the matter. Snap executives plan to be relatively conservative in pricing the offering, the people said. Recent tech offerings have generally been priced conservatively. The average multiple of total company value to expected sales for tech companies at their debut this year was three times, compared with 3.6 times last year and 4.9 times in 2014, according to a recent report from Deutsche Bank’s equity-capital-markets group.There is no guarantee that Snap, based in Venice, Calif., will proceed with a share sale in the time frame it currently envisions, or that it will achieve the valuation contemplated.Snap’s main source of revenue is selling ads on Snapchat that are slotted in between stories contributed by media partners and video diaries posted by the app’s users. Marketers also can buy location-based or event-based geofilters and “lenses” that add quirky characteristics to photos and videos.Snap has been working hard to win over Madison Avenue ahead of the IPO. Advertisers are intrigued by the Snapchat app, which reaches more than 150 million users daily, including 41% of 18- to 34-year-olds in the U.S., according to Nielsen.But marketers and ad agencies have been frustrated with Snap’s tight controls on ad content and the long wait times some have experience getting ads approved by the platform. Others say those problems amount to growing pains.Snap has been taking some steps to make life easier for advertisers. It released an “application programming interface” that helps advertisers buy ads through a more automated process. And it has lifted some previous restrictions, allowing marketers to target customers using email databases and other data sources.The company’s revenue has grown quickly since it started running ads in 2014. Snap told investors earlier this year that it expected revenue of between $250 million and $350 million in 2016 and as much as $1 billion in 2017.It is already ahead of the top end of its 2016 forecast, people familiar with the matter have said. In 2015, the company generated just $60 million in revenue. Snapchat loses money, according to people familiar with the matter, as it focuses on revenue growth and finding ways to make money off its big user base.In September, the company renamed itself Snap in a bid to show that its ambitions extend beyond Snapchat. As part of the change it unveiled camera-equipped sunglasses, called Spectacles, that can record video in short bursts. The foray into hardware potentially gives Snap another source of revenue, but poses new challenges such as managing inventory.

How did successful people spend their time when they were young, between the ages of 10 and 22?

All those people were accomplishing improbable things long before the world had given them permission.

Steve Jobs once called up the CEO of multinational mega-corp HP and talked himself into a summer job. He was 12. Steve later travels to India for spiritual enlightenment, drops out of college and founds Apple by age 21.

Bill Gates started a business aged 15, developing software that monitored traffic patterns, and made $20,000. He graduates scoring 1590 out of 1600 on the college SAT test, and founds Microsoft aged 22.

Elon Musk wrote a video game called Blastar aged 12, selling it for around $500. Being born in South Africa, at age 17, he decided he needed to live in the US and flew solo to Canada with no home or job, and survived doing hard labour on farms and cleaning out boilers, working his way into University aged 19 and earning two degrees in economics and physics.

Richard Branson started his first two businesses at age 16 from the crypt of a church. By age 22 he set up a music label and recording studio, where his first signed artist Mike Oldfield recorded the hit song Tubular Bells.

Before he was 21, Peter Thiel was a US Chess Master, one of the highest ranked under-21 players in the country. He also had time to found The Stanford Review aged 19.

I sure as hell don't deserve to be in the same list (well – not yet) – but I was programming aged 8, wrote my own operating system aged 16, and founded my business aged 21. I'm willing to bet that the other people you listed that I don't know had their own share of unconventional accomplishments.

It's a popular myth that you can't tell if something is going to be successful early. Certainly early success doesn't guarantee late success, and sometimes – very rarely – success can come from nowhere. But actually, most things that end well start off well. You might have looked at Elon Musk aged 18 and seen a penniless kid cleaning goop out of pipes, but his internal fortitude had already accomplished more than most would live to imagine. He was already a success – it just took a little time for reality to catch up.

So you want to know what to do between age 10 and 22? Accomplish things. Don't wait for the world. You want it to be the one doing the catching up

Mental Resilience and Success

Ok, so Navy SEALs are tough. Maybe the toughest in the world.
But why should we care? What do civilians, desk-workers, and noncombatants have to gain from more mental resilience?
A lot, actually.
With such examples as the now-famous Stanford marshmallow experiment and the concept of Grit introduced by Angela Duckworth in her bestseller of the same name, we have a good idea of how important grit (mental toughness) is for driving (and predicting) long-term success.
Turns out, the ability to stick it out when the going gets hard matters a lot. Winston Churchill famously advised, “If you are going through hell, keep going.” That’s some damn good advice.
In the soft-boiled world of today with heated toilet seats, A/C set to “freeze your ass off” and more food than we stuff our faces with, it’s no surprise that people fail at the slightest tinge of suffering.
But who cares about that.
What’s interesting to me is that, in a world full of softies, cultivating mental resilience provides an incredible advantage. By building the ability to stick it out as those around us give way, we are setting ourselves up for success.

6 Mental Toughness Techniques from the NAVY Seals

After reading my way through a handful of memoirs from assorted ex-SEALs, I’ve distilled the tips and techniques they use down to the following 6 techniques.
Each technique comes with a short explanation and a practical application to real life.

Technique #1: Eat the Elephant

 How do you eat an elephant?

One bite at a time.
Faced with a daunting task—a marathon, a pretty girl on the street, or a startup launch—we often feel the fear, freeze and stop before we have begun.
The SEALs present a solution in segmentation. Slowly divide the elephant into neatly digestible parts and… Well, you get the idea. Take your challenge one tiny step at a time. It’s cliche, but it works.
You’ll see many ultra-marathoners and triathletes doing this. They focus on the next immediate objective—the next point in the horizon—and prevent their minds from passing to the entire race.
Application: Break down any daunting task into immediate, bite-sized objectives. Ideally, they should fit into a 24-hour window. Focus only on completing one at a time. Avoid considering the whole.

Technique #2: Visualize Success

This one startled me.
In a certain study, basketball players improved their free throw accuracy by 23% from just visualizing the free throws. Players who practiced actual free throws only improved by 24%. That’s a mere 1% difference. Wow.
Good visualizations have the following qualities:

• Vivid and detailed. Engage all the senses. Imagine the particulars. Make it as real as possible.
• Repetition. Run the play-by-play over and over in your head. Make it automatic.
• Positive Imagery. Do not envision yourself failing. Instead, repeatedly envision yourself in a state of effortless success.
• Imagine Consequences. If your fortitude wanes, imagines the consequences of failure. See the faces of your friends and family when they hear the news. Envision the pain of personal embarrassment.

Application: The next time you have a big, stressful event coming up, use visualizations to imagine yourself succeeding.

Technique #3: Emotional Control

In times of great stress, a rush of our body’s main stress hormones—adrenaline, cortisol, and norepinephrine—can give us a boost of energy and focus.
However, when these hormones stay elevated for long periods, we cannot switch to relaxation mode. We have trouble sleeping, motivation tumbles and immune function takes a serious hit.
The SEALs simple solution is something called the 4 by 4 for 4:

1. Breathe in for 4 seconds
2. Breathe out for 4 seconds
3. Repeat for 4 minutes

Look familiar? This is the same kind of thing yogis have been doing for thousands of years. Our brain affects our body, and the reverse is true as well.
Use simple breathing exercises to switch off your stress hrmones and prep the body for relaxation.
Application: This helps if you do meditation already, but the next time you catch yourself feeling stressed, stop and take several deep breaths. Bestselling author Tim Ferriss recommends stopping everything and taking a simple 3 breaths before going on with your day.

Technique #4: Nonreactivity

“Men are disturbed not by things, but the view they take of them.” —Epictetus

We have more control than we think.
We can’t control what happens in our outside world, but we can control our interpretation of it.
In his book, Breaking BUD/S: How Regular Guys Can Become Navy SEALs, D.H. Xavier recalls his own “Hell Week” experience—

“They were kicking me while I was way, way down. My belief could have been that they truly didn’t want me there; the consequence of that belief would have been me quitting. Instead, my belief was that I didn’t care what they said. I believed I was capable of succeeding…”

Xavier implements something I call reframing. He takes one possible belief or world view, discards it, and selects another one. What could have been interpreted as a negative event suddenly becomes a positive one.
Application: Take an active look at how you are interpreting external events. Once you recognize it, challenge that view. Try to reframe any negative views into more positive ones. See “bad” events as a challenge for you to go out there and improve yourself.

Technique #5: Small Victories

What to do when morale is low? You lost your wallet, it’s raining, AND your wife just left you in the same day. What to do when nothing is going right and everything is going wrong?
Try to think smaller.

Every day, I write three things in my journal that I am grateful for.
Today I wrote:

1. The cool, refreshing air following a long rain.
2. The smoky satisfaction of iced coffee.
3. A smile with the barista at my local cafe.

Small victories keep morale high. And high morale feeds forward into more high morale. It creates a virtuous circle of positivity for doing good work.
Give it a shot if you haven’t tried this. It matters a lot more than you might think.

Technique #6: Find Your Tribe (and Necessity)

In his book, Tribe: On Homecoming and Belonging, Sebastian Junger writes—

“Humans don’t mind hardship, in fact they thrive on it; what they mind is not feeling necessary. Modern society has perfected the art of making people not feel necessary. It’s time for that to end.”

Junger is on to something here. We’ve all seen the tales of immense human performance in times of great need. It’s the classic “mind over body” of a mother lifting up a car to rescue her child.
We humans are social creatures. And we crave meaning in a world that sometimes seems all too meaningless.
Find both—close friends and close principles—and you have a hotbed for mental resilience.
Application: I’ll be writing more on specific techniques to do this, but spend some time thinking about what brings meaning to your life. That’s the first step to finding your tribe—your group of people that share similar vision and values.

---

Thanks for reading!

              A little sight into the UI developer works:

What is a MVC ?

the model view controller pattern is a pattern based on the names of its main parts, which are as follows.

Model: this is a domain specific representation of the information on which application operates.The model is another name for the domain layer.Domain logic adds meaning to raw data(for calculating if today is the birthday of the user ,or the taxes and shipping charges for the shopping cart).

View : renders the model into a form suitable for interaction ,typically a user interface element.MVC is often seen in web applications where the view is the HTML page and code which gathers dynamic data for the page.

Controller : Processes and responds to events ,typically user actions and invokes changes on the model and perhaps the view.

What are key tasks of a UI developer :

1-Create a web application front end as per design comps and information architecture.

2-Integrate front end application with the application business layer.

3-Follow best practices and standards for accessibility and cross browser comparability.

4-Collect feedback from design and technical staff on website development needs.

5-Stick to established coding standards and groups procedures individually and in teams.

6-Coordinate with interface design architects for meeting standards at code level.

7-Design and build UIs on any server platform in a team environment.

A user Interface developer for short is not someone who knows a bit of HTML .As developers for web we must know about HTTP and siblings ,HTML,css,JavaScript ,j query ,AJAX ,J son and multiple browsers and their differences ,tools and programmes that deal with web communications.As developers you must know about the human cognition ,basic psychology and logic sorting .You should also have good common sense and must know about all technologies offerings in accessibility and usability interaction principles , MVC platform separation ,languages for creating interfaces and generally tool kits ,tools and programmes that deal with interfaces .

        How to apply to Startup Jobs effectively 

Goal 1 :
Make a list of companies that you want to apply badly and want to be a part of it.The inspiration for this list may come from the blogs or in which field you want to make your career and news websites like Tech crunch.com or you can read about them in the quora.

Goal 2 :
make a detailed report about th company.You don't have to necessarily demonstrate a deep understanding of their product or space.Show them that how much you are interested in them and have spend a lot of time researching about them.


Search about their :

1- Traffic shares  You can use the websites like Similar-Web.com,SEMPush.com

2-Their Products and features.

3-How they evolved from starting stage over the months and years. Use Web Archive.

4-Read about their updates.What are their features added and removed in their latest updates.

5-Read about their app , if they have an android app or IOS app ,know everything about that , how it works.

6-Any recent news about them and any article about them.

7-Read about their founder and their teams.

8-Thier main competitors.

9-Use their product if its a B2B app ,make a small transaction from it and get a feel for the experience.If its B2B HR tool , sign up for free trial version.


Goal 3:

Email the Founder

The reason behind mailing the Founder directly is that if you will message the HR dept they will never read your email and it will be a part of their junk folder.
As the HR personnel get hundreds of email daily within their company and from the outside of the company also.
Don't be on their list of top 500 people.

To get email of the founder , first Google '[first name]@[company].com' and related combinations.If that doesn't works out use Email Hunter or Clear Bit.The tiers for both the services will most likely be enough to get what you need.

Content Of the Mail

[subject Line]

Experiment with unusual subject lines .For example : "do you want to hire me?"


 Open rate of these types of messages are 250percent.

   [Body]

      1. Always start by giving Context.What was your previous or recent role in the last job.Why you want to work for them.If you are a college graduate ,talk about your project.

      2.Send a link to your git hub profile and Linked In profile.If you are a front-end developer you could also send link of your Behance profile or dribble profile.

     3- Mention the recent technologies and tools you are working with.
 
     4-End with a call -to -action, prompting a response .For example "Let me know if you are interested in taking this forward." I will be happy to share more details with you or meet with you in your office! "


                             Don't forget to attach your CV!

     You want Inspiration || get it from him

Sean Parker.

1. He co-founded the revolutionary (and notorious) file-sharing service Napster and also served as the first President of Facebook. He also co-founded Plaxo, Causes and Airtime.
2. His father taught him programming on an Atari 800 when he was only seven years old.
3. As a teenager, he had been sentenced to community service when he was caught by the FBI for hacking the network of a Fortune 500 company.
4. He had interned for Mark Pincus (founder of Zynga) while he was still in high school.
5. He had won the Virginia computer science fair for developing a web crawler and was eventually recruited by the CIA.
6. By the end of his senior year of high school, Sean Parker was earning more than $80,000 a year through various projects.
7. He never went to college.
8. He created Napster along with Shawn Fanning when he was only 16 years old.
9. He is one of the board members of Spotify.
10. Parker’s father, who put his family over his entrepreneurial dreams, told Parker "if you are going to take risks, take them early before you have a family."

New JavaScript package manager

 

Facebook today launched Yarn, a new package manager for JavaScript. If you’ve every worked with JavaScript and Node.js, chances are that you’ve used the npm package manager to find and reuse existing code (or maybe publish your own libraries, too). At Facebook’s scale, though, npm didn’t quite work for the company, though, and it started developing an opinionated alternative for its internal use. Over time, the team got help from developers at Google, Exponent and Tilde.
It’s worth stressing that Yarn, which promises to even give developers that don’t work at Facebook’s scale a major performance boost, still uses the npm registry and is essentially a drop-in replacement for the npm client.
As Facebook software engineer Sebastian McKenzie and engineering manager Tom Occhino told me, the company had developed lots of internal infrastructure around npm. “But over time, as we bolted new pieces to this, we realized it didn’t work so well,” McKenzie said. So instead of hacking around npm’s limitations, Facebook decided to rewrite it from scratch.
Given that npm works well for millions of developers, why did it not work for Facebook? The team told me there were a couple of fundamental problems with npm for the company’s workflow. Performance was one of those, so Yarn does a better job at caching files locally, which ensures it doesn’t have to hit the network quiet as often as before. Yarn is also able to parallelize some of its operations, which in turn speeds up the install process for new modules, too.
At Facebook, npm slowed down the company’s continuous integration workflow. Early on, engineers had to run the ubiquitous “npm install” command manually, but that didn’t work in the sandboxed and isolated continuous integration environments the company uses for security and reliability reasons. Checking all of the modules into a repository was also inefficient because even a minor change could easily trigger massive commits. React Native, for example, currently has 68 dependencies (which themselves have their own dependencies). Once you’ve unspooled all of those, you end up with 121,358 files. That’s obviously not very efficient.
Another issue Facebook ran into was that npm is, by design, nondeterministic — yet Facebook’s engineers needed a consistent and reliable system for their DevOps workflow. Depending on the modules you have already installed, the node_modules directory that is part of every project can look very different depending on which developer’s machine you’re looking at. Yarn uses lockfiles and a deterministic install algorithm to create consistent file structures across machines.
By default, npm also allows developers who write these packages to execute other code that’s needed as part of the install process. That creates security issues, though, so Yarn does not have this feature.
As McKenzie told me, the team tried to “fix” npm for its purposes, but at the end of the day, many of the features of the existing npm client that didn’t work for Facebook were not bugs, but features. Occhino added that many of the features the team wanted to build were not the kind of changes that the npm community would’ve likely accepted.
Npm, the commercial entity that backs the npm project, is obviously aware of this new project, but given that its business model revolves more around the registry than the client, there is far less conflict here than one would initially think.
Yarn is now available on GitHub. Given that a number of other companies contributed to the project, the team decided to host it outside of Facebook’s own repository. It’s not clear what the governance model for Yarn will look like, though. “Our hope is that all of the folks who have been contributing to it so far can help us figure that out,” Occhino said.