My woodburner arrives today and I'm looking for some suitable materials to test it on. Can anyone share links to items they have ordered from Amazon UK that are of decent quality but not too expensive?
There is so much stuff on there and I don't know what is good or rubbish. I don't want to spend a fortune since I will need to practice first, but I obviously don't want to order materials that aren't fit for purpose.
Any help would be appreciated!

TLDR: I (f/25) am tied between my ex (m/35) and true love (m/56)
This isn’t an easy one. Both of the men I’ll talk about are very committed and devoted to me.
The first guy let’s call him Kevin - Kevin (m/35) and I were together for 10 months before I broke up with him, we’ve left the no contact period and talking again.
The pros:
He is devoted hardworking and had all the values I wanted in a man I’d start a family with: Family-orientated, hardworking, good career (earns 5k per month) he made me feel feminine and was the typical problem-solver kind of man always ready to fix anything that felt wrong. To start a family with him makes sense - we have an age gap as well so if I went with him we’d be ready to buy a house next year and start a family which for my age in our economy (England) is quite amazing! My mum also lovers him.
The cons:
He was very controlling, neurotic, and jealous if I ever went out without texting him (which I usually did) he would overreact and make me feel guilty for something I’d never done aka feel like a cheating whore. He always had something bad to say about my friends and my clothes even though when confronted he said he didn’t mean these things badly he just saw ways of how things could be ‘better’. I eventually understood that his behaviour simply came from the fact that he has a tendency to be very negative and insecure which he projects to those he loves. I broke up with him a few months ago and after our no contact period we met every week or so and I notice he’s changed. He’s not so much on his judgemental and critical high-horse anymore and I feel a lot more respected. We are thinking of going away for a week to test if we can work.
Guy 2 is also older, many of you would’ve assumed HE would’ve been the controlling jealous possessive one but he never was. I met…let’s call him Jay. I met Jay online when I was 22, I had always had a teacher student fantasy and his wisdom and age really drew me in. We started a casual thing and met up sporadically a few times per month but messaged each other every single day. What started off as just a fling started to become quite special. I realised I’d never connected to anyone like I did to him in my life and the love we shared was nothing I’d ever experience and still to this day have ever experienced. He was very romantic and wrote me poems and songs and was extremely devoted to me to the point of crying whenever I cried and wanted my happiness to be the focal point of all of our meet ups.
The pros:
We have the same values: honesty, spirituality, empathy, self-exploration, open-mindedness and he is the most gentle kind person I’ve ever met. I’m quite empathetic and compassionate and he’s really only person who I’ve met to radiate on the same level with me. We are both creative musical and open people so our interests have always alligned. Once I realised we were getting closer and I said we should stop talking but since 22 until I met my ex, we were on and off for 2 years because it was just really hard not to talk again, we were never officially though I gave my heart more to him than Kevin. There’s no one I’d want to start a family more with than him, our children would be raised on love and tender devotion.
The cons:
With the age gap all the issues would come when he retired. If we started a family say when I was 30 he’d be 61 and once he retired the family would have to depend on my sole salary, to add onto that I’d have to be a carer not only for my kids but him too and have to live with the reality of most likely losing him when I would be 50 and him 80. Not only that but my kid(s) would be out the house by then so I’d be left alone caring for him and also my parents (who are actually younger than him) my mum has a life long disease so I’ve been raised to be more responsible than others Im also the oldest of my siblings they’re 10 and 15 years younger than me so my tween and teen years were spent basically being a love in babysitter and housekeeper. A lifetime of taking on a caring role for both my partner, my mum, my dad when he’s old too my children AND having had to also deal with being the oldest and looking after my siblings growing up just feels quite entrapping to be honest.
To add I’m aware I have a thing for older men and I love the protection I feel from them but would you think it’s best to leave these two men completely and try and find someone closer to my age? My biological dad left when I was young but my new ‘dad’ married my mum before I was 5 and actually adopted me so I’ve always had a father figure BUT perhaps there’s some strange fixation to older guys going on and that’s why I’m so tied between these two?
Lastly to add with Kevin I’d have a very functional relationship, be in a nice house and he always talked about me being a stay at home mum which he though was a dutiful role (many young girls dream of this but I actually find that the money I make per month now is enough for a good life and I doubt he’d be able to give me the same amount if I stayed at home (maybe though as he does earn 5k per month)…I also hate the idea of being dependent on him for money knowing how much he likes control) he can be very respectful in every sense other than when he’s feeling negative and seems to pick apart everything wrong about life, himself, the day and worst ‘me’ he’s the typical ‘Virgo’ and ‘Scorpio’ kind of man and very dominant assertive and not necessarily the most agreeable person but I’m the only person that truly softens him down. He also gets anxious quite easily and has insomnia but when I’m in his life that’s the happiest he is.
With Jay, I’d live quite a romantic life full of softness and airy fairy love and fluffy relationship vibes. But he’s also quite forgetful, disorganised and a bit of a last minute person that’s late to everything (so me but to the next level) he has in the past had trouble remembering to pay bills which also makes me worry that family life together won’t just have issues at the end when he’s aging but from the beginning plus he doesn’t own a house or car and seems to always prefers living in council flats despite now earning over 60k now (also to mention when we were talking he moved into a nicer neighbourhood to try and win me over but after we stopped talking he moved back into a council flat). Jay wants to start taking again but said he doesn’t want what happened last year to happen where I say I’ve found someone closer to my age and disappear.
Perhaps I should do the week together test with Kevin and make a decision then do a week together with Jay? Let me know what you think? Choose the guy I get on we’ll with looks good on paper (and very handsome) could start a successful functional family with but also know that he has controlling tendencies or choose the guy that’s 30 years my senior basically my soulmate but practically a future and family together may be extremely overwhelming both financially and emotionally.
I guess it’s also good to mention what I myself want and value, I want a family before 30 but also want to travel and start a side huddle before I have them. I value empathy and kindness a lot but I’m also the type of girl that needs security in my man, I need him to be my rock, and not just provide security emotionally but financially too, I need to feel like he can be someone I can depend on and know will fix things when the chips are down, masculinity is a big one for me.

MBBS in Georgia: Overview

MBBS in Georgia is a popular course among Indian students who want to pursue a career in the field of medicine. Georgia has become a popular destination for Indian students to pursue MBBS abroad due to its quality education, affordable fees, and English medium of instruction.
Here are some key things you should know if you're interested in pursuing MBBS in Georgia as an Indian student in 2023-24:

1. Eligibility criteria: To be eligible for MBBS in Georgia, Indian students must have completed 10+2 with Physics, Chemistry, and Biology as their main subjects. They should also have a minimum aggregate score of 50% in these subjects.
2. Entrance exams: Students must also clear the National Eligibility cum Entrance Test (NEET) in order to be eligible to study MBBS in Georgia.
3. Admission process: Students can apply directly to the universities in Georgia that offer MBBS courses. The admission process generally involves filling out an application form and submitting academic transcripts and NEET scores. MBBS without NEET is not valid in Georgia
4. Course duration: The duration of the MBBS course in Georgia is six years, which includes five years of academic study and one year of internship.
5. Language requirements: While the medium of instruction is English, students may be required to learn Georgian or Russian as a part of their curriculum.
6. Cost of education: The MBBS in Georgia fees is comparatively lower than in other countries like the USA or UK. The fees for the entire course may range between USD 25,000 to USD 35,000, depending on the university.
7. Visa and accommodation: Indian students require a student visa to study in Georgia. They must also arrange for their own accommodation, which can be either on-campus or off-campus.
8. Recognition of degree: The MBBS degree from Georgia is recognized by the Medical Council of India (MCI) and other international medical councils, which allows graduates to practice medicine in India and other countries.

Overall, pursuing MBBS in Georgia can be a good option for Indian students looking for affordable and quality medical education abroad. However, it is important to research and compares different universities before making a decision.

Test Innovators is updating our SAT practice platform for the New Digital SAT.

So, had been exploring to appear for PMP and had posted my "How to and where to start" question here roughly about 4 months ago and today I was able to get certified 3AT !
I got really serious from February 2023 and had started with AR. One has to give it to him for the ease and comfort with which he makes us fall in love with the concepts. The quiz questions at the end of each chapter were extremely tailored to his course cadence - not to expect the same in Realtime exam.
David Mclachlan Agile and PMBOK 7 videos on YT. Questions in the exam were extremely similar to the ones discussed in his videos.
I purchased study hall essentials with 7 days to go for the exam with 4 working days in between. Couldn't harness its features completely but I felt that Questions were difficult in SH causing extreme frustration and demotivating at times. I discarded the practice series midway and couldn't complete the Practice Exams as well due to lack of time and also demotivating results in the attempted practice tests. Pro tip - if you are somewhere in the same boat, take solace from this post that things are still good and not out of control
Purchased fellow member u/third3rock Study guide based on reviews in this sub. This is a priceless resource and a great TL:DR savings tons of time and effort in curating a nice summary. Thank you bro for helping at thr time of need. Folks, do consider supporting him as in my case,it proved to be a game changer.
At the exam, I opted to attend in a Pearson Vue center.

1. The check in process was streamlined and quick. No surprises there. One suggestion is to go more than 30 minutes before as you are handled in the order in which you arrive at the location. First in , more quicker check in before the queue piles up.
   
2. Do take breaks as you need the energy to calm down after each session. All 3 sessions had 60 questions of same rhytm/cadence. It was like taking 3 mock tests one after the other
   
3. Payback time - That feeling of seeing the message after submitting - dedicating to the wonderful people to this sub and the resources mentioned above. After window shopping for about 1.5 years, this sub and the resources above made the actual difference. Cannot thank you enough. If I can, anybody can. Let me know if I can assist you in providing my experience.
   

Vashikaran Mantra To Convince Parents Baba Ji, +91-7300250825 >>> future spouse prediction calculator free Numerology can be used to predict a future husband. By using the date of birth and name, you can find out information about your future husband.
Numerology can be used to predict your future husband! By using your birth date and the numerology of your name, you can find out which numbers are associated with your future husband. You can then use these numbers to find out what his name and personality will be like. future husband prediction by date of birth free
If you’re curious about who your future husband might be, you might want to try numerology. By looking at your birth date and analyzing the numbers associated with it, numerology can give you some insight into your future spouse. Here’s how to use numerology to predict your future husband’s name.

Numerology: Predicting Your Future Husband’s Identity

Introduction:

Can numerology really reveal who your future husband will be? Some people swear by the accuracy of this ancient practice, while others remain skeptical. If you’re curious about what numerology has to say about your future spouse, read on to find out more. future spouse prediction calculator

Table of Contents:

• 1. What is Numerology?
• 2. How is a Person’s Future Husband Predicted Using Numerology?
• 3. What Does the Predicted Future Husband’s Name Mean?
• 4. What Are the Chances of the Prediction Being Accurate?
• 5. Conclusion

1. What is Numerology?

Numerology is the study of numbers and their mystical meanings. Proponents of numerology believe that numbers can be used to unlock the secrets of the universe and better understand our lives. Numerology has been used for centuries, with some believing that it can be used to predict future events.

2. How is a Person’s Future Husband Predicted Using Numerology?

There are a few different methods that can be used to predict a person’s future husband using numerology. One common method is to add up the numbers in a person’s birth date. This number is then reduced to a single digit, which is said to be that person’s “life path number.” The life path number is said to represent a person’s journey through life and can be used to make predictions about their future. future spouse prediction calculator

3. What Does the Predicted Future Husband’s Name Mean?

Another way to predict a person’s future husband using numerology is to analyze the meaning of their name. Each letter in a person’s name is said to correspond to a certain number. By adding up the numbers associated with each letter of a person’s name, a “numerology number” can be calculated. This number is said to reveal certain aspects of a person’s personality. future husband prediction by date of birth free

4. What Are the Chances of the Prediction Being Accurate?

There is no scientific evidence to support the claims of numerology. As such, it is difficult to say how accurate the predictions made by numerology are. Some people swear by the accuracy of numerology, while others remain skeptical. If you’re curious about what numerology has to say about your future husband, it is ultimately up to you to decide whether or not to believe the predictions.

5. Conclusion

Numerology is an ancient practice that some believe can be used to predict future events. There are a few different methods that can be used to predict a person’s future husband using numerology. However, there is no scientific evidence to support the claims of numerology. Ultimately, it is up to you to decide whether or not to believe the predictions made by numerology.
future spouse prediction by date of birth and time According to this blog article, you can predict your future spouse’s characteristics by their date of birth and time. For example, if your future spouse was born on a Wednesday at 9:00 am, they will be hardworking and methodical. If they were born on a Thursday at 12:00 pm, they will be fun-loving and spontaneous. future spouse prediction calculator
In this blog article, the author discusses how to predict your future spouse by date of birth and time. The author provides a step-by-step guide on how to do this, and includes a few helpful tips along the way.
In this blog article, the author describes how to predict your future spouse by date of birth and time. They claim that this method is over 80% accurate, and provide instructions on how to do the calculation.

How to Predict Your Future Spouse’s Date of Birth and Time

Introduction:

Are you curious about who your future spouse might be? Well, you’re not alone. Many people want to know what the future holds for them, especially when it comes to love and relationships.
There are many ways to predict your future spouse’s date of birth and time. Some people use astrology, while others use numerology. There are even some people who believe that you can predict this information simply by looking at your birth date and time.
No matter what method you choose, predicting your future spouse’s date of birth and time can be a fun way to get a glimpse into your future love life.
free online future husband prediction Are you curious to know who your future husband will be? If so, you may be interested in trying out a free online future husband prediction. There are a number of websites that offer this service, and it can be fun to see what they have to say about your future spouse. Keep in mind, however, that these predictions are for entertainment purposes only and should not be taken too seriously.

Do you want to know who your future husband will be? Take this quiz to find out!

Are you curious about who your future husband will be? If so, you may be interested in taking a free online future husband prediction test. While these tests are not always accurate, they can give you a general idea of who you may be compatible with in the future. If you are interested in taking a test, simply search for “free online future husband prediction” in your favorite search engine. future spouse prediction by date of birth and time

How to Predict Your Future Husband for Free Online

Introduction:
If you’re curious about who you’ll marry one day, there are a few things you can do to try and predict your future husband. You can look at your astrological chart to see if you have any planetary alignments that could indicate who you’ll be attracted to. You can also look at your numerology to see if your birth date has any clues about your future spouse. And, of course, you can always consult a psychic or tarot card reader for their opinion!
There are also a few fun, free online quizzes and games that purport to be able to tell you who your future husband will be. These are mostly for entertainment purposes only, but they can be fun to do with your friends. So why not give them a try? future spouse prediction by date of birth and time

Table of Contents:

• 1. How to Predict Your Future Husband for Free Online
• 2. Astrological Clues About Your Future Husband
• 3. Numerology and Your Future Husband
• 4. Psychics, Tarot Readers, and Your Future Husband
• 5. Fun and Free Online Future Husband Prediction Games

When it comes to finding out who our future husband will be, there are a lot of us who rely on predictions. Whether it’s from a fortune teller, a psychic, or even just a simple online quiz, we want to know who the man of our dreams is going to be. And while there’s no guarantee that any prediction is 100% accurate, it can be fun to see what the future might hold for us.
If you’re curious about who your future husband might be, why not take a free online quiz? There are a lot of different quizzes out there, so you can definitely find one that suits your interests. Plus, it’s always fun to see what the results say. Who knows, you might just be surprised by who your future husband turns out to be!

future husband prediction by numerology

Are you curious about who your future husband will be? Do you want to know what he’ll be like, and how you two will get along? If so, you’re in luck! There’s now a free online future husband prediction tool that can give you some insight into your future love life.
To use the tool, simply enter some basic information about yourself, such as your name, birth date, and zodiac sign. Then, the tool will generate a prediction for who your future husband will be. The prediction will include some basic information about him, such as his name, age, and what he does for a living. future spouse prediction by date of birth and time
Of course, this tool is just for fun and should not be taken too seriously. But it can be a fun way to get a glimpse into your future and see what your husband might be like. So why not give it a try? Who knows, you might just be surprised by what you find out!

Definitions
Acqui-Hire: When a company acquires another company with the intention of gaining access to their human capital and talent profile
Anti-Dilution Clause: It allows the investors to maintain their ownership percentages in the event that new shares are issued
Arbitrage: It is the simultaneous purchase and sale of the same or similar asset in different markets in order to profit from tiny differences in the asset's listed price
Average Selling Price: The average price at which a particular product or commodity is sold across channels or markets
Bad Debt: It is the term used for any loans or outstanding balances that a business deems uncollectible
Beta Testing: It is a type of user acceptance testing where the product team gives a nearly finished product to a group of target users to evaluate product performance in the real world
Black Swan Event: It is a metaphor describing a rare, unexpected phenomenon with a low probability of occurrence, yet has a significant impact on society as a whole
Blockchain: A decentralised digital ledger of transactions maintained by a network of computers in a way that makes it difficult to hack or alter
CapEx - Capital Expenditure: It is the money spent by a company to buy, maintain, or improve its fixed assets such as property, buildings, equipment, etc
CCD - Compulsory Convertible Debentures: Instruments which are recognised as debt initially till they are converted mandatorily in equity shares of the company
Commoditisation: It is the process by which products or services become inseparable from competing offerings over a particular period. Price becomes the only distinguishing factor
Content Seeding: It is a strategy in which content creators plant a brand's content across various platforms to reach their target audience and attract leads
Credit Period: The time given to the customer to make the payment for the goods or services purchased
Convertible Debt: A type of financing that gives investors the option to convert their debt into equity in a company at a future date
Cottage Industry: It is a small manufacturing operation and is often run out of a home by a single individual or family
Debt Leverage: The use of debt (borrowed capital) in order to undertake an investment or project
Docked Bicycle: It refers to a bicycle that is designed to be locked or secured from unauthorized use by being locked or secured to a dock, rack, sharing station, etc.
Dock-less Bicycles: Instead of docks, these bikes are secured using locks that are built onto the frame.
Typically, an app is needed to gain access to these bicycles
Down-round: A scenario where the value of a business at a time of investment is below the value of the same business during a previous period or financing round
Fill Rate: It is the percentage of customer order demand that is met
First Principles Thinking: It is a means to challenge assumptions and solve complex problems by breaking them down into their most basic elements and reassembling them from the ground up
Freeze Drying: It is a low temperature dehydration process that involves freezing the product and lowering pressure, removing the ice by sublimation
Funding Winter: It refers to a period of market correction in capital inflow which lowers the probability of startups getting higher valuations in the short to mid term
Geofencing: It refers to creating a virtual geographical boundary that triggers an action to a mobile device when a user enters or exits that boundary
GMV - Gross Merchandise Value: A business metric commonly used in ecommerce which measures the total value of sales over a certain period of time
Hub and Spoke Model: A distribution model used to disperse inventory to multiple fulfilment centres from a large distribution centre
If Else Statement: In programming, it is a conditional statement that runs a different set of statements depending on whether an expression is true or false
Incineration: Destruction of something, especially waste material, by burning
Inflection Point: A key event that dramatically changes the trajectory of a business, industry, or economy
Institutionalisation: It is the action of establishing something as a convention or norm in an organization or culture
Intercropping: The practice of growing two or more crops in proximity
Jagriti Yatra: A 15 days train journey that brings together youth from all across the globe to encourage entrepreneurship in India
Lead to Sale Conversion Rate: It is a metric that measures how effective the sales team is at converting a prospective customer, called a lead, into a paying customer
Listing Fees: It is the amount of money a company pays a retailer to appear on the shelves
Loan Underwriting: It is the process by which the lender decides whether an applicant is creditworthy and should receive a loan
Markup: It is a percentage that is added to the cost of a product to determine its selling price, in order to cover costs and provide profit
MAU - Monthly Active Users: The number of unique users who engage with an app or website within a predefined 30-day period
Moat: A distinct competitive advantage that helps the company protect its market share
Mulch: A protective covering (as of sawdust, compost, or paper) spread or left on the ground to reduce evaporation, maintain even soil temperature, prevent erosion, control weeds and enrich the soil
Nudge: A nudge is a contextual push notification that is aimed at deriving action from receivers
Omni-channel: It describes a business strategy that aims to provide a seamless shopping experience across all channels, including in store, mobile, and online
Operating Lease: It is a contract for a company to use an asset and return it in a similar condition to the lessor
Operating Profit: It is the total income a company generates from sales after paying off all operating expenses, such as rent, employee payroll, equipment and inventory costs. It excludes gains or losses from interest, taxes and investments
Payback Period: It refers to the time required to recoup the funds expended in an investment, or to reach break-even point
Pharmaceutical Grade Sugar: It is the more pure form of sugar that may not contain sulphur and heavy toxic material like lead arsenic and mercury etc. It is used mainly in preparation of pharmaceuticals and food products
Proctoring: To watch people taking an exam in order to check that they do not cheat
Protective Farming: It is a practice of preventing the crop from different agents including pests, weeds, plant diseases, and other organisms that cause damage to the agricultural crops
Realised Revenue: It is revenue that the company already has received
Receivables: Amount owed to a firm by its customers for goods or services used or delivered but not yet paid for
Reverse logistics: The supply chain process of returning products from end users back through the supply chain to either the retailer or manufacturer
Risk Return Ratio: A measure of return in terms of risk for a specific time period
ROFR - Right of First Refusal: It is a right in a contract that gives shareholders the opportunity of matching the price at which a third party has agreed to buy shares from existing investors or founders
SEO - Search Engine Optimisation: The process of improving the quality and quantity of website traffic to a website or a web page from search engines
Secondary Sale of Shares: It is the sale of shares of a private company by an existing investor to a third party that does not occur in connection to the acquisition of the company
SOP - Standard Operating Procedure: A set of written instructions that describes the step-by-step process that must be taken to properly perform a routine
Sunk Cost: Money that has already been spent and cannot be recovered
Table Turnover Rate: It measures the amount of time a party occupies a table over a specific period of time
Take-Rate: It is the fee charged by a marketplace on a transaction performed by a third-party seller or service provider
Term Sheet: A non-binding agreement outlining the basic terms and conditions under which an investment will be made
Throughput: It is the amount of a product or service that a company can produce and deliver to a client within a specified period of time
Trademark: A special symbol, design or name that a company puts on its products and that cannot be used by any other company
Valuation Floor: It sets the minimum possible valuation at which the convertible note derives its conversion price
Viral Coefficient: The number of new consumers or customers that are generated by an existing satisfied customer
Web 3.0: It is the concept of the next generation of the web, in which most users will be connected via a decentralised network and have access to their own data
White Labelling: When a company buys its product or service from another company and rebrands it as their own
Y2K Bug - Year 2000 Bug: A computer flaw, or bug, that may have caused problems when dealing with dates beyond December 31, 1999
Acronyms
FBA: Fulfillment by Amazon
GSM: Grams per Square Metre
КРО: Knowledge Process Outsourcing
OTA: Online Travel Agency
LTV: Lifetime Value

Definitions
Acqui-Hire: When a company acquires another company with the intention of gaining access to their human capital and talent profile
Anti-Dilution Clause: It allows the investors to maintain their ownership percentages in the event that new shares are issued
Arbitrage: It is the simultaneous purchase and sale of the same or similar asset in different markets in order to profit from tiny differences in the asset's listed price
Average Selling Price: The average price at which a particular product or commodity is sold across channels or markets
Bad Debt: It is the term used for any loans or outstanding balances that a business deems uncollectible
Beta Testing: It is a type of user acceptance testing where the product team gives a nearly finished product to a group of target users to evaluate product performance in the real world
Black Swan Event: It is a metaphor describing a rare, unexpected phenomenon with a low probability of occurrence, yet has a significant impact on society as a whole
Blockchain: A decentralised digital ledger of transactions maintained by a network of computers in a way that makes it difficult to hack or alter
CapEx - Capital Expenditure: It is the money spent by a company to buy, maintain, or improve its fixed assets such as property, buildings, equipment, etc
CCD - Compulsory Convertible Debentures: Instruments which are recognised as debt initially till they are converted mandatorily in equity shares of the company
Commoditisation: It is the process by which products or services become inseparable from competing offerings over a particular period. Price becomes the only distinguishing factor
Content Seeding: It is a strategy in which content creators plant a brand's content across various platforms to reach their target audience and attract leads
Credit Period: The time given to the customer to make the payment for the goods or services purchased
Convertible Debt: A type of financing that gives investors the option to convert their debt into equity in a company at a future date
Cottage Industry: It is a small manufacturing operation and is often run out of a home by a single individual or family
Debt Leverage: The use of debt (borrowed capital) in order to undertake an investment or project
Docked Bicycle: It refers to a bicycle that is designed to be locked or secured from unauthorized use by being locked or secured to a dock, rack, sharing station, etc.
Dock-less Bicycles: Instead of docks, these bikes are secured using locks that are built onto the frame.
Typically, an app is needed to gain access to these bicycles
Down-round: A scenario where the value of a business at a time of investment is below the value of the same business during a previous period or financing round
Fill Rate: It is the percentage of customer order demand that is met
First Principles Thinking: It is a means to challenge assumptions and solve complex problems by breaking them down into their most basic elements and reassembling them from the ground up
Freeze Drying: It is a low temperature dehydration process that involves freezing the product and lowering pressure, removing the ice by sublimation
Funding Winter: It refers to a period of market correction in capital inflow which lowers the probability of startups getting higher valuations in the short to mid term
Geofencing: It refers to creating a virtual geographical boundary that triggers an action to a mobile device when a user enters or exits that boundary
GMV - Gross Merchandise Value: A business metric commonly used in ecommerce which measures the total value of sales over a certain period of time
Hub and Spoke Model: A distribution model used to disperse inventory to multiple fulfilment centres from a large distribution centre
If Else Statement: In programming, it is a conditional statement that runs a different set of statements depending on whether an expression is true or false
Incineration: Destruction of something, especially waste material, by burning
Inflection Point: A key event that dramatically changes the trajectory of a business, industry, or economy
Institutionalisation: It is the action of establishing something as a convention or norm in an organization or culture
Intercropping: The practice of growing two or more crops in proximity
Jagriti Yatra: A 15 days train journey that brings together youth from all across the globe to encourage entrepreneurship in India
Lead to Sale Conversion Rate: It is a metric that measures how effective the sales team is at converting a prospective customer, called a lead, into a paying customer
Listing Fees: It is the amount of money a company pays a retailer to appear on the shelves
Loan Underwriting: It is the process by which the lender decides whether an applicant is creditworthy and should receive a loan
Markup: It is a percentage that is added to the cost of a product to determine its selling price, in order to cover costs and provide profit
MAU - Monthly Active Users: The number of unique users who engage with an app or website within a predefined 30-day period
Moat: A distinct competitive advantage that helps the company protect its market share
Mulch: A protective covering (as of sawdust, compost, or paper) spread or left on the ground to reduce evaporation, maintain even soil temperature, prevent erosion, control weeds and enrich the soil
Nudge: A nudge is a contextual push notification that is aimed at deriving action from receivers
Omni-channel: It describes a business strategy that aims to provide a seamless shopping experience across all channels, including in store, mobile, and online
Operating Lease: It is a contract for a company to use an asset and return it in a similar condition to the lessor
Operating Profit: It is the total income a company generates from sales after paying off all operating expenses, such as rent, employee payroll, equipment and inventory costs. It excludes gains or losses from interest, taxes and investments
Payback Period: It refers to the time required to recoup the funds expended in an investment, or to reach break-even point
Pharmaceutical Grade Sugar: It is the more pure form of sugar that may not contain sulphur and heavy toxic material like lead arsenic and mercury etc. It is used mainly in preparation of pharmaceuticals and food products
Proctoring: To watch people taking an exam in order to check that they do not cheat
Protective Farming: It is a practice of preventing the crop from different agents including pests, weeds, plant diseases, and other organisms that cause damage to the agricultural crops
Realised Revenue: It is revenue that the company already has received
Receivables: Amount owed to a firm by its customers for goods or services used or delivered but not yet paid for
Reverse logistics: The supply chain process of returning products from end users back through the supply chain to either the retailer or manufacturer
Risk Return Ratio: A measure of return in terms of risk for a specific time period
ROFR - Right of First Refusal: It is a right in a contract that gives shareholders the opportunity of matching the price at which a third party has agreed to buy shares from existing investors or founders
SEO - Search Engine Optimisation: The process of improving the quality and quantity of website traffic to a website or a web page from search engines
Secondary Sale of Shares: It is the sale of shares of a private company by an existing investor to a third party that does not occur in connection to the acquisition of the company
SOP - Standard Operating Procedure: A set of written instructions that describes the step-by-step process that must be taken to properly perform a routine
Sunk Cost: Money that has already been spent and cannot be recovered
Table Turnover Rate: It measures the amount of time a party occupies a table over a specific period of time
Take-Rate: It is the fee charged by a marketplace on a transaction performed by a third-party seller or service provider
Term Sheet: A non-binding agreement outlining the basic terms and conditions under which an investment will be made
Throughput: It is the amount of a product or service that a company can produce and deliver to a client within a specified period of time
Trademark: A special symbol, design or name that a company puts on its products and that cannot be used by any other company
Valuation Floor: It sets the minimum possible valuation at which the convertible note derives its conversion price
Viral Coefficient: The number of new consumers or customers that are generated by an existing satisfied customer
Web 3.0: It is the concept of the next generation of the web, in which most users will be connected via a decentralised network and have access to their own data
White Labelling: When a company buys its product or service from another company and rebrands it as their own
Y2K Bug - Year 2000 Bug: A computer flaw, or bug, that may have caused problems when dealing with dates beyond December 31, 1999
Acronyms
FBA: Fulfillment by Amazon
GSM: Grams per Square Metre
КРО: Knowledge Process Outsourcing
OTA: Online Travel Agency
LTV: Lifetime Value

After dreaming about going for the CISSP for a while I finally coughed up the money to do it from the Peace of Mind sale. I am a very good test taker and I have been taking verious certs (I currently hold many including the SSCP, CySA+, and PenTest+) over the last 7 years as well as a BS in CyberSecurity. I have only used the OSG via one readthrough at this point and a lot of that was skimmed since I did it in 3 days. Since i had the protection I decided to go all the way after scoring higher on a practice test and just do it! So in around 30 hours I sit for this dream of mine.
Any last minute tips for maybe not the most careful of test takers?

I've found these two studies by Kim P. C. Kuypers, that claim that

A retrospective survey study reported that using classic psychedelics in low, repeated doses, so called microdosing (MD), was rated as being more effective than conventional treatments for ADHD.

They're published in Neuroscience Applied (Microdosing with psychedelics to self-medicate for ADHD symptoms in adults: A prospective naturalistic study, 2022), and a 2019 version in Frontiers in Psychiatry (Self-Rated Effectiveness of Microdosing With Psychedelics for Mental and Physical Health Problems Among Microdosers). From the 2022 study again,

the majority indicated that they used psilocybin/psilocin (magic mushrooms, truffles) (78%), followed by novel lysergamides (e.g., 1P-LSD, ALD-52) (12%), LSD (9.5%)

Of course, there was selection bias, and no control group:

Due to lacking a placebo-control group, the design could not test whether the MD group behaved differently than a group receiving a placebo. In the current study, participants were recruited via a MD website and respondents had the intention to microdose to self-treat their ADHD symptoms. It can only be expected that individuals who choose MD as self-treatment are positively oriented towards the practice of MD, which might enhance a potential placebo effect

Anyway, interesting study, but I don't understand how the participants tried to improve their ADHD issues specifically. Or did they just microdose and hope for the best? Why wouldn'y microdosing improve other symptoms, like depression or anxiety? Or is it claimed to improve everything?
This layman's article on the 2022 study, called Microdosing for ADHD doesn't explain that either.

Designing and developing websites and apps is a complex process that requires a combination of creativity and technical skills. Whether you are a seasoned designer or a beginner, there are always new tips and tricks to learn that can improve your workflow and help you create stunning designs. Here are some design and development tips to help you get started:
​

1. Understand your target audience: Before you start designing or developing, you need to understand who your target audience is. This will help you create designs that are tailored to their needs and preferences. You can use tools like Google Analytics or user surveys to gather insights about your audience.
2. Use high-quality icons, illustrations, logos, and backgrounds: The right icons, illustrations, logos, and backgrounds can make all the difference in your design. Visit docnek.com, a platform that provides icons, illustrations, logos, and backgrounds to choose from. Using high-quality visual assets can make your website or app look more professional and engaging.
3. Keep it simple: Simplicity is key when it comes to design. Avoid cluttered layouts, too many colors, and too much text. Stick to a simple color palette and use plenty of white space to make your designs look clean and elegant
4. Make it responsive: With the rise of mobile devices, it's more important than ever to make sure your designs are responsive. This means they should look good on any device, from smartphones to desktop computers. Use a responsive design framework like Bootstrap or Foundation to ensure your designs are optimized for all screen sizes.
5. Test and iterate: Testing is an important part of the design and development process. Test your designs on real users to gather feedback and iterate on your designs based on that feedback. Use tools like user testing software to gather feedback from your audience.
6. Stay up-to-date with the latest design trends: Design trends are constantly evolving, so it's important to stay up-to-date with the latest trends and best practices. Attend design conferences and workshops, read design blogs, and follow design influencers on social media to keep up with the latest trends.
   Designing and developing stunning websites and apps takes time and effort, but by following these tips, you can create designs that are both beautiful and functional. Visit docnek.com to browse a wide selection of icons, illustrations, logos, and backgrounds to use in your designs. With the right tools and techniques, you can create designs that will captivate your audience and help you achieve your business goals.
   

credit: https://dormando.livejournal.com/484577.html

The Technical Element

Design for change

- The old google mantra is right. Design for change. Change is having to deploy new software, upgrade existing software, scaling, equipment breaking, and people shifting around. - Everything in this mantra is about finding balance. You might think it's a good idea to tightly marry your system to a particular OS or Linux distro. It's just as bad of an idea to separately them entirely. Use layers and a _little_ indirection if you must. - This does not mean complete and total platform agnostics. It's about making one system two, two systems twenty. Dealing if a sysadmin gets hit by a bus, if that dangling harddrive dies, if someone runs rm -rf /. It's for the incremental changes. Security updates, pushing new corporate content.

Use automatic, repeatable builds

- Don't build anything by hand. If you do, do it twice, and grab every single command the second time around. - I cannot stress how important this is. It should take no more than 15 minutes from bare metal to production for new hardware. There does not need to be a human element to screw it up, or get punished when a server goes down and no one knows how to replace it. - This is true for anything. There is _no_ such thing as a "one off" server build. If you've built it once, and it only needs to exist once, it will exist twice. The second time around is when it breaks, or if you need to do a major upgrade or consolidation two years down the road and have no frickin' clue how it was put together. - Test, vet new builds. This should be easy because your builds are all automatic, correct? - Scripted builds means that upgrade from Linux Distro Version 3 to Version 4 is absolutely clear cut. Install Version 4 and test the scripts. Read documentation and fix until it works again. This should be a week's worth of work at most, not a yearlong project. (to finish just in time for Version 5 to come out!).

Use redundancy

- Just beacuse something might be easy to rebuild, doesn't mean you can ignore redundancy. Jump boxes, mail servers, billing gateways, whatever. Wouldn't it be a hell of a lot easier if you could swap out one half of the equation without causing downtime for your customers? - ... and along those lines, you get to "deal with it later!" when a box goes down at 3am, and the redundant machine kicks in. - Even if it's not ideal, go for it anyway. Rsync'ing configs to a second box is a step above nothing. DRBD might not be perfect but it can provide an amazing service.

Use backups

- We shouldn't even joke about this. Use harddrives, burn the tapes. Compress them, move them, run them in parallel. Backup EVERYTHING! - If your builds are automatic, the entire process can be backed up. If you're following along past this point a *real* Disaster Recovery plan might not seem so far fetched.

Keep monitoring specific

- Monitor every damn thing you can, but do it right. Don't get a thousand alerts if your NFS server craps its pants. Don't alert on timeouts if it doesn't make sense for your system. Test for success at the most specific level; sure the service might allow a new TCP connection, and it might even say hello, but does it remember how to do its job? - If you have 500 webservers, you probably don't need to know immediately if one goes down. You _should_ know if the load balancer decided to not take it out of rotation and real human people are seeing its uglyriffic error messages.

Graph data, keep exact historical data

- Graphs are for visualizing trends. Historical data is for crunching numbers. Don't mix the two! It's too easy to get wrong numbers from eyeballing graphs. Many sites use rrd's or other aggregating data systems which will average and smooth out data over time to save on storage space. This means it's not only hard to read, it's wrong. - Don't get trapped having to skim through hundreds of graphs just to pinpoint an issue. If you're trying to find outliers in the graphs, you can pull those out via scripts as well. - If you must use graphs for troubleshooting, try to aggregate high level concepts into a single page, which link into drill-down pages from there. If you can see a spike in the database load, you'll know to click to the page overviewing the databases, then you'd see the one or two iffy machines in question. The idea is to narrow something down fast. Remove as much guesswork as possible.

Log useful information, use multiple streams of data

- Work on your own, and with development, to log as much useful information as you can. Doesn't matter if you live analyze it and store the data somewhere, or lump it into a database and run reports. Information is useful. - Useful examples: Page rendering time (what page, what box, etc), user-facing errors, database and internal service errors, bandwidth usage, etc. - Establish graphs, reports, and do historical comparisons from generalized data. - Reports are really important. Get digested data week-to-week or day-to-day about changes in your infrastructure.

Understand your data storage, databases

- There's an entirely separate set of undrestanding about operating databases, but sometimes you can't leave all of this up to your DBA. - Having multiple, redundant databases affords you many luxuries. Operations that were once many hours of downtime can be done "online" without shelling out for a huge Oracle instance. MySQL and replication is a fantastic thing. - Work with the DBAs to get the best possible hardware for the database in question. RAID10, gobs of RAM, many fast spindles, and potentially RAM disks and SSD's. Ops has access to the vendors, DBA's can beat the pants off the hardware. Find out what works best and save tons of cash in the long run. - Database configurations are changing. Software like HiveDB, MySQL Proxy, DPM exist now. We're absolutely doing partitioned data for huge datasets. We're also thinking outside of the box with software like starling and Gearman. Learn what these are, and understand that not everything will be in a database. - Get a good grip on your filers! If the data's important, back it up! Snapshots on monolithic NFS servers are fantastic, wonderful, and NOT a backup! - Consider alternatives. MogileFS gets better year after year. There're likely other projects for freely and cheaply maintaining massive stores of files. Similar systems were developed for youtube.com, archive.org, etc. We're finally free of expensive NFS filers being the standard!

Scale out a lot, up a little

- You've seen all of the papers. Scale out is really the way to go. Get commodity (read: available, affordable, standard, NOT super cheap) hardware and work with everyone to ensure all aspects possible can scale out. - Scaling out starts at two, work from there. This also happens to encompass redundancy. - Scale out as far as you can without being idiotic about it. The example of MySQL replication with single master, many slaves, is a fantastic example of one form of scale-out sucking. All slaves must do all writes, so as the number of writes scale up with the reads (if they do for your app, which I bet they certainly do), you get less capacity per slave you add. - Keep alternatives in mind. User or range partitioning onto many databases, avoiding production slaves where possible, etc. Good ideas, many ways of implement. - Everything can scale if you give it a chance! Routers, switches, load balancers, webservers, databases. - Remember scale up? Big evil machines with many slow cores, lots of IO boards, and very expensive storage equipment? They're coming back. Well, the CPU part is. - RAM is cheap. - Combine the two, and you just may end up combining services again. A load balancer here, a webserver there... If an application can use many CPUs (apache) this is perfect. If it can't (memcached doesn't get much benefit from it, usually) you can end up wasting tons of available resources by segregating services too much. - Job systems could potentially fill in gaps here. Where there're extra cores, slap up more workers.

Cache

- Caching is good. Developers, sysops, etc. Get on this! Yes, it's weird. It's different. Sometimes you may even need to, gasp, make a tradeoff for it. Effective use of caching can have as much as a ten times increase in overall system performance. That's a giant magnifying glass over the systems you have already and a fraction of the overall cost. - Memcached. Service cache, denormalize DB structures (where it makes performance sense!), squid cache, or even make better usage of OS caches. - Test it, toy with it, and break it. There will be new and different problems with caching. Be prepared for it.

Asyncronous jobs

- Starling, Gearman, The Schwartz, whatever. Job systems allow much more application flexibility. Workers can be spawned one-off, be persistent (load cached data, prepare data, etc), be on different hardware, different locations, and be syncronous or asyncronous. - Maintaining these things is an ops issue. Using them is both a developer and an ops issue. - User clicks "send all my friends an e-mail". Schedule a job, immediately say "okay done! Your friends will receive your spam shortly!" - let the job service multiplex and deal with the issue. - Job systems are great places to bridge services. Blog post -> IM notification, billing cron -> billing services, authentication gateways, etc. - Easy to scale. There will be choke points for where requests come in, and all the workers need to do is pull. This is in contrast with the largely push/pull state of HTTP.

Security and patrols

- Install security updates! Seriously! There's a whole crazy network of people who are dedicated to giving these to you in the shortest period of time possible. Don't let them sit for _years_ because you're afraid of change. - Security is in layers. Accept what you can and cannot secure. Just because mysql has password access doesn't mean it gets to be directly accessable by the internet. - Disable passwords over ssh. Use passphrase encrypted key auth. Remote users _cannot_ guess your private key. They _have_ to get it from you. Keep it safe, and there's no point in firewalling off your ssh port. - Understand how the application works, exactly what it needs to do, and work that to your advantage. If the only part of your application which needs outbound internet access _at all_ are the billing pages and some twitter-posting service, those can easily become job workers. Put the job workers on specific boxes and allow those access to specific hosts. Keep the rest of your network in the dark. - The above is especially important for php sites, but probably works great elsewhere. If someone breaks in, it's most likely going to be through your application. When someone gets in through the front gate, they'll need to haul in their toolbox to get into the safe. Don't let them pull in data and get what they need, or upload the contents of your database somewhere! - These specific suggestions aside, read a lot. Use your best judgement, and test. If you have no understanding of how a security model works, that might not immediately make it worthless, but you certainly don't know where its limits are or even if it works. - Secure based on testing, theory, attack trees, don't stab in the dark. I love it when people dream up obscure security models and ordinary folks like me can smush it to crumbles. - Patrol what you can! Audit logins, logouts, commands used. All accesses to external facing services, including all arguments given in the request. Find outliers, outright ban input outside of the scope of your application, and do what you can actively and have the data to work retroactively. - If you suspect something's been cracked, *take proper precaution* and understand a little computer forensics (or get a company that does). Respond by removing network access, checking the system through serial console or direct terminal, and avoiding using any service, config file, or data on the compromised machine. Too many people "clean up a trojan' and never understand how it got there, or if they've _actually cleaned it up_. - If you do have a security team, forensics expert, or anyone else onhand, you must touch the machine as little as possible and isolate it. This means not rebooting it to "clear out some funky running processes". They need to be able to get at those. If you need to half ass it, go ahead, but remember to wipe the system completely clean, apply any security updates, and do your best to figure out if they've compromised any important data. Do what you can. - Security is an incredible balancing act. If you do it wrong, developers, users, etc, will revolt and find ways around it. If they _can_ get around it, you're not doing your job right. If they _can't_ get around it, they might just give up and leave. - Keep an iron grip on access control. This means ops must absolutely provide windows for what doors have been locked. Kicking development off of production entirely means they get to stab in the dark on fixing hard problems. Providing logging, debugging tools, etc, without allowing them to directly change the service, will be a win for all aspects of production.

The Human Element

Learn from many sources

- Fill up some RSS feeds, and read at least a few good articles per week. LWN, kerneltrap, undeadly.org, whatever's relevant, or even loosely related, to what you do. - Read blogs from smart people. Sometimes they post interesting topics, and comment streams give us the unique ability to directly converse with the masters. - Read a few blogs from not so smart people. Get a feel for what stumps them, or what they do that doesn't work so well. - Get to know people who can kick your ass, at anything. Stay humble. - Help find your own strengths by taking in from many sources, and gobbling up what envigorates you. - Read up on success and failure stories from other companies. Ring up their CTO's and get them to divulge advise over free lunch.

Try many things

- You'll be amazed at what you can do if you keep trying. Never seen something before? Give it a shot. - Try to not be a dangerous newbie. Play in the sandbox until you're comfortable enough to not burn down the house.

Understand redundancy

- Really understand how redundancy affects things. How it works, how it doesn't work. - Break redundant systems in a test lab, sometimes in production. Learn what you can while you're in control. Unplug the power, yank cards out, kill processes, run the box out of memory, yank a harddrive, yank ethernet. - Test replacing and upgrading systems in a redundant setup. Maybe you can toss in that brand new hal-o-tron 8000 without taking downtime.

Understand scalability

- There're tons of papers on making scalable systems. Even if you can't write one yourself, try to understand the theory. - Learn with virtualization. Set up a few virtual machines and try tossing up applications to multiple machines. Run multiple instances locally on different ports. - It's usually the job of operations to do proper capacity planning. You won't know what to do add unless you truely understand where resources should be added.

Become a troubleshooting superstar

- The moment something breaks the clock is ticking. You must be able to pull out your arsenal and use them effectively. - Practice troubleshooting. Pick a perfectly good, working page, and try to track down how it works. - strace, ltrace, lsof, logs. - Understand that load != load. Look at all available information as to how a host is performing or behaving. - Be very familiar with the tools for your IO system. Often "mysterious" performance problems happen beacuse your RAID or SAN setup isn't happy for some reason. - Leave documentation. Checklists, troubleshooting tips, build tools. - Build more tools. For yourself, for other people, or add features to existing ones.

Work with IT

- Believe it or not, there is overlap. - Ops has to maintain high bandwidth network access for servers. IT has to do the same for people, and is often the bridge ops has *into* the datacenter. It may make sense to work together on this one. - Draw the right line. IT should manage mail, but ops should manage development servers. Don't offload things you don't need to, and offer to do what you do best if necessary. - Don't alienate people. Macs are popular, linux is (slowly) gaining share. Believe it or not, forcing everyone to use microsoft productivity software can bite you. There are plenty of alternatives, try one. Odds are more people in your company are familiar with google apps than they are with outlook. - Don't make it more difficult than you have to do for people to run a unix system natively. Unless your backend is a windows shop, wouldn't you want people to have more familiarity with the OS they're supposed to support?

Work with developers

- You both work on the same product, for the same purpose. Try working together a little more. - Having strategy meetings is not working together. - Development understands the code resources the best, and operations understands the hardware and deployment the best. You can design something more efficient by taking all of this into mind. - Cross training. Disseminating information can show how tools and designs on both sides can be improved to be more manageable and resilient. - Be careful of being too demanding on either side. It's not an Us vs Them. Everyone's human. Everyone should be doing as much as they can for the company, not for themselves. - It's more pleasent to handle crunch times and emergencies when everyone gets along.

Work with ops

- Ops folks have their specialties. Networking, databases, OS. Don't forget to talk to each other! - Getting stuck in a rut is demotivating, boring, and a good way to lose people. Even if your systems ops guy has the ability to look over the shoulder of the network guy, they have the opportunity to learn. - Always give people an opportunity to try, learn, and grow. - Be careful of rewarding your best with too much work. If there're people who can pick up slack, you use them. - Bad eggs. It happens. Be tough enough to deal with them. Most people can be turned around with a little help, but they need to be able to be independent.

The Practice

Fix it now, not later

- If a webserver goes offline, don't care about it. You have ten spare, right? - Pick a day during the week to sweep up broken crap. Replace any broken hardware, ensure everything's 100% before swinging into the weekend. - If small, annoying problems crop up, fix them permanently first thing in the morning. Logs fill up the disk twice last week? Come in fresh the next day, and fix it for good. These stack up, and suck. - If you have automated builds, use this to your advantage to fix what you can right away, or in bulk.

Automate everything

- Humans can't screw up scripted tasks (as easily). - Do it twice. Once by hand if you must, then roll up what you did into a script. - Commented scripts make fantastic documentation. Instead of writing twenty pages detailing how to install something (which is up to interpretation of the reader!), write a script which explains what it does. - Scripts can be rolled up into automated builds. The more often something is done, the closer it should get to becoming a zero time task.

Change what's necessary

- Make small, isolated changes. - If you don't have to change it, leave it. - This also means you must understand _when_ to change. Find what's necessary and upgrade it, switch it out, make it standard.

Design for change

- If you can't do it right immediately, get on the road to it being right. - This means if you don't have time to do something right, get the basics going with a clear migration roadmap to the right thing. While your new mail system might not be the crazy cool redundant bounce-processing spam monster you dream of, installing postfix and setting up two hosts with a clean configuration gets you closer than you might think. - This does have a tendency to leave unfinished projects everywhere, but you were going to do that anyway. :)

Practice updating content, fast

- It's usually the job of operations to push out code. Don't suck at it. Push in parallel, apply rolling restarts, be an efficient machine. - This includes software updates, security patches, and configuration changes. - Use puppet, cfengine, whatever you need to control the configuration. Keep it clean, simple, and easy. - The fewer files one must change to make a necessary adjustment the better. If you're adding one line to 20 files just to push out a new database, you're doing it wrong. Build simple templates, build outward, and don't repeat data which needs to be edited by hand.

Standardize, stick to the standard

- Pick one or two standard OS's, httpd's, databases, package systems. - Stick with them. Adjust and upgrade methods as it makes sense. - Don't stick with that major version forever. Unless your product is going to be feature frozen forever, you'll need to keep the standard rolling forward, and everthing behind it. - The _more_ is standard, the more places your tools will work. The more packages for other parts of the operation will "just work" everywhere else too.

Document well

- Document process - Document product - Categorize into shallow trees. - Don't redundantly document. If a script has a long help, ask the reader to refer to that. The closer the documentation is to the program being discussed, the more likely it is to stay accurate. - Marry documentation into code. perldoc, pydoc, etc. - Out of date documentation is poisonous. Reserve time to keep things up to date. Sit down with new employees and update documentation as they run into problems. - Use ticketing systems, with moderation. Documentation of history is important as well. Forcing people to create detailed process tickets for a DNS is just pissing in other people's cheerios.

Use source control

- Use git, or mercurial. Avoid SVN like the black plague. - Put all of your configurations, scripts hacks, whatever, into source control. - Keep checkouts everywhere... - Keep strict, clean, master checkouts. No one should be able to push changes that aren't comitted, but it should also be easy to test changes (in a VM, directly on a single test machine) without having to wrestle with the source control.

Hire well

- Discern between stubborn and smart - Don't avoid hiring senior. Some people really know their shit. Some _seem_ like they do. Others are "senior" in a particular area and will fall behind as technology changes. While you might want to avoid some, there are definitely rockstars out there. - Don't avoid hiring junior. I know so many people who've started really junior (including myself! I still view myself as junior), who've shot up through the ranks and are now have firm established careers. I'd believe most of us have. Except there are ones who don't learn, don't have the motivation, or are in the wrong field.

Avoid vendor lock in, and keep a good relationship with the vendors you do use

- Buying propreitary hardward has the major downside of potentially locking you into always using it. It might be a particular SAN, NAS, special-case direct attached storage, backup systems, etc. Avoid getting sucked in. If you follow all of the above design advise, one should be able to build test environments on different platforms quickly. You're then able to keep on top of hardware evaluations and keep choices open. - If everything's deep, dark, gnarled, undocumented, and directly dependent on your fancy proprietary load balancer, you'll never wriggle free of it. - Be nice to the vendors you do end up using. If you "push them _hard_ on price!" for every single purchase, expect some shit hardware to show up. - Datacenters these days have a lot of potentially useful resources. Try to throw some free remote hands service into your contract and abusing that to get harddrives replaced, vendor items shipped/RMA'ed, and some basic hardware installs. I've had entire racks of equipment delivered and installed with barely a visit from an employee... and damn, it's nice.

Give Open Source a serious try

- nginx, mongrel, lighttpd, apache, perlbal, mogilefs, memcached, squid, OpenBGPD, PF, IPTables, LVS, MySQL, Postgres, blah, blah, blah. Before you hop back on that trusty, reliable, expensive proprietary setup, give open source a shot. You might find yourself adding plugins, extensions, code fixes or contracting help to bring features you'd never be able to do otherwise. In my own experience OSS is just as reliable, often moreso, than big expensive hardware when put under significant load. - The idea of "you get what you pay for" is a complete lie. If you can't make OSS work for you and need the hand holding, you _can_ still go with a vendor. If you have a smart, motivated team, who really want to learn and understand how their infrastructure runs, you just can't beat some hardy GPL'ed or BSD'ed systems. - MySQL and Postgres are fine. Call them tradeoffs if you will; nothing's going to crawl out of your closet and night and eat your data. Sure, it does happen, but you're much more likely to be screwed over with monolithic oracle instances going offline (it happens!) than you are with a well tested and stable MySQL instance, in a redundant master<->master cluster pair. - I'd say 'cite references' - but go look around. Check out any number of articles on the LAMP stack. Most major dot coms, ISP's, and even corporations now are adopting. Give it a shot. The worst you'll have is some lost time, and another product to scare your vendor into dropping price with.

Hello, I live in Europe and Comptia is not really known but I wanted some challenge while learning at the same time. I mostly do IT Risk management, it's not a technical cyber position.
So after passing CEH, eJPT and some Azure/AWS certs, I got Security+ back in November 2022. Then Blue teamLVL1 in February of this year (I wanted some practical hands-on skills unlike Cysa+).
While preparing for CISSP I noticed the Comptia Advanced Security Practioner so I thought it was like Security+ but harder....I clearly underestimated the exam. Every questions were scenario-based and most answers could fit the question (barely no distractors): from CASB, log analysis, MDM to ICS/Scada, GDPR, modern protocols and cryptographic cyphers...the topics were really broad. The most important thing is to carefully read the context and what security controls are expected.
The hardest part was the VM assessment (cannot give you more details about it due to NDA). It took me almost 1 hour to solve it and the exam administrator at the test center had to help me relaunch the exam. Really stressful situation but it was eventually solved (do not attempt the exam remotly if possible). The score report told me I passed somehow !!

I’ve been using SH to practice. Have done all mini exams and over have of the practice questions. Today, all my scores were gone. I took about 5 mini tests again, and again all scores are missing. Anyone have this happen? It’s messing me up because when I retake the test I have memorized the answers so now my averages are way too high. :/

PMP certification training is a globally recognized project management certification. Aligned with the PMBOK® v7 New EXAM 2021, this PMP certification training program comes with a host of learning aids like practice tests and in-depth video lectures. Sprintzeal’s expert-led PMP training program is designed to help learners pass the PMP exam on their first attempt and get certified.

Hi,
If anyone wants targeted function (derivatives) practice, I've compiled my own solutions to such free response questions/FRQ's (1998 to 2019). I gave hints, elaborated more than the official solutions, and tried to make them more systematic in approach.
Video: https://www.youtube.com/watch?v=vLIgFMhcvfE
Slides: https://robbiepmath.wordpress.com/2023/03/21/ap-calculus-ab-bc-frq-functions-derivatives-frq-1998-2019/ (a link to a wordpress; not a direct pdf link)
Original questions can be found on the official college board site: https://apcentral.collegeboard.org/courses/ap-calculus-ab/exam/past-exam-questions and https://apcentral.collegeboard.org/courses/ap-calculus-bc/exam/past-exam-questions (I can't include copyrighted questions and so you'll have to match my solution with the test year)

Soooo I'm getting my Alaska in about 15 hours, and I'm curious. I want to run one of the AL cruiser commanders on her, AL Baltimore or AL Montpelier. I'm rlly having quite the tough time figuring out which I want to use. They're practically the same, skill wise, aside from their base traits and unique skills. Which I don't particularly ever use on Baltimore since I hit citadels reliably, so it ends up with me using the +10% AP damage and +6% AP pen mult. But Montpelier's unique skills seems quite decent... +4% grouping of main shells, and +10% incoming fire dispersion, but +5% damage taken, which IMO is so miniscule it doesn't matter too much. If I'm eating Yami shells then I'm either taking overpens, bounces, or citadels, there's no sweet spot. ANYWAY I just want some opinions on who I should run on her! I'm gonna test them both out to see which I prefer, but more opinions are always good!