What is 1x.engineer ?

What is 1x.engineer ?

  • Searches Google, Duckduckgo, Bing, or wherever they like when they’re not sure what’s up.
  • Copy/pastes code snippets from Stack Overflow, Glitch, Codepen, or wherever they find answers.
  • Gives credit where credit is due.
  • Creates community and shares knowledge.
  • Spends time on things outside of engineering, like hobbies, friends, and family.
  • Has a schedule that allows them to maintain a healthy work-life balance, and respects others’ time-boundaries, too.
  • Isn’t measured by arbitrary contribution scores on any website, and doesn’t judge others for theirs either.
  • Writes code that has bugs.
  • Writes code that others can read.
  • Reads the Docs.
  • Updates the Docs.
  • Doesn’t need to be passionate about the code they write or the problems they solve, but may be.
  • Doesn’t act surprised when someone doesn’t know something.
  • Is willing and able to collaborate with others.
  • Publicly celebrates others for their wins.
  • Ask questions before providing critical feedback.
  • Gives tough feedback privately.
  • Treats others how they would like to be treated.
  • Provides code reviews and feedback to their peers that are constructive, helpful, and presented tactfully, helping their peers to grow personally and professionally.
  • Expresses appreciation for code reviews and feedback from their peers that are constructive and helpful.
  • Sometimes feels hurt by critical feedback, but doesn’t react destructively.
  • Sometimes takes short breaks to clear their head.
  • Makes mistakes from time to time, and finds growth in those mistakes.
  • Willing to admit when they’re wrong, and aren’t afraid to say “I don’t know.”
  • May or may not like writing documentation, but does it anyway for future maintainers.
  • May or may not like writing tests, but tries to learn to do so if the team or project needs it.
  • Thanks others for their time, effort, and energy.
  • Can have colorful desktop backgrounds.
  • Supports code in production, even if they did not write it.
  • Can feel like an imposter at times, and understands others may, too.
  • Believes that everyone in the room is equally as smart and capable as they are.
  • Will help level-up others, and asks for help when they need it.
  • Never stops learning, but can feel totally overwhelmed by the amount of learning there is to do.
  • Tries to keep discussions productive and lets others have their say before the team makes a decision.
  • Is willing to leave their comfort zone.
  • Contributes to the community in their own way when possible, and appreciates the ways that others contribute when they can.
  • Can be a slow coder.
  • Has productive and unproductive days.
  • Doesn’t take themselves too seriously.
  • Says, “I’ve never heard of that,” in lieu of nodding and pretending.
  • Is trustworthy.
  • Works to live, rather than living to work.
  • Sometimes loses their work.
  • Doesn’t have to have the entire codebase memorized.
  • Respects and upholds community Codes of Conduct.
  • May work from home, the office, a coffee shop, or where ever else best works for them.
  • Doesn’t hate on tools, processes, or languages that they’d rather not use, or that others are using.
  • Is not defined by the computer they’re using.
  • May decorate their laptop and workspace in any way they like, and is respectful of others’ decor (or lack thereof), too.
  • Isn’t defined by myopic Tweetstorms by clueless VCs.
  • Notice something missing from the list? 1x engineers are often humble and willing to accept Pull Requests to fix mistakes.
  • If you feel like you’ve got something that’s missing from the list, feel free to open a Pull Request against the website’s repo.

Joel’s Developer Test

Joel’s Developer Test

Do you use source control?
Can you make a build in one step?
Do you make daily builds?
Do you have a bug database?
Do you fix bugs before writing new code?
Do you have an up-to-date schedule?
Do you have a spec?
Do programmers have quiet working conditions?
Do you use the best tools money can buy?
Do you have testers?
Do new candidates write code during their interview?
Do you do hallway usability testing?

Rob Pike’s 5 Rules of Programming

Rob Pike’s 5 Rules of Programming

Rule 1. You can’t tell where a program is going to spend its time. Bottlenecks occur in surprising places, so don’t try to second guess and put in a speed hack until you’ve proven that’s where the bottleneck is.

Rule 2. Measure. Don’t tune for speed until you’ve measured, and even then don’t unless one part of the code overwhelms the rest.

Rule 3. Fancy algorithms are slow when n is small, and n is usually small. Fancy algorithms have big constants. Until you know that n is frequently going to be big, don’t get fancy. (Even if n does get big, use Rule 2 first.)

Rule 4. Fancy algorithms are buggier than simple ones, and they’re much harder to implement. Use simple algorithms as well as simple data structures.

Rule 5. Data dominates. If you’ve chosen the right data structures and organized things well, the algorithms will almost always be self-evident. Data structures, not algorithms, are central to programming.

Pike’s rules 1 and 2 restate Tony Hoare’s famous maxim “Premature optimization is the root of all evil.” Ken Thompson rephrased Pike’s rules 3 and 4 as “When in doubt, use brute force.”.

Rules 3 and 4 are instances of the design philosophy KISS.

Rule 5 was previously stated by Fred Brooks in The Mythical Man-Month. Rule 5 is often shortened to “write stupid code that uses smart objects”.

Employee Work Together and Stay Together. Stop spreading COVID19 to your families

COVID19 Pandemic spread is now something that everybody talks about, Also enforcing lockdown for a long period will neither help the individuals nor the government. We have to find some ways to Prevent COVID19 spread and as well as run our operations on a daily basis. This will help the economy of the individuals. If individuals prosper, the state prosper, if the state prosper, the whole country and subsequently the whole world will prosper.


There are Workforce that can’t work from home, they should come to work regularly. For example Govt. employees, Banking Officials, Corporation Office employees, and other important private sectors. Yea I do agree that all corporates take all measures like using IR Thermometers, Sanitiser at the doorstep entries etc. But COVID Virus being Asymptomatic, its hard to detect and by the time it is detected.

Can’t stay back at home:

From the employee standpoint and from the employer standpoint, its totally unavoidable to stay at home this might not be a great idea as well. Now, lets say the some of the employee has few elderly people at his home, who are potential risk. Now they hesitate to come to work considering being contracted and they could eventually spread to their loved ones.

Is workplace that risk of being contracted ?

When considering the following situations, the workplace seem serious threat.

  • Being a field workers, covid19 frontline warriors you can easily get infected by the virus.
  • There are 20 – 50 people are coming from 50 different locations.
  • Every minute the Virus spreads in every possible directions. As a consequence everyday new places are getting impacted. Many new cases are coming up everyday.
  • Also since COVID 19 is air borne, meaning it travels by air. As you commute to the office on a day today basis. Its quite possible that anybody can get contracted as they commute.
  • More chances are if you are utilising a public vehicle like cab or taxi, there are much more chances.
  • Field workers who go out daily like municipal workers, govt. servants, health officials have high risk of getting contracted.

Does Work From Home works for everyone?

For most of the information technology and related organisations, yes work from home makes sense. But there are lots of sector for which Work From Home does not work as we expect.

Following Sectors can’t operate in Remote mode ( Work From Home )

  • Health workers
  • Field officers who are constantly on the field visits.
  • Govt. Servants who work in Post Office, Banks.
  • Logistics: You need lots of people to execute movements of objects from Point A to Point B. You need people to be in warehouse to receive the incoming materials, sort it and move it accordingly.
  • Infrastructure: We need a huge workforce to construct a building that starts from an engineer to the mason and helpers and so on.

What is the solution ?

Serving your profession at this odd time can’t be ignored. At the same time balancing both Profession & Safety for the family is important. You can’t compromise one for other, rather you have to balance both together.

Current Mode of Operation:

Consider our illustration. Let us assume an organisation has four persons working as P1, P2, P3, P4. and P1 has two kids K1, and K2. and Elderly person E1, and E2. Likewise other employes P2, P3, P4 has their own families, Please follow the fig-1.

Everyday starts like this, everyone will come to office or goes to field work. If one person say P2 is contracted on his way to office. He has great chance to spread it to others, despite all the safety precautions.

Now all the Person in the office P1, P3, P4 will get contracted easily, the worst part is these people will take it to their home and spread it to others. This is the biggest trouble, these persons / employees spread it to the home where elderly people live with them.

Isolate all employees in a Stay Together Home,Move all employees

Yea, Move all your employees, workers in an organisation to one totally isolated apartment or location, to stay. They should be working at office and they should stay there only, in COVID19 Corporate Home. Everyone should be allotted Individual Bedroom with washroom / toilet attached. There may be separate apartments for male and female to avoid new office romances sprouting up.

This can be their schedule: lets say if the employees are working for a week, starting on 10th August 2020 to 15th August 2020, They should be put in “Work Together, Stay Together” from 10th August 2020 – 15th august 2020 + 14 days. So its Number of days you are working plus 14 days.

Wow, Benefits are So many: Employees may get sick, but none of their family can get sick.

  • No family members will be infected.
  • All elderly people will be saved.
  • It might incur additional cost to the organisation, when comparing the tradeoff with the productivity and efficient operation of the organisation, this would be close to negligible.
  • With this Safe procedure in place, All family members of the employees can be saved without.
  • Lots of death can be prevented.
  • Every individual can go to work happily without the fear of risking the lives of their family.
  • Employees in the middle age group can get sick and recover without impacting the lives of their loved ones.
  • Employees also will easily co-operate for this Safe Procedure.
  • This can be given to the employees as an option, if the employee have any elderly persons, they can opt in for this “Work Together, Stay Together”
  • This “Work Together, Stay Together” will be applicable for organisation of any size, and any sectors For eg: Large corporations can take multiple isolated huge apartments or flats, or they can make temporary fabrication of a large marriage halls.

Thank You

If at least 10 families are saved adopting this procedure, I would be happy and grateful to you. Share this with your friends, families and so on till. Share this with your employers or at least with your ex-colleagues.

If you would like to add any other suggestions or strategies, please do mention on this. Or if you find any flaws in this, please do raise it on the comments below.

Lets make India COVID19 free India.