TipTop

tiptop

Ever found yourself squinting at your own code at 2 a.m., trying to remember what exactly you were thinking when you wrote it? You’re not alone. Writing clean, maintainable code is one of those things that sounds great in theory but can feel impossible under tight deadlines and mounting pressure. But here’s the thing, clean code is your secret weapon. It’s the key to fewer late-night debugging sessions, fewer headaches for your future self, and more time to actually enjoy life outside of coding. So, let’s dive into why clean code matters, how to achieve it, and why your future self will thank you. The Importance of Clean Code: Why It Matters: Imagine you’re handed a project written by someone else, and it’s an indecipherable mess of variables named var1 and x23. You waste hours trying to figure out what’s going on, and by the time you do, you’re too frustrated to care. Now, flip the script. What if you’re the one writing that code? Clean code isn’t just about making life easier for others; it’s about making life easier for you. Think of it as a gift to your future self, a codebase that’s a pleasure to work with, not a burden. Principles of Clean Code: 1. Keep It Simple, Smarty Pants: There’s a certain allure to writing clever, complex code that only you (and maybe your cat) can understand. Resist it. Simplicity is your friend. The simpler your code, the easier it is to maintain and the fewer the bugs. Remember, your code should do one thing well, not everything poorly. 2. Write Code Your Mom Could Understand: Okay, maybe not your mom, but at least a fellow developer who’s never seen your code before. Self-explanatory code means fewer comments, less confusion, and fewer excuses for why you can’t fix that bug. Descriptive variable names, clear functions, and intuitive classes are your best friends here. 3. DRY—Because Repeating Yourself Is So Last Year: Repetition might be great for memorizing lines in a play, but in coding, it’s a recipe for disaster. The DRY principle—Don’t Repeat Yourself—is all about reducing redundancy. Why write the same code twice when you can abstract it into a reusable function? Think of it as Marie Kondo-ing your code: if it doesn’t spark joy (or efficiency), it’s time to refactor. 4. Refactor Like You Mean It: Refactoring is like cleaning your house: it’s never done, but it’s always worth it. Regularly refactoring your code keeps it in tip-top shape, improves readability, and can even uncover hidden bugs. Plus, there’s nothing quite like the satisfaction of turning a chaotic codebase into something neat and orderly. 5. Test Like Your Code’s Life Depends on It: Because it does. Tests are your safety net, catching errors before they become full-blown disasters. Whether it’s unit tests, integration tests, or end-to-end tests, make sure you’ve got your bases covered. Writing clean code without tests is like skydiving without a parachute. Eventually, it’s going to hurt. Practical Tips for Writing Clean Code: 1. Break It Down, Now: Big, sprawling functions are like that one junk drawer in your house—full of stuff, but impossible to find anything in. Break your functions down into smaller, single-purpose units. Your future self (and your team) will thank you when they’re not wading through a 500-line behemoth. 2. Consistency Is Key: There’s nothing worse than a codebase that looks like a patchwork quilt of different naming conventions. Whether you’re a fan of camelCase, snake_case, or kebab-case, just pick one and stick with it. Consistency makes your code easier to read and maintain and it stops your colleagues from grumbling about your variable names behind your back. 3. Clever Code ≠ Good Code: Sure, that one-liner might look impressive, but is it readable? If the answer is no, then it’s not worth it. Prioritize clarity over cleverness. Your code should be easy to understand at a glance, not something that requires a degree in cryptography to decipher. 4. Embrace the Power of Peer Reviews: Code reviews are like having a second pair of eyes on your work and sometimes, those eyes catch things you never would have noticed. They’re not just about catching bugs, though; they’re also an opportunity to learn from your peers and improve your own coding practices. 5. Let the Robots Help: Linters and code formatters are your silent, tireless helpers. They catch issues before they become problems, enforce coding standards, and generally make your life easier. Set them up in your IDE, and let them do the heavy lifting when it comes to keeping your code clean. Clean code isn’t just a nice-to-have, it’s a must-have if you want to be a developer who’s not constantly putting out fires. By keeping things simple, writing self-explanatory code, and embracing practices like DRY, refactoring, and testing, you’ll set yourself up for success. Plus, your future self will definitely appreciate not having to decipher a tangled mess of code. So go ahead, write that clean code, and enjoy a little more peace of mindand maybe even a full night’s sleep. Ever found yourself squinting at your own code at 2 a.m., trying to remember what exactly you were thinking when you wrote it? You’re not alone. Writing clean, maintainable code is one of those things that sounds great in theory but can feel impossible under tight deadlines and mounting pressure. But here’s the thing, clean code is your secret weapon. It’s the key to fewer late-night debugging sessions, fewer headaches for your future self, and more time to actually enjoy life outside of coding. So, let’s dive into why clean code matters, how to achieve it, and why your future self will thank you. The Importance of Clean Code: The Importance of Clean Code: Why It Matters: Imagine you’re handed a project written by someone else, and it’s an indecipherable mess of variables named var1 and x23. You waste hours trying to figure out what’s going on, and by the time you do, you’re too frustrated to care. Now, flip the script. What if you’re the one writing that code? Clean code isn’t just about making life easier for others; it’s about making life easier for you. Think of it as a gift to your future self, a codebase that’s a pleasure to work with, not a burden. Principles of Clean Code: Principles of Clean Code: 1. Keep It Simple, Smarty Pants: There’s a certain allure to writing clever, complex code that only you (and maybe your cat) can understand. Resist it. Simplicity is your friend. The simpler your code, the easier it is to maintain and the fewer the bugs. Remember, your code should do one thing well, not everything poorly. 2. Write Code Your Mom Could Understand: Okay, maybe not your mom, but at least a fellow developer who’s never seen your code before. Self-explanatory code means fewer comments, less confusion, and fewer excuses for why you can’t fix that bug. Descriptive variable names, clear functions, and intuitive classes are your best friends here. 3. DRY—Because Repeating Yourself Is So Last Year: Repetition might be great for memorizing lines in a play, but in coding, it’s a recipe for disaster. The DRY principle—Don’t Repeat Yourself—is all about reducing redundancy. Why write the same code twice when you can abstract it into a reusable function? Think of it as Marie Kondo-ing your code: if it doesn’t spark joy (or efficiency), it’s time to refactor. 4. Refactor Like You Mean It: Refactoring is like cleaning your house: it’s never done, but it’s always worth it. Regularly refactoring your code keeps it in tip-top shape, improves readability, and can even uncover hidden bugs. Plus, there’s nothing quite like the satisfaction of turning a chaotic codebase into something neat and orderly. 5. Test Like Your Code’s Life Depends on It: Because it does. Tests are your safety net, catching errors before they become full-blown disasters. Whether it’s unit tests, integration tests, or end-to-end tests, make sure you’ve got your bases covered. Writing clean code without tests is like skydiving without a parachute. Eventually, it’s going to hurt. Practical Tips for Writing Clean Code: Practical Tips for Writing Clean Code: 1. Break It Down, Now: Big, sprawling functions are like that one junk drawer in your house—full of stuff, but impossible to find anything in. Break your functions down into smaller, single-purpose units. Your future self (and your team) will thank you when they’re not wading through a 500-line behemoth. 2. Consistency Is Key: There’s nothing worse than a codebase that looks like a patchwork quilt of different naming conventions. Whether you’re a fan of camelCase, snake_case, or kebab-case, just pick one and stick with it. Consistency makes your code easier to read and maintain and it stops your colleagues from grumbling about your variable names behind your back. 3. Clever Code ≠ Good Code: Sure, that one-liner might look impressive, but is it readable? If the answer is no, then it’s not worth it. Prioritize clarity over cleverness. Your code should be easy to understand at a glance, not something that requires a degree in cryptography to decipher. 4. Embrace the Power of Peer Reviews: Code reviews are like having a second pair of eyes on your work and sometimes, those eyes catch things you never would have noticed. They’re not just about catching bugs, though; they’re also an opportunity to learn from your peers and improve your own coding practices. 5. Let the Robots Help: Linters and code formatters are your silent, tireless helpers. They catch issues before they become problems, enforce coding standards, and generally make your life easier. Set them up in your IDE, and let them do the heavy lifting when it comes to keeping your code clean. Clean code isn’t just a nice-to-have, it’s a must-have if you want to be a developer who’s not constantly putting out fires. By keeping things simple, writing self-explanatory code, and embracing practices like DRY, refactoring, and testing, you’ll set yourself up for success. Plus, your future self will definitely appreciate not having to decipher a tangled mess of code. So go ahead, write that clean code, and enjoy a little more peace of mindand maybe even a full night’s sleep.

The Secret Weapon of Developers Who Want to Sleep at Night

03/28 Crypto Market Update Let's face it: the crypto market's been about as exciting as watching paint dry lately. But then, in walks Litecoin, the rebellious teenager of the world, defying the odds and skyrocketing to a two-week high of around $99. Now, this 9.25% jump in 24 hours has us scratching our heads – what's going on here? crypto Sleeping Giants Awake (and Maybe Cause a Little Trouble First) Here's the first plot twist: a bunch of dormant Litecoin tokens worth over $60 million decided to wake up from their slumber and rejoin the party on March 5th. It was the biggest daily jump for these sleepyheads on record. Now, this reunion wasn't exactly smooth sailing. The market initially freaked out, causing a 19% price drop. But hey, maybe it was just a case of first-day jitters? Because guess what? The market quickly absorbed these revived tokens, leading to a 37.25% rebound. This whole scenario feels eerily similar to what happened before Litecoin's 2017 bull run, where a similar awakening of dormant tokens paved the way for a massive price surge. So, is history repeating itself? Buckle up, folks, it's getting interesting. Coinbase Futures: The Shiny New Toy That Might Lure the Big Guys Adding fuel to the fire is a rumor that Coinbase will launch cash-settled Litecoin futures contracts in April. Now, this might sound like financial jargon overload, but here's the gist: it could attract a whole new crowd – the big institutional investors. Remember what happened when CME launched Bitcoin futures in 2017? The market went nuts! Could this be the secret sauce for Litecoin's future success? We don't have a crystal ball (yet!), but it's definitely something to keep an eye on. Strong Foundations: Not Just About Price But it's not all about price jumps. Litecoin's network itself seems to be in tip-top shape. The hash rate, which basically measures how secure the network is, is hitting record highs. This suggests that miners, the folks who keep the whole thing running, are feeling pretty confident. Maybe it's because of the upcoming Bitcoin halving event (where the rewards for mining Bitcoin get cut in half). This often leads to a price increase for Bitcoin, and sometimes, its ripple effect reaches other cryptocurrencies like Litecoin. So, even if you're not a techie, understand this: strong network = happy miners = potentially good news for Litecoin. The Chart Whisperers and Their Predictions Now, for those who like to analyze charts and lines more than we do, here's some good news. Litecoin's recent price action suggests it might have broken free from a long downtrend. In financial speak, that's a bullish signal. Plus, there's strong support from traders (think of it like having a bunch of people cheering for Litecoin) and a positive indicator called the RSI. The bottom line? The charts seem to be whispering that Litecoin might keep climbing, potentially reaching around $127.25 by April. But hey, remember, the crypto market can be as unpredictable as a teenager's mood. There's always a chance it could retreat and test support levels at $75.50. Oh, and Don't Forget About the Rest of the Crypto Zoo While Litecoin steals the show, there's other drama unfolding in the crypto world: A judge said "no way" to Coinbase's attempt to ditch a lawsuit from the SEC. This legal battle could have a major impact on crypto exchanges and regulations. Coinbase vs. SEC: Rumors are swirling about a potential mega-merger between some big names in AI – SingularityNet, , and Ocean Protocol. This could create a $7.5 billion giant in the AI-powered blockchain space. Talk about a power couple! AI Token Merger? Fetch.ai The NFT game Munchables got hacked, resulting in a massive loss of ETH. This serves as a stark reminder that security in the NFT space is crucial. NFT Security Breach: The Final Word: Don't Be a Blind Follower Remember, the crypto market is exciting, but it's also risky. Don't just blindly follow the latest trends. Do your own research, understand the risks, and maybe consult with someone who isn't as easily swayed by shiny objects (like, ahem, some of us). This article is just a glimpse into the ever-changing world of crypto, but hopefully, it keeps you entertained (and maybe a little informed) along the way.

Crypto Market Update: Litecoin Soars Like a Rocket While Cryptoland Sleeps 

This one is personal. It was a random Friday evening and I had a ‘simple’ goal: host a static website on with my domain. I mean, how difficult can it be, right? Apparently quite, considering it took 10 articles, 4 tutorials, 2 videos, and an entire day of trying everything the internet had to offer. AWS S3 GoDaddy But fret not! Your journey will be far smoother. Let’s embark on this adventure together, starting with the first and fundamental step: snagging yourself a catchy domain. Content Overview GoDaddy: Securing Your Slice of the Internet Pie! Amazon Web Services: Where Websites Fly First Class Migrating GoDaddy Domain to AWS S3 Bucket Webmaster: Smooth Updates for Your Shiny, New Site Celebration Time: You’re Live! GoDaddy: Securing Your Slice of the Internet Pie! (Learn how to acquire and set up a personal domain with GoDaddy.) So, you’ve decided to establish your own little corner on the web. Exciting times ahead! Let’s begin with the basics: . acquiring a domain Step 1: Choose Your Domain Start by brainstorming a unique and memorable domain name that represents you or your project well. Keep it short, sweet, and easy to spell. Once you have a few options in mind, it’s time to head over to GoDaddy’s website. Step 2: Search and Select On GoDaddy’s homepage, enter your desired domain name into the search bar. If your first choice is taken, don’t despair! GoDaddy will offer alternative suggestions, or you can try a variation of your initial idea. Once you find an available domain that you love, add it to your cart by clicking on the button. Make it Yours Step 3: Customize and Checkout GoDaddy will offer various add-ons and options, like privacy protection and professional email addresses (<username>@yourdomain). Review these offerings, select the ones that fit your needs, and proceed to checkout. Complete the transaction, and voila, the domain is yours! Step 4: Setup and Configuration Now, with the domain in your possession, there might be a few setup steps and changes before it shows up on your desired URL. Configure your domain settings, connect it to your hosting (which we’ll dive into next), and ensure everything is in tip-top shape for launch. For this part of the setup we’ll be visiting your domain’s DNS Records and Forwarding rules. And just like that, you’ve successfully secured your slice of the internet pie with GoDaddy! Stay tuned as we navigate through the next phase of our digital journey: hosting with AWS S3. Amazon Web Services: Where Websites Fly First Class (Introduction to hosting your website on Amazon Web Services’ S3.) Welcome to the powerhouse of the internet: . If the web were an ocean, AWS would be its mightiest vessel, and today, you’re coming aboard to host your website in style. Amazon Web Services (AWS) Step 1: Navigating the AWS Landscape AWS is vast, with a myriad of services that can be overwhelming for first-timers. Either log-in to your existing AWS account or create a new one. : Upon first login to AWS, you’ll encounter the AWS Management Console. It’s your control center for AWS services, so take a moment to explore its layout. Notice the ‘Services’ dropdown at the top left, your go-to hub for all AWS offerings. Familiarizing Yourself : Under the ‘Services’ dropdown, you’ll find ‘S3’ listed under the ‘Storage’ category. Click on ‘S3’ to enter the S3 console, where you’ll be managing your static website hosting. Finding S3 Step 2: Creating an S3 Bucket Think of a bucket as a storage unit for your website. Click on the ‘Create Bucket’ button. Here, you’ll name your bucket (usually, this should match your domain name for simplicity but its fine to name it anything you like), select a region closest to your target audience, and follow through with the default settings for now. : Under the S3 console, click the blue ‘Create bucket’ button. A window appears prompting you for a bucket name. Select a name closely matching your domain for consistency. Naming Your Bucket : Pick a region close to your audience to minimize latency. Each region corresponds to a specific geographical area. For me personally, I always prefer using US East regions since I am based in the US and also because it helps with SSL certification process on AWS (more on this in the next section). Selecting Regions : While many settings are fine at default, glance through each option and get acquainted. You’ll likely not need to adjust much here, but familiarity is key for future troubleshooting and adjustments. Reviewing Settings Step 3: Configuring the Bucket Once your bucket is ready, it’s time for some configurations. Set the properties and permissions to make your bucket public (as it is private by default), enabling people to view your website. You’ll also set up static website hosting here by enabling the feature and designating your index and error documents. : Uncheck “Block all public access” to allow users to access the bucket files. This is what it should look like post allowing access. Public Access Settings Step 4: Uploading Content and Making it Public With everything set up, you’re ready to upload your website’s files to the bucket. Simply drag and drop, or manually upload your HTML, CSS, and other files into your S3 bucket. : Upload your static website files to the new bucket. You can do this using the AWS CLI or by selecting the “Upload” option under the “Objects” tab. Personally I always use the upload option. Uploading Website Files : Navigate to the “Properties” tab of your bucket and scroll to “Static website hosting”. Click “Edit”, enable static website hosting, and input your default page name (typically ‘index.html’) in the “index” text field. Don’t forget to save your changes! Enabling Static Website Hosting : Head to the “Permissions” tab and add a bucket policy to grant public read access to your bucket (change YOUR-BUCKET-NAME and add the code provided below). This policy allows anyone on the internet to read the objects in your bucket, so ensure you want your data to be publicly accessible. Be sure to review and understand the policy’s permissions before saving it along with your other changes. Granting Public Access {
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "PublicReadGetObject",
            "Effect": "Allow",
            "Principal": "*",
            "Action": [
                "s3:GetObject"
            ],
            "Resource": [
                "arn:aws:s3:::YOUR-BUCKET-NAME/*"
            ]
        }
    ]
} Step 5: Testing Your Live Site AWS provides a unique endpoint for your hosted content. Click on this link, and if all is well, you’ll see your static website alive and kicking! And there you have it! The initial descent into AWS might seem daunting, but with these steps, you’ve not only landed but set up base. Ready for the next adventure? We’ll delve into going live in the upcoming section. Finally Done: Your Site is Live! (A walkthrough of successfully hosting your website and seeing it go live.) Congratulations, you’re almost there! Now, let’s bind everything together by pointing your shiny new GoDaddy domain to the AWS S3 bucket you’ve meticulously set up. Migrating GoDaddy Domain to AWS S3 Bucket Step 1: Getting an SSL Certificate with AWS ACM Open AWS Certificate Manager (ACM). Click “Request” to initiate a new certificate and select “Request a public certificate”. Add your domain names — & . www.your-domain.com your-domain.com Choose “DNS Validation”. After certificate creation, two CNAME records will be generated by ACM. Copy both the “CNAME name” and “CNAME value” for later use. Step 2: Updating DNS Records in GoDaddy Login to your GoDaddy account and navigate to the domain settings of your chosen domain. Go to “Manage DNS” under “Additional Settings”. Add the CNAME records provided by ACM. Repeat this step for both sets of values provided. Set “Type” to “CNAME”. “Name” is the “CNAME name” from ACM (in this case making it _95c3d23b4c008dfcadeed5b518ed3d1d.www & _2bb2bfda7c66af8c036422465b415a8c). omitting the . part from the CNAME name your-domain.com “Value” is the “CNAME value” from ACM (copy as is). Set “TTL” to “Default”. Allow some time for these changes to propagate and the certificate to be validated. Step 3: Creating AWS CloudFront Distribution Open the CloudFront console on AWS. Click “ ”. Create Distribution Enter the S3 bucket website URL as the “ ” (avoid using the auto-suggested link). Origin Domain Under “ ”, select “Redirect HTTP to HTTPS”. Viewer Protocol Policy Under “ , select “Enable security protection”. Web Application Firewall (WAF)” Add “ ” for both your preferred website URLs ( and ) under “ ”. Alternative Domain names (CNAME) www.your-domain.com your-domain.com Settings Choose the previously created ACM certificate under “ ”. Custom SSL Certificate Complete the distribution creation process and wait for it to deploy (usually 5–10 minutes). Step 4: Pointing Domain to CloudFront and Final Adjustments Unfortunately, GoDaddy’s standard DNS service does not support direct ALIAS or ANAME records to CloudFront. Therefore, the best practice is to set up a CNAME for the www subdomain and then redirect the root domain to the www subdomain. You already have a CNAME for www, so let’s modify that. Take note of the CloudFront domain name provided upon creating your distribution, resembling . CloudFront Domain Retrieval: dxxxxxxxxxxxxx.cloudfront.net GoDaddy’s standard DNS doesn’t support ALIAS or ANAME records pointing directly to CloudFront for root domains. To address this, set up a CNAME for your subdomain and redirect the root to . Updating Root Domain Record: www www Modify the existing CNAME record for subdomain: Adjusting CNAME for www: www Type: CNAME Name: www Data: [Your CloudFront domain name] TTL: 1 Hour (adjust as preferred) Implement forwarding to redirect traffic from your root domain to the subdomain: Setting Up Root Domain Forwarding: www Go to DNS management for your domain in GoDaddy’s dashboard. Locate the “Forwarding” section and add “Domain” forwarding. Forward to: www.your-domain.com Redirect type: 301 (Permanent) Settings: Forward only Maintain the existing NS, SOA, and records without changes. Handling Other Records: _domainconnect Following these DNS adjustments, propagation might require some time, potentially ranging from immediate to several hours. Utilize tools like to monitor propagation status globally. Propagation Time Consideration: DNS Checker Once propagation concludes, accessing or should direct users to your site hosted on CloudFront securely via HTTPS. your-domain.com www.your-domain.com Webmaster: Smooth Updates for Your Shiny, New Site (Guidance on updating and maintaining your newly hosted website.) Updating your static website hosted on AWS S3 is a straightforward process. Follow these steps to ensure your site stays fresh and up-to-date: Step 1: Accessing AWS S3 Log in to your AWS Console. Navigate to the S3 service. Open the bucket hosting your website. Step 2: Updating Website Files To update existing files: Navigate to the file you wish to replace. Either overwrite this file by uploading a file with the same name or delete the existing file and upload the new version. To add new files, simply upload them to the relevant directory within your bucket. Step 3: File Permissions (if necessary) When uploading new files, ensure their permissions are set correctly. If your bucket is public, new files should typically be set to ‘public read’ to be accessible to visitors. Step 4: Clearing Cache (if using CloudFront) If you’re utilizing AWS CloudFront for content delivery, remember that updates might not reflect immediately due to caching. You may need to create an invalidation to clear the cache for updated content to appear. Navigate to your CloudFront distribution, go to the ‘Invalidations’ tab, and create an invalidation by entering the path of your updated files (use to invalidate all files). /* Step 5: Testing After updating files and settings, visit your website to confirm that changes are live and functioning as expected. Test on different devices and browsers to ensure compatibility and proper display. Celebration Time: You’re Live! Congratulations on successfully navigating the digital waves to launch your shiny, new website! Your virtual real estate is now up, running, and ready to welcome visitors from around the globe, securely and swiftly. This journey, while seemingly daunting, has brought you from domain registration with GoDaddy to secure, static website hosting on AWS S3, all the way to deploying with CloudFront for that extra speed and security layer. Cheers to your success! 🚀🎉

Bridging Domains:How to Migrate From GoDaddy to AWS S3 in Style!

ব্রিজিং ডোমেন: GoDaddy থেকে AWS S3-এ স্টাইলে কীভাবে স্থানান্তর করা যায়!

Überbrückung von Domänen: So migrieren Sie stilvoll von GoDaddy zu AWS S3!

Puente de dominios: ¡Cómo migrar de GoDaddy a AWS S3 con estilo!

Pontage de domaines : comment migrer de GoDaddy vers AWS S3 avec style !

ब्रिजिंग डोमेन: स्टाइल में GoDaddy से AWS S3 पर कैसे माइग्रेट करें!

ドメインのブリッジング:GoDaddy から AWS S3 にスタイリッシュに移行する方法!

도메인 브리징:GoDaddy에서 AWS S3로 스타일리쉬하게 마이그레이션하는 방법!

Bridging Domains:Como migrar do GoDaddy para o AWS S3 com estilo!

Соединение доменов: как стильно перейти с GoDaddy на AWS S3!

Etki Alanları Arasında Köprü Oluşturma: GoDaddy'den AWS S3'e Şık Bir Şekilde Nasıl Geçiş Yapılır?

Kết nối miền: Cách di chuyển từ GoDaddy sang AWS S3 thật phong cách!

桥接域：如何时尚地从 GoDaddy 迁移到 AWS S3！

ERA II. WHITSUNTIDE

The Big Four by Agatha Christie, is part of the HackerNoon Books Series. You can jump to any chapter in this book here . WE INVESTIGATE AT CROFTLANDS X. WE INVESTIGATE AT CROFTLANDS The Scotland Yard Inspector was, indeed, waiting on the platform, and greeted us warmly. "Well, Moosior Poirot, this is good. Thought you'd like to be let in on this. Tip-top mystery, isn't it?" I read this aright as showing Japp to be completely puzzled and hoping to pick up a pointer from Poirot. Japp had a car waiting, and we drove up in it to Croftlands. It was a square, white house, quite unpretentious, and covered with creepers, including the starry yellow jasmine. Japp looked up at it as we did. "Must have been balmy to go writing that, poor old cove," he remarked. "Hallucinations, perhaps, and thought he was outside." Poirot was smiling at him. "Which was it, my good Japp?" he asked; "accident or murder?" The Inspector seemed a little embarrassed by the question. "Well, if it weren't for that curry business, I'd be for accident every time. There's no sense in holding a live man's head in the fire—why, he'd scream the house down." "Ah!" said Poirot in a low voice. "Fool that I have been. Triple imbecile! You are a cleverer man than I am, Japp." Japp was rather taken aback by the compliment—Poirot being usually given to exclusive self praise. He reddened and muttered something about there being a lot of doubt about that. He led the way through the house to the room where the tragedy had occurred—Mr. Paynter's study. It was a wide, low room, with book-lined walls and big leather arm-chairs. Poirot looked across at once to the window which gave upon a gravelled terrace. "The window, it was unlatched?" he asked. "That's the whole point, of course. When the doctor left this room, he merely closed the door behind him. The next morning it was found locked. Who locked it? Mr. Paynter? Ah Ling declares that the window was closed and bolted. Dr. Quentin, on the other hand, has an impression that it was closed, but not fastened, but he won't swear either way. If he could, it would make a great difference. If the man was murdered, some one entered the room either through the door or the window—if through the door, it was an inside job; if through the window, it might have been any one. First thing when they had broken the door down, they flung the window open, and the housemaid who did it thinks that it wasn't fastened, but she's a precious bad witness—will remember anything you ask her to!" "What about the key?" "There you are again. It was on the floor among the wreckage of the door. Might have fallen from the keyhole, might have been dropped there by one of the people who entered, might have been slipped underneath the door from the outside." "In fact everything is 'might have been'?" "You've hit it, Moosior Poirot. That's just what it is." Poirot was looking round him, frowning unhappily. "I cannot see light," he murmured. "Just now—-yes, I got a gleam, but now all is darkness once more. I have not the clue—the motive." "Young Gerald Paynter had a pretty good motive," remarked Japp grimly. "He's been wild enough in his time, I can tell you. And extravagant. You know what artists are, too—no morals at all." Poirot did not pay much attention to Japp's sweeping strictures on the artistic temperament. Instead he smiled knowingly. "My good Japp, is it possible that you throw the mud in my eyes? I know well enough that it is the Chinaman you suspect. But you are so artful. You want me to help you—and yet you drag the red kipper across the trail." Japp burst out laughing. "That's you all over, Mr. Poirot. Yes, I'd bet on the Chink, I'll admit it now. It stands to reason that it was he who doctored the curry, and if he'd try once in an evening to get his master out of the way, he'd try twice." "I wonder if he would," said Poirot softly. "But it's the motive that beats me. Some heathen revenge or other, I suppose." "I wonder," said Poirot again. "There has been no robbery? Nothing has disappeared? No jewellery, or money, or papers?" "No—that is, not exactly." I pricked up my ears; so did Poirot. "There's been no robbery, I mean," explained Japp. "But the old boy was writing a book of some sort. We only knew about it this morning when there was a letter from the publishers asking about the manuscript. It was just completed, it seems. Young Paynter and I have searched high and low, but can't find a trace of it—he must have hidden it away somewhere." Poirot's eyes were shining with the green light I knew so well. "How was it called, this book?" he asked. "The Hidden Hand in China, I think it was called." "Aha!" said Poirot, with almost a gasp. Then he said quickly, "Let me see the Chinaman, Ah Ling." The Chinaman was sent for and appeared, shuffling along, with his eyes cast down, and his pigtail swinging. His impassive face showed no trace of any kind of emotion. "Ah Ling," said Poirot, "are you sorry your master is dead?" "I welly sorry. He good master." "You know who kill him?" "I not know. I tell pleeceman if I know." The questions and answers went on. With the same impassive face, Ah Ling described how he had made the curry. The cook had had nothing to do with it, he declared, no hand had touched it but his own. I wondered if he saw where his admission was leading him. He stuck to it too, that the window to the garden was bolted that evening. If it was open in the morning, his master must have opened it himself. At last Poirot dismissed him. "That will do, Ah Ling." Just as the Chinaman had got to the door, Poirot recalled him. "And you know nothing, you say, of the Yellow Jasmine?" "No, what should I know?" "Nor yet of the sign that was written underneath it?" Poirot leant forward as he spoke, and quickly traced something on the dust of a little table. I was near enough to see it before he rubbed it out. A down stroke, a line at right angles, and then a second line down which completed a big 4. The effect on the Chinaman was electrical. For one moment his face was a mask of terror. Then, as suddenly, it was impassive again, and repeating his grave disclaimer, he withdrew. Japp departed in search of young Paynter, and Poirot and I were left alone together. "The Big Four, Hastings," cried Poirot. "Once again, the Big Four. Paynter was a great traveller. In his book there was doubtless some vital information concerning the doings of Number One, Li Chang Yen, the head and brains of the Big Four." "But who—how—" "Hush, here they come." Gerald Paynter was an amiable, rather weak-looking young man. He had a soft brown beard, and a peculiar flowing tie. He answered Poirot's questions readily enough. "I dined out with some neighbours of ours, the Wycherlys," he explained. "What time did I get home? Oh, about eleven. I had a latch-key, you know. All the servants had gone to bed, and I naturally thought my uncle had done the same. As a matter of fact, I did think I caught sight of that soft-footed Chinese beggar Ah Ling just whisking round the corner of the hall, but I fancy I was mistaken." "When did you last see your uncle, Mr. Paynter? I mean before you came to live with him." "Oh! not since I was a kid of ten. He and his brother (my father) quarrelled, you know." "But he found you again with very little trouble, did he not? In spite of all the years that had passed?" "Yes, it was quite a bit of luck my seeing the lawyer's advertisement." Poirot asked no more questions. Our next move was to visit Dr. Quentin. His story was substantially the same as he had told at the inquest, and he had little to add to it. He received us in his surgery, having just come to the end of his consulting patients. He seemed an intelligent man. A certain primness of manner went well with his pince-nez, but I fancied that he would be thoroughly modern in his methods. "I wish I could remember about the window," he said frankly. "But it's dangerous to think back, one becomes quite positive about something that never existed. That's psychology, isn't it, M. Poirot? You see, I've read all about your methods, and I may say I'm an enormous admirer of yours. No, I suppose it's pretty certain that the Chinaman put the powdered opium in the curry, but he'll never admit it, and we shall never know why. But holding a man down in a fire—that's not in keeping with our Chinese friend's character, it seems to me." I commented on this last point to Poirot as we walked down the main street of Market Handford. "Do you think he let a confederate in?" I asked. "By the way, I suppose Japp can be trusted to keep an eye on him?" (The Inspector had passed into the police station on some business or other.) "The emissaries of the Big Four are pretty spry." "Japp is keeping an eye on both of them," said Poirot grimly. "They have been closely shadowed ever since the body was discovered." "Well, at any rate we know that Gerald Paynter had nothing to do with it." "You always know so much more than I do, Hastings, that it becomes quite fatiguing." "You old fox," I laughed. "You never will commit yourself." "To be honest, Hastings, the case is now quite clear to me—all but the words, Yellow Jasmine—and I am coming to agree with you that they have no bearing on the crime. In a case of this kind, you have got to make up your mind who is lying. I have done that. And yet—" He suddenly darted from my side and entered an adjacent bookshop. He emerged a few minutes later, hugging a parcel. Then Japp rejoined us, and we all sought quarters at the inn. I slept late the next morning. When I descended to the sitting-room reserved for us, I found Poirot already there, pacing up and down, his face contorted with agony. "Do not converse with me," he cried, waving an agitated hand. "Not until I know that all is well—that the arrest is made. Ah! but my psychology has been weak. Hastings, if a man writes a dying message, it is because it is important. Every one has said—'Yellow Jasmine? There is yellow jasmine growing up the house—it means nothing.'" "Well, what does it mean? Just what it says. Listen." He held up a little book he was holding. "My friend, it struck me that it would be well to inquire into the subject. What exactly is yellow jasmine? This little book has told me. Listen." He read. "'Gelsemini Radix. Yellow Jasmine. Composition: Alkaloids gelseminine C22H26N2O3, a potent poison acting like coniine; gelsemine C12H14NO2, acting like strychnine; gelsemic acid, etc. Gelsemium is a powerful depressant to the central nervous system. At a late stage in its action it paralyses the motor nerve endings, and in large doses causes giddiness and loss of muscular power. Death is due to paralysis of the respiratory centre.' "You see, Hastings? At the beginning I had an inkling of the truth when Japp made his remark about a live man being forced into the fire. I realised then that it was a dead man who was burned." "But why? What was the point?" "My friend, if you were to shoot a man, or stab a man after he were dead, or even knock him on the head, it would be apparent that the injuries were inflicted after death. But with his head charred to a cinder, no one is going to hunt about for obscure causes of death, and a man who has apparently just escaped being poisoned at dinner, is not likely to be poisoned just afterwards. Who is lying, that is always the question? I decided to believe Ah Ling—" "What!" I exclaimed. "You are surprised, Hastings? Ah Ling knew of the existence of the Big Four, that was evident—so evident that it was clear he knew nothing of their association with the crime until that moment. Had he been the murderer, he would have been able to retain his impassive face perfectly. So I decided then, to believe Ah Ling, and I fixed my suspicions on Gerald Paynter. It seemed to me that Number Four would have found an impersonation of a long lost nephew very easy." "What!" I cried. "Number Four?" "No, Hastings, not Number Four. As soon as I had read up the subject of yellow jasmine, I saw the truth. In fact, it leapt to the eye." "As always," I said coldly, "it doesn't leap to mine." "Because you will not use your little gray cells. Who had a chance to tamper with the curry?" "Ah Ling. No one else." "No one else? What about the doctor?" "But that was afterwards." "Of course it was afterwards. There was no trace of powdered opium in the curry served to Mr. Paynter, but acting in obedience to the suspicions Dr. Quentin had aroused, the old man eats none of it, and preserves it to give to his medical attendant, whom he summons according to plan. Dr. Quentin arrives, takes charge of the curry, and gives Mr. Paynter an injection—of strychnine, he says, but really of yellow jasmine—a poisonous dose. When the drug begins to take effect, he departs, after unlatching the window. Then, in the night, he returns by the window, finds the manuscript, and shoves Mr. Paynter into the fire. He does not heed the newspaper that drops to the floor and is covered by the old man's body. Paynter knew what drug he had been given, and strove to accuse the Big Four of his murder. It is easy for Quentin to mix powdered opium with the curry before handing it over to be analysed. He gives his version of the conversation with the old man, and mentions the strychnine injection casually, in case the mark of the hypodermic needle is noticed. Suspicion at once is divided between accident and the guilt of Ah Ling owing to the poison in the curry." "But Dr. Quentin cannot be Number Four?" "I fancy he can. There is undoubtedly a real Dr. Quentin who is probably abroad somewhere. Number Four has simply masqueraded as him for a short time. The arrangements with Dr. Bolitho were all carried out by correspondence, the man who was to do locum originally having been taken ill at the last minute." At that minute, Japp burst in, very red in the face. "You have got him?" cried Poirot anxiously. Japp shook his head, very out of breath. "Bolitho came back from his holiday this morning—recalled by telegram. No one knows who sent it. The other man left last night. We'll catch him yet, though." Poirot shook his head quietly. "I think not," he said, and absent-mindedly he drew a big 4 on the table with a fork. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Agatha Christie (2023). The Big Four. Urbana, Illinois: Project Gutenberg. Retrieved https://www.gutenberg.org/cache/epub/70114/pg70114-images.html This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org , located at https://www.gutenberg.org/policy/license.html .

WE INVESTIGATE AT CROFTLANDS

The Quarantine at Alexander Abraham’s

ALL IN EXPECTATION

Someone commented on LinkedIn that the next big thing web3 startups need to focus on is creating a “ ” and it just triggered me the wrong way. minimum viable community I keep seeing people using this word like a child uttering a swear word for the first time and the parents hastily trying to stop it. Only their behavior delights the sprog and so they repeat it over and over, getting louder and louder, all the while everyone around them standing laughing as the parents crawl into a hole and die. Community the condition of sharing or having certain attitudes and interests in common. Customer a person who buys goods or services from a shop or business. Fandom the fans of a particular person, team, fictional series, etc. regarded collectively as a community or subculture. Cult a person or thing that is popular or fashionable among a particular group or section of society. I covered some of this before in but it’s clear it needs fucking repeating. Chapter 3 Definition — Community: a group of people living in the same place or having a particular characteristic in common. Or if you want to break it down, “a group of people living in the same place [echo chamber] or having a particular characteristic in common [being completely fucking gullible]”. I don’t understand posts that claim community, collaboration and co-opetition didn’t exist before web3. They have nothing to do with technology and everything to do with strategy and people. They existed, they always have. You are a customer of Starbucks. You don’t belong to a community. You don’t care about anyone else in that store when you order a latte. You are a customer of Mcdonald’s. You don’t belong to a community. You don’t care about anyone else in that restaurant when you order that burger. You can’t even call yourselves fans. Consumers don’t think how they feel. They don’t say what they think and they don’t do what they say.” — David Ogilvy In these examples, there’s a killer point that I don’t think a lot appreciate — habit. Habits drive a lot more behavior than people realize. When they see others form a habit it encourages a network effect. There’s also one more — blanket coverage. McDonald's and Starbucks are everywhere. There are hundreds of variations of Colgate toothpaste that are all the same just with different packaging and it’s a tactic to shut out other brands from being front of mind. You’re therefore being conditioned to form a habit around a choice you no longer have the freedom to make. You are just a customer with a habit you didn’t ask for. You’re not part of a community. You’re not part of a fandom. But you could argue that the conditioning you’ve experienced is nothing less than cult-like. Sounds a lot like the fever surrounding Bored Apes and Axie Infinity to me. Steve Jobs didn’t famously say “ ” for example and for good reason which I’ll explain below. So many investors have fallen foul of this community phenomenon by using it as a yardstick for the quality of the project. Morons. start with the community and work backward to the technology Let me regale you a tale of yore, precisely 20 years ago in fact. I owned a slightly modded Subaru Impreza Turbo. They were great cars, and it was in Sonic Blue, the same color as the UK P1 variant. I joined , a BBS forum for owners of all things Subaru, and set about learning everything I could about the cars, modifications, etc. Scoobynet I spent hours talking to people from all over the world. I bought secondhand parts from some to modify the car further. I posted about spotting other Scooby’s on the road so I could connect to them and say ‘hi’. We flashed our headlights at each other when we passed one another. We met up in groups and, well, just talked and had fun. Even when I had surgery for a back problem I loaned the car out to one of them whom I’d never met in real life to basically keep the car running tip-top instead of seizing up on the driveway. This is what a group of passionately random people do when they congregate over something they share a love for. Yes, it all sounds incredibly sad but this is community. We’ve existed for some time, odd that. Even in the games industry, as toxic as it can get, there are players who form genuine communities and bonds to the point they become lifelong friends. Harley Davidson is another such example where you don’t just own a product, you become part of one of the planet’s biggest communities much in the same way I did with my Subaru. And when one of them dies they mourn. And they all mourn collectively. You should be lucky to experience hundreds of Harleys thundering down the street to pay their last respects, tens of modified Subarus with that exhaust burble, or hundreds of players who log on and all travel to one location in the game to share their memories of a friend. They all make the headlines. Now let’s turn our attention to what Web3 is about and all this bullshit about community. Because it’s not community. It’s a cult. It’s easy to confuse the two, you’re sharing common interests but at the moment the difference is pretty obvious — web3 and everything it brings to the table is just fashionable for a lot of people without any real connection. You can tell instantly who is really a part of a community or just part of a cult every time to log into a Discord server. The talk is never about sharing personal stories or genuinely being interested in what’s going on with others — it’s about when the next NFT drop is, how best to pump the token, or how to create a pyramid scheme to make money from the next poor sap who can’t afford the buy-in. Owning a Discord server or a bunch of Twitter bots does not equate to a community, and yet so many naive investors fall for this trick. A community actively adds value to whatever it’s attached to, like a community of developers working on an open-source project to improve the software. How many so-called communities are actually just filled with passive lurkers who live vicariously through the actions of others? They cheer from the sidelines but never actively take part or have even bought into the service or project they’re fervently passionate about. Again, how many investors so desperate to have a windfall in Web3 have fallen for this as proof of market validation? How many hodlers will turn up at the funeral of Ape#34574.5 I wonder…fuck all is the most likely answer. Who’s going to care if Moonbird #2342 fell off her bike and broke her back? “Hey everyone, doctors think I’ll never walk again.” WAGMI! People in Web3 are almost like a new segmentation, they sit between being a customer and being the product. They are a byproduct of being part of a cult with the delusion of being a community. It’s not the minimum viable community you’re creating, it’s a minimum viable cult. And you can buy them cheap because a community will stick by you, cults just migrate from one fashionable lure to another for the promise of something better than the last. I’m being harsh of course but for good reason. You can’t even claim to be part of fandom for example because you pump and dump so fast you don’t even care whether a project lives or dies, or care enough to still be a fan years later and admit it. How many of us are still fans of defunct TV shows that passed into shadow long ago but we still talk about them, defend them, and yearn for just one more season or a reboot? ( ) yeah, I’m talking about Firefly lol How many of you will still talk about Mfers or some other shitty PFP project in 5 years time when it inevitably goes tits up and is worthless? “In 1.0, your community is IRL and based on things like where you were born, where you went to school, what sports team you supported, etc. In 2.0, your community was a URL, where you joined interest-based online groups across Facebook, Reddit, Discord, etc. In 3.0, the community is all about ownership. Being part of a community means you’re providing funding to run the community and gaining transparency and voting power.” Do you hear yourselves when you say this out loud? Do you think Starbucks is going to invite you to the next investors' call and ask your opinion just because you joined their new NFT rewards program? And do you finally recognize that Web2 brands using pseudo-web3 principles and technologies are still Web2?! Or are you all part of a cult that’s brainwashed you into thinking you’re really part of a community only to abandon you as soon as the grass turns a different shade of green on that next plot of land in The Sandbox? Also published . here

Dear Web3, You Don’t Have A Community, You Have A Cult

Querido Web3, No tienes una comunidad, tienes un culto

David Copperfield: Chapter 39 - Wickfield And Heep

For the Story Teller: Story Telling and Stories to Tell, by Carolyn Sherwin Bailey is part of HackerNoon Books Series
. You can jump to any chapter in this book here . The Three Cakes The Three Cakes Once upon a time there was a little boy named Henry, who was away from his home at a boarding school. He was a very special kind of boy, forever at his book, and he happened once to get to the very tip top of his class. His mother was told of it, and when it came morning, she got up early and went to speak with the cook as follows: “Cook, you are to make a cake for Henry, who has been very good at school.” “With all my heart,” said the cook, and she made a cake. It was as big as—let me see—as big as the moon. It was stuffed with nuts, and raisins, and figs, and candied fruit peel, and over it all was an icing of sugar, thick, and smooth, and very white. And no sooner was the cake home from the baking than the cook put on her bonnet and carried it to the school. When Henry first saw it, he jumped up and down. He was not patient enough to wait for a knife, but he fell upon the cake tooth and nail. He ate and ate until school began, and after school was over he ate again with his might and main. At night he ate until bedtime, and he put the cake under his bolster when he went to bed and he waked and waked a dozen times that he might take a bite. But the next day when the dinner bell rang, Henry was not hungry, and was vexed to see how heartily the other children ate. His friends asked him if he would not play at cricket, tan, or kits. Ah! Henry could not; so they played without him, and Henry could scarcely stand upon his legs. He went and sat down in a corner, and the head master sent for the apothecary to come with all his phials of physic. After some days Henry was well again, but his mother said that she would never let him have another cake. Now there was another scholar in the same school, whose name was Francis. He had written his mother a very pretty letter without one misspelled word or blot, and so his mother, like the mother of Henry, sent him a great cake. Francis decided that he would not be so unwise as to follow the example of Henry, so he took the cake, which was so heavy that he could hardly lift it, and he watched to see that no one was looking, and he slipped up to his chamber and put the cake in his box under lock and key. Every day at play time he used to slip away from his companions, go upstairs on tiptoe, and cut off a tolerable slice of his cake which he would eat by himself. For a whole week did he keep this up, but alas—the cake was so exceedingly large! At last the cake grew dry, and quickly after it became moldy. Finally the maggots got into it, and Francis, with great reluctance, was obliged to throw it away. There was a third little gentleman who went to the same school as Henry and Francis, and his name was Gratian. One day his mother, whom he loved very dearly, sent him a cake because she also loved him. No sooner had it arrived than Gratian called his friends all about him, and said: “Come! Look at what my mother has sent me. You must, each one, have a piece.” So the children all got around the cake as bees resort to a flower, just blown, and Gratian divided the cake with a knife into as many pieces as he had invited boys, with one piece over, for himself. His own piece he said he would eat the next day, and he began playing games with the boys. But a very short time had passed, as they were playing, when a poor man who was carrying a fiddle came into the school yard. He had a very long, gray beard, and he was guided by a little dog who went before him, for the old man was blind. The children noticed how dexterous was the little dog in leading, and how he shook a bell which hung underneath his collar, as if to say: “Do not throw down or run against my master!” When the two had come into the yard, the old man sat down upon a stone, and said: “My dear little gentlemen, I will play you all the pretty tunes that I know, if you will give me leave.” The children wished for nothing half so much as to hear the music, so the old man put his violin in tune and then played over jigs and tunes that had been new in former times. But Gratian, who was standing close to him, noticed that while he played his jolliest airs, a tear would often roll down his cheeks. And Gratian asked him why he wept. “Because,” said the old man, “I am hungry. I have not any one in the world to feed me, or my faithful dog.” Then Gratian felt like crying, too, and he ran to fetch the cake which he had saved to eat himself. He brought it out with joy, and as he ran along he said: “Here, good man, here is some cake for you.” Then Gratian put the cake into the old man’s hands and he, laying down his fiddle, wiped his eyes and began to eat. At every piece he put into his mouth he gave a bit to his faithful little dog, who ate from his hand; and Gratian, standing by, had as much pleasure as if he had eaten the cake himself. From the French of Monsieur Berquin’s L’Ami des Enfants—1784 About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Bailey, Carolyn Sherwin. 2018. For the Story Teller: Story Telling and Stories to Tell. Urbana, Illinois: Project Gutenberg. Retrieved April 2022 from https://www.gutenberg.org/files/58107/58107-h/58107-h.htm#Page_35 This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org , located at https://www.gutenberg.org/policy/license.html .

Stories for Telling: The Three Cakes

Stories, News & Mentions about TIPTOP

Tiptop’s Stories on HackerNoon