Web site to promote and amplify communities presence with direct access to the communities - no middle man

Seniors Places

Authors: (1) Gopal Yadav, Department of Physics, Indian Institute of Technology & Chennai Mathematical Institute. Table of Links Abstract Acknowledgment PART I Chapter 1: Introduction Chapter 2: SU(3) LECs from Type IIA String Theory Chapter 3: Deconfinement Phase Transition in Thermal QCD-Like Theories at Intermediate Coupling in the Absence and Presence of Rotation Chapter 4: Conclusion and Future Outlook PART II Chapter 5: Introduction Chapter 6: Page Curves of Reissner-Nordström Black Hole in HD Gravity Chapter 7: Entanglement Entropy and Page Curve from the M-Theory Dual of Thermal QCD Above Tc at Intermediate Coupling Chapter 8: Black Hole Islands in Multi-Event Horizon Space-Times Chapter 9: Multiverse in Karch-Randall Braneworld Chapter 10: Conclusion and Future outlook APPENDIX A APPENDIX B APPENDIX C Bibliography ACKNOWLEDGMENTS I am very grateful to my supervisor, Prof. Aalok Misra, for guiding me during my Ph.D. and making me what I am today. I enjoyed all the discussions that we have together. He trained me so that I can now do independent research. Apart from the research part, I learned many things from him, which helped me in the development of my personality in real life and as a researcher. I am very fortunate to have him as my supervisor. I am very thankful to my supervisor and his family, who always treated me like a family member, and for their encouragement, appreciation, and blessings. Without all these, my Ph.D. journey would not have been so smooth and pleasant. I would like to thank the very humble members of my research committee known as “Student Research Committee (SRC)”: Prof. Tashi Nautiyal (chairperson SRC), Prof. Dibakar Roychowdhury (internal member), Prof. Sugata Gangopadhyay (external member - Department of Computer Science and Engineering, I.I.T. Roorkee) and Prof. Arnab Kundu (Saha Institute of Nuclear Physics (SINP), Kolkata, India, an external member of me as a research fellow of CSIR), for their appreciation, encouragement, valuable comments, questions and evaluating me time to time. I am very grateful to Prof. Dibakar Roychowdhury for the discussions related to the research and post-doctoral position. He always encouraged me not to get tired and never give up. I would like to thank my collaborators, my supervisor, Dr. Vikas Yadav and Mr. Nitin Joshi (Indian Institute of Technology Ropar, Punjab, India) for working on the projects and publishing the papers with me. I would like to thank my colleagues from the string theory and high energy physics group Shivam, Hemant, Jitendra, Salman, Debarshi, Pushpa, Sumit and Abhishek for the valuable discussions, comments and questions. I am very grateful to the two former students from our research group Prof. Pramod Shukla (Bose Institute, Kolkata, India) and Dr. Karunva Sil (University of Cyprus) for their very helpful suggestions and guidance to me which helped me in getting a post-doctoral position. I am very grateful to Prof. Keshav Dasgupta for the help related to academia. I would like to thank Prof. Juan Maldacena (IAS, Princeton, USA), Prof. Andreas Karch (The University of Texas, Austin, USA), Prof. Tadashi Takayanagi (YITP, Kyoto University, Kyoto, Japan), Prof. Kostas Skenderis (University of Southampton, UK), Prof. Thomas Hartman (Cornell University), Prof. Suvrat Raju (ICTS, Bangalore), Prof. David Berenstein (University of California, Santa Barbara, USA), Prof. Xi Dong (University of California, Santa Barbara, USA), Prof. Arpan Bhattacharyya (IIT Gandhinagar, India), Prof. Christoph Uhlemann (University of Oxford), Prof. Rong-Xin Miao (Sun Yat-Sen University, China), Prof. Xuanhua Wang (UCAS, Wenzhou, China), Prof. Xian-Hui Ge (Shanghai University, China), Prof. Mohsen Alishahiha (IPM, Tehran, Iran), Prof. Sanjay Siwach (BHU, India), Prof. Chethan Krishnan (IISc Bangalore) for the useful discussions and comments during my PhD. I would also like to thank Prof. Suresh Tiwari, Prof. Rudra Prakash Malik, and Prof. Bhabani Prasad Mandal from the Banaras Hindu University (BHU), India, who helped me to start my journey into the Theoretical High Energy Physics during my master’s. I would also like to thank the editors, associate editors, and referees of the Journal of High Energy Physics (JHEP), Physical Review D (PRD), Physics Letters B (PLB), and European Physical Journal C (EPJC) for their comments, criticism, etc. Those comments helped me in learning something new which was missing in my papers. I am very grateful to the organizers (including speakers and participants) of the various conferences/workshops/schools for organizing very interesting events. I enjoyed those events and learned about the many new research topics. I would like to thank the members of Indian Physics Association (IPA) Roorkee chapter. I enjoyed working with them. The members include, Prof. Akhilesh Kumar Mishra, Prof. Anjani Kumar Tiwari, Ishani, Aalok, Jaikhomba, Nifeeya, Prem Sagar, Priyanshu, Ritika, Shikha, Tsewang, Vanshaj, Vidisha. I would like to extend my gratitude to all the faculty members, staff, and to students, and postdocs in the Department of Physics at I.I.T. Roorkee for making this a memorable journey. I would like to thank my colleagues from the : Shakti, Soumya, Monika, Amarjyoti, Sonu, Pooja, Pooja, Manish, Veer and Mukesh for bearing me and making the workplace vibrant. I also thank my colleagues from the all the research scholar rooms. I thank my friends Shailesh, Rahul, Anurag, Nandeshwar, Sarvesh, Amit, Ramnivas, Shubhajit for their time to time motivation and encouragement. research scholar room 2 I am very thankful to have wonderful seniors who treated me like younger brother: Shubham, Naveen, Aalok, Dibyendu. I specially thank Prem Sagar who took care of me always during my stay at IIT Roorkee and Deepak for the wonderful company. I would like to thank Priyanka, Pooja and Jaikhomba who helped in various way during pre-synopsis and thesis submission. I am very thankful to Anil, Ramashish, Amarjyoti, Shakti and Soumya for their real life knowledge, I feel everyone should have friends like them but please don’t follow them otherwise you may get bitten at some places. I am also thankful to Shivam and Shubranshu for their valuable time and discussion on the real life issues. It was a great pleasure to have Manish, Brij Mohan, Ashutosh, Arun, Harsh, Ishitwa, Shakti at IIT Roorkee who are the alumni from BHU. I thank my friends Divya, Pavneet, Ankur, Anshu, Hemant, Anju, Rahul, Ashish, Tejaswini, Gagan, Uwais for their valuable time and discussions (on various topics) during my stay at IITR. I am very grateful to my family for their continuous support and everything. I am very grateful to my parents (Shri Shyam Narayan Yadav and Shrimati Chinta Devi) who always left me free to do what I wanted to do. I was very fortunate to learn many things about life from my grandfather (Late Shri Ghurfekan Yadav). Seeing me as “Dr. Gopal Yadav” was his dream, I think he will be very happy for me wherever he will be now. I thank my maternal uncle and aunty, “Phupha” and “Bua”, and brother in laws who always encouraged me to believe in myself and for their support. I am very fortunate to have bhaiya and bhabhi, Rinki di, Priyanka di, Shaloo, Prity, Sandip, Arvind bhaiya, Santosh bhaiya, Ravi bhaiya, Bunty, Aman, Aditya, Mahesh, Vipul, Pooja, Ranjita di, Anjali, Akriti, Ankita, Shrija, Devansh, Shreya, Shivansh, Tejas in my life. I am very grateful to my school teachers, college/university professors, and all of my gurus in various fields for educating me in various aspects of life. Education can bring changes and what I am today is the perfect example of it. This paper is under CC 4.0 license. available on arxiv

Aspects of Thermal QCD Phenomenology at Intermediate Gauge/'t Hooft Coupling: Acknowledgment 

Propose new names for software engineer levels using a transparent and standardized classification system relevant to your company. Junior, Middle, and Senior are how a Software Engineer (SWE) career looks, right? But what does this mean? Different companies have different definitions, so borders are blurred. In this article, I’m going to share with you my considerations regarding levels in and try to rethink what the path might look like. A kind of disclaimer: this is only my vision and not the ultimate truth, so I’m happy to hear your feedback. software engineering What Is Wrong With Current Levels They are polysemantic. From what I can see on the market, from my experience, and those I tracked, different companies have different definitions of Junior/Middle/Senior engineers. Some of them have even more: Staff, Principal, and Distinguished engineers to have a better expression of seniority of highly experienced individual contributors. One of the key problems with “Senior SWE” is that people with absolutely different experiences might get this title. Technically, a Senior Mobile Engineer is not the same as a Senior Frontend Engineer or a Senior Backend Engineer. There are different specializations, and in general, that would not be correct to move from SME to SBE without any downgrade, but why? Logic dictates soft skills are the same, and life experience is the same as well (because it is still the same person). Only one thing changed - the ability to solve problems. You might be an extremely experienced Mobile Developer, but you have never solved issues within a web browser, problems with distributed systems, etc. So, let me take this particular criterion as a separator between levels. The first milestone is simple problem-solving. 1. Pathfinder: Random-Way Simple Problem Solver Originally, a pathfinder was someone who found or created a path through an unexplored or wild area. This term was often used to describe explorers or scouts who ventured into unknown territories, paving the way for others to follow. They were crucial in mapping new lands and navigating through difficult terrains. Sometimes, I hear, “You have to look after Junior dev, but the Middle one is working fully on one’s own." Is that true? Not. People on the Middle level usually do not care about the wider picture of the world, so they cannot make the best decision just by design. In any way, you need to look after every developer to help to stay within the project’s range of norms and not to allow to leak of over-engineered solutions. So, Random-way Simple Problem Solver (author: RwSPS short scares me as well), a.k.a Pathfinder, is able to solve atomic problems (not decomposable in a relevant way). Think about one task that someone else prepared for Pathfinder. Would you name it Junior? Middle? It doesn’t matter because you measure the results of these guys by their ability to solve business problems. Ok, Pathfinder will solve your problems. SOMEHOW, is it just enough? It depends. If you are creating a short-living project and all tasks are straightforward, a group of pathfinders will probably be enough. But for a long-living project, you need to solve problems, especially in a simple way. Otherwise, maintenance becomes a nightmare. 2. Specialist: Simple-Way Simple Problem Solver Specialist has deep, extensive knowledge and expertise in a specific field. Specialists are highly skilled in their area, often focusing on a narrow aspect of a discipline. Simple-way Simple Problem Solver (SwSPS), a.k.a Specialist, is the next level after Pathfinder. The key difference is that have enough experience to solve simple problems predictably in a simple way. That might be a proper framework/library usage, assembling solutions from existing components. For example: Specialists If tries to handle nulls by IFs, the will use nullable types to strict nullability by design. Pathfinder Specialist If might add logging at the start and the end of every method explicitly, will just use (those who believe that AOP is unacceptable should throw tomatoes in the comments) Pathfinder Specialists Aspect Oriented Programming If might refactor ten lines of code one by one. will use IDE’s multi-cursor to introduce changes in many places simultaneously. Pathfinder Specialists With experience and seeing more and more code that works, mastering tooling Specialists will provide more reliable solutions faster. This level is limited to atomic tasks only. Sounds like the next growth point! 3. Generalist: Random-Way Complex Problem Solver Generalist solves problems by synthesizing and applying knowledge from various domains. They are often effective in dealing with new or unforeseen challenges due to their adaptable and flexible approach. What is outside of a simple problem? Other simple problems! The source of all these simple ones is one or more complex issues that software engineers have to decompose before they start working. Let’s define . a complex problem In the context of this article, is a problem that might be decomposed for the sake of improved predictability of implementation time. Also, a complex problem might consist of other complex problems that should be decomposed eventually. a complex problem The key difference between a Random-way Complex Problem Solver (Generalist) and a Simple-way Simple Problem Solver ( ) is scale. A generalist is still able to solve simple problems in a simple way, but experience relevant to complex problems is not enough to follow the same approach for complex tasks. Here are a few examples: Specialist might design a new complex system starting with microservices and ignoring the fact that the customer-facing systems have <10 unique users in total yet. Generalists might start from on-premise db instead of just relying on managed services even if requirements do not specify that need and the key motivation is past experience. Generalists Generalists might bring redundant complex technologies from the previous company, ignoring the fact that the previous and the current ones are at different stages of business maturity. Getting experience in solving complex problems, starts finding ways to quickly get simpler solutions, and it means that the next level is coming. Generalist 4. Navigator: Simple-Way Complex Problem Solver Historically, navigators were crucial on ships and aircraft. In modern contexts, the term is used in roles requiring strategic planning and direction-setting, like in project management or leadership positions in companies. Counterintuitive that solving problems in a simple way is more complex, but the nature behind this fact is ignorance. At the beginning of your path, you have a high level of unawareness about already available solutions and ready-to-go components. Sometimes, they appear while you develop your own. Simple-way Complex Problem Solvers ( ) can deeply and seamlessly dive into an unknown environment, map their experience, find a simple solution, and basically have this expectation of something available instead of reinventing the wheel. A few examples: Navigator would never start by creating a marketplace if the business is about selling things but not SaaS. Navigator would research available opportunities before planning and designing. Navigator is fine with Google Sheets + Forms to launch the business. Navigator provides relevant solutions to the current business stage. Navigator Profits of the Alternative Level Classification Relative to the classical level set, this gradation: Is in terms of specific business requirements. more transparent Is in practical tasks. measurable Does correlate with experience. Does of a particular company. align expectations Conclusion The past “Senior” job title doesn’t say anything about your real ability to solve complex problems in the new company. People should align their skills with reality and not pretend to be seniors only because they already have this title. Movement through Pathfinder -> Specialist -> Generalist -> Navigator requires constant self-educating, so don’t waste your time. And please, don’t tell me that I showed myself as Pathfinder when describing such a simple topic in such a complex classification :) Also published . here

Redefining Software Engineer Levels: A Transparent Classification System for Your Company

The Signora Neroni, the Countess De Courcy, and Mrs. Proudie Meet Each Other at Ullathorne

254 Stories To Learn About Healthcare

207 Stories To Learn About Health

183 Stories To Learn About Infographic

Typing 150+ words per minute won't help you get things done. Likely it will do the opposite. Do you notice that the most popular channels on productivity have one thing in common? They have at least one video on typing 150+ words per minute. Does it matter how fast you type or is it yet another reason to procrastinate? YouTube Nowadays every office worker needs to know how to use a computer and be keyboard proficient. Most of our jobs require critical thinking and analysis. The typing speed isn't the factor that slows down work. Usually, our brains aren't capable of processing data fast enough to keep up with our typing speed. Stephen King is one of the most prolific authors. He wrote 64 novels and he writes up to 2000 words per workday. If we assume he writes for 6 hours daily. It means he types about 340 words per hour (not per minute!). King is creative but his limit is his brain's computing power, not his typing speed. You might say that you are a developer, and you cannot relate to the most creative writers. Companies don’t hire software engineers to write code but to solve problems. The amount of written lines of code isn't the measure of your skill or impact. The companies want you to complete your tasks in the simplest and fastest fashion. If you are new to software engineering and you love your job. You might feel tempted to write everything from scratch. It is great since at the early stages of your career you should produce as much code as possible to gain experience. As you grow, you will discover that your job isn't about code itself. Most companies require product sales for revenue generation, necessitating the integration of a payment system. However, developing such systems from scratch is often impractical. Instead, companies should prioritize their core business and delegate payment processing to established providers like Stripe or Shopify, who charge a fraction of development costs. Consider the intricate nature of a customized payment system. It must incorporate fraud detection, secure credit card storage, and customer support. Creating such a system would consume months and incur millions in expenses. As you progress in your career, your mindset shifts from being a code producer to a code reducer. The goal becomes minimizing code in your project, as each line adds complexity and cost. Once a project grows, maintenance takes precedence over new features. True excellence is achieved when coding is unnecessary to solve a problem. I have worked at 7 different companies. Successful and failed startups, SMEs and enterprises. In my entire career, I have never seen a developer who could write more than 500 lines of code in a workday. Based on my observation: senior developers write between 100 and 250 lines of code per workday. Actually, junior developers write more lines of code than seniors. Since they usually receive well-planned tasks. Let’s assume you are an outlier and you write 500 lines of code per work day. Most teams restrict their line length to 80-120 characters. If we assume that an average word has 5 characters each line would have up to 16 words. 500 lines times 16 words per line sums up to 8000 words. It is four times more than Stephan King. If you are a “slow writer” and you write only 60 words per minute. It would mean you will write those 8000 words within about 2 hours. I want to emphasize one fact - it is four times more than Stephan King does during his work routine. Nowadays tools such as completely changed the coding game. You cannot type faster than an AI model. The machine will always beat you. So, your typing speed becomes even less relevant. But, it doesn’t mean that you can write with one finger. You must be keyboard proficient and be able to type without looking at your keyboard. When you reach the pace of 80-120 words per minute your job is done. Github Copilot or ChatGPT The greatest impact on your career will be learning code syntax and design patterns. How to write loops, when to use singletons and why you shouldn’t do it, dependency injection, inversion of control, facades, decorators, and so on. If you work on a new codebase the majority of the time you will write code. After working on the project with many developers you will find out that you spend more time reading code than writing. After I graduated college I moved to Vienna, Austria to start my first real job in IT. Austria is a german speaking country and they have different keyboard layout. I am used to the English international keyboard. The German keyboard layout is so different even apostrophes are in different places. The company I worked for encouraged pair programming sessions between developers. Imagine my frustration during pair programming sessions with my Austrian colleagues. When I tried to type an apostrophe and got an umlaut. About 4 years ago I moved out of Vienna. I never learned German keyboard layout but I’m glad that I never did. English is the lingua franca of programming. We should not only speak and write code in English but should use the same keyboard layout when we code together. In the end, if there are ISO standards for time and dates why shouldn’t we have one for keyboard layouts? Join me Thank you for reading. This article was . initially published on my weekly newsletter I started it in response to a younger me who felt lost and needed to find a career path on his own. Today, I am a software engineer with 10 years of experience living my best life as a digital nomad.

SENIORS PLACES

seniorsplaces.com

-- employees

Since n.d.

COMPANY RANKING

SENIORS PLACES

EVERGREEN INDEX #9372

Representing this company? Click here to claim and customize this page!

Seniors Places WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

SENIORS PLACES

seniorsplaces.com

-- employees

Since n.d.

COMPANY RANKING

SENIORS PLACES

EVERGREEN INDEX #9372

RELATED COMPANIESRANK

STORIES ABOUT SENIORS PLACES

Representing this company? Click here to claim and customize this page!

Seniors Places WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!