FortMesa

fortmesa

Startups of The Year 2023 Winners: North America 

Let's cut through the noise: Our state, this intricate socioeconomic and political beast, is nothing but a fortress manned by relentless gatekeepers. They stand guard, ensuring that groundbreaking technologies like AI remain mere spectators in the grand play of employment, growth, and stability.This state we're in? It's a Kafkaesque nightmare, a convoluted labyrinth where rules, regulations, and pretentious power plays thrive. It's a world where money speaks, contracts bind, and patents choke creativity. Everything, from the smallest code to the largest border, is caged within this colossal castle where size does, unfortunately, matter. And the purpose of this grand design? It's to perpetuate the gatekeepers, to breed an army of them under the guise of jobs and progress. Yet, the irony! Many don't even see themselves as gatekeepers anymore. They've donned the masks of knowledge workers, researchers, project managers - but the gates they guard? Oh, they're as real as the money they covet, the interest they demand, and the copyright they fiercely protect. These gatekeepers, they create zilch of real value. That's why economic forces barely graze them. Invent a computer to replace a million clerks? Watch them smirk as they double the number of clerks, erecting more gates, more barriers. What's the epitome of this gatekeeping farce? Look no further than the crypto world. It started as a wild west of innovation, free from the clutches of traditional gatekeeping. Yet, what happened? Mining pools morphed into mini fortresses, regulators swarmed in demanding compliance, KYC, anti-money laundering measures – you name it. And soon, only a few big players got the golden ticket, building their own walls and charging entry at their shiny new gates. Even the bigwigs in AI are eyeing the government, craving their own set of walls and gates. And let's not forget the ultimate gate: Money. The government, ever so generously, distributes banking licenses while the banks, in their ivory towers, demand ludicrous entry fees.It's a world where innovation suffocates under the weight of gatekeeping, where progress is but a distant dream. The state, with its army of gatekeepers, ensures that. My point is that technology will not replace jobs in a state of gatekeepers. note: . ChatGPT did a edit of this article - I asked it for a more bloggish tone. I changed a few things after

The State: A Fortress of Gatekeepers Crushing Innovation

In today’s digital age, data is like gold – precious and worth protecting. For HR platforms, this couldn’t be truer. Let's dive into why your company’s HR system needs to be Fort Knox for employee data. Why is HR Data so Darn Important? : Think about what your HR system knows about you – it's like a biography, with details from your birthday to your bank account. Personal Info on Display : It also knows what you earn, which is pretty hush-hush. Salary Secrets : Plus, it holds the financial secrets of the business. The Company's Treasure Chest The Boogeymen of Data Security : Just like in the movies, there are bad guys trying to sneak a peek at your data. Hackers and Leaks : Places like the EU have put up big stop signs like GDPR to slap fines on anyone playing fast and loose with personal data. Tough Rules Building an HR Fortress The Must-Haves for Top-Notch Security : Certifications like ISO27001 and ISO27018 are not just fancy numbers – they're like global hall passes for trust. International Security Badges : These are like the bouncers at the club, making sure everything inside is safe and sound. SOC2 and SOC1 Certs Inside the Fortress: Safeguards You Need : Set up VIP lists – only let certain eyes (like your boss or HR) see the super-secret stuff. Who Can Peek at Your Data? : This scrambles your data into a secret code that only the right key can unlock. Data Encryption Knock Before You Enter: The Consent Rule : Well, not exactly. But if someone needs to fix a bug, they need to ring the doorbell and ask nicely (i.e., get your permission). Polite Hackers? Playing Nice with Others: Third-Party Integrations : Just like you wouldn't let just anyone join your group project, the HR system checks if other software is cool enough (read: secure enough) to join the party. The Friend Vetting Process The HR Security Checklist ✅ Does your HR platform have the global security hall passes (ISO27001 and ISO27018)? ✅ Are the bouncers (SOC2/SOC1) in place? ✅ Can you set a VIP data viewing list? ✅ Is your data in secret code (encrypted)? ✅ Do you ask for a permission slip before someone digs around (consent protocols)? ✅ Are your software buddies (third-party integrations) checked for cooties (security risks)? Understanding all this can seem as tough as learning a new language. But just like locking your doors at night, these steps are what keep your HR data as safe as sleeping dragons. So, let’s make sure your HR platform is more than just a database – it's a digital fortress. HiBob's Vision: A Masterclass in HR Data Security and Efficiency In an era where data is both currency and commodity, securing HR information is paramount. HiBob has pioneered a solution that not only streamlines HR operations but embeds security into its very DNA. The platform, affectionately known as Bob, has been engineered to marry intuitiveness with robust security, ensuring that every stakeholder, from HR professionals to managers and employees, interacts with a system that is as secure as it is easy to use. Let’s delve into how HiBob has redefined the nexus of HR convenience and security. Intuitive and Robust: The Pillars of HiBob's Platform : Bob is meticulously crafted to provide a seamless user experience. The interface is intuitive, meaning less time spent on training and more on productivity. Yet, beneath this ease of use lies a sophisticated security infrastructure. User-Friendly Design : Accessibility does not compromise security on this platform. HiBob has integrated advanced security measures that work silently in the background, providing powerful protection without disrupting the user experience. Accessible Yet Secure Insights and Resources: The Tools for Building an Inclusive Culture : With Bob, your organization can harness the power of data without the risk of exposure. The platform provides a wealth of insights and analytics, allowing for informed decision-making that is crucial in crafting an inclusive company culture. Data-Driven Decision Making : HR documentation is a trove of sensitive information. Bob’s document management system is not just about storage; it's about secure access, with automated reporting that upholds the highest standards of data security. Secure Document Management Building Trust: The Onboarding to Offboarding Journey : The onboarding process sets the tone for an employee's journey. HiBob ensures this is a positive experience, with a focus on security from the get-go. Personal details are encrypted and kept confidential, providing peace of mind for new hires. A Secure Start : Bob’s 360-degree performance reviews are conducted within a secure ecosystem. Feedback and personal development plans remain confidential, fostering an environment where employees feel safe to grow and succeed. Continuous Development in a Protected Environment Fair and Secure Compensation Management: Transparency Meets Confidentiality : Compensation management requires a delicate balance. With Bob, this process is flexible for HR and transparent for employees, yet all personal data remains under strict digital lock and key. Flexible Yet Firm : HiBob’s commitment to equity is evident in its compliance features, ensuring that compensation management upholds fairness and confidentiality. Compliance With Fair Pay Practices The Pulse of Your Organization: Secured Feedback Channels : Surveys are vital for gauging employee engagement, but they also contain sensitive responses. Bob’s survey tools are designed to gather this feedback securely, ensuring that personal opinions don't become public knowledge. Confidential Surveys Time Management: Privacy in Every Second : Time management is a fundamental HR function, and Bob handles it with discretion. Requests for time off and attendance tracking are processed in a way that respects employee privacy at every turn. Sensitive Scheduling Payroll with Privacy: The Art of Secure Processing : Payroll is complex, but Bob simplifies it. The Payroll Hub is a testament to HiBob’s commitment to security, ensuring that personal and financial details are processed securely, in real-time, and in compliance with regulatory standards. Simplified Payroll Journey Analytics with Anonymity : People Analytics in Bob offers a deep dive into your workforce's metrics while safeguarding individual data, allowing for informed decisions without compromising privacy. Actionable Insights Without Exposure A Safe Space for Speaking Up : Bob's Your Voice module offers a secure channel for employees to report concerns in alignment with whistleblower protection laws. Empowerment Without Exposure Strategic Workforce Planning : Workforce planning tools within Bob help map out future hiring needs using current data, all while maintaining strict data confidentiality. Forward Planning with Backward Privacy A Sandbox for Secure Experimentation : Bob’s Sandbox allows you to test changes and simulate events in a secure environment, ensuring that the integrity of your live data is never compromised. Risk-Free Exploration For a detailed dive into the HiBob data security measures and why it's the fortress your HR data needs, visit their page HiBob data security HiBob: A Secure, Intuitive Revolution In the age where data breaches are as common as coffee breaks, HiBob emerges as the guardian of your company’s most valuable asset - its people's information. With its finger on the pulse of the latest in data security, HiBob’s platform, Bob, does more than just secure data; it empowers businesses to foster a culture of trust and innovation. Closing the Gap Between Security and Usability HiBob has meticulously woven security into the very fabric of its HR platform, ensuring that every module, from onboarding to compensation, is a bastion of data protection. Yet, the beauty of Bob lies in its simplicity - a testament to the fact that world-class security can go hand-in-hand with a seamless user experience. Secure, Empowered, Connected Through Bob, HiBob demonstrates a commitment to security that is unyielding, to employee empowerment that is unparalleled, and to a connected ecosystem that is unmatched. Bob stands as a testament to what HR platforms should aspire to be - secure, intuitive, and endlessly supportive of growth. Secure Today, Success Tomorrow As we wrap up this exploration into the secure expanses of HiBob’s platform, remember that in a world rife with digital risks, the right HR platform is not a luxury but a necessity. It's about choosing a partner who values your data as much as you do, a system that stands resilient against the tides of cyber threats, and a solution that grows with you, securely and robustly. With HiBob, you’re not just choosing an HR platform; you’re choosing peace of mind. You're choosing a future where data security and compliance are given, not a goal. So, as you navigate the challenges and opportunities of the modern workplace, let HiBob’s Bob be the compass that guides you to a secure harbor, every time. Visit to learn more about how HiBob is redefining HR data security, one secure, intuitive step at a time. Because when it comes to your data, good enough is not enough; it has to be the best. And with HiBob, the best is what you get. HiBob data security Strategic HR Data Management Within the competitive landscape of HR technology solutions, HiBob's platform, distinguishes itself not merely as an aggregate of features but as an integrated, strategic solution. It's engineered to fortify the most confidential employee data while delivering an experience that is not only intuitive but also seamlessly aligned with the user’s needs. Bob stands as a paragon of trust in the digital HR sphere, adeptly navigating the intricate nexus between user accessibility and stringent data security protocols. Bob: A Technologically Advanced Partner in HR Strategy : HiBob recognizes the imperative of safeguarding personal and sensitive data, embedding advanced encryption and access control measures that operate with the subtlety required in HR systems. Data Confidentiality : In the milieu of evolving compliance demands, Bob is designed to remain compliant with international standards, such as GDPR, reflecting a deep understanding of global compliance landscapes and the complexities therein. Regulatory Compliance : The platform's architecture is the epitome of sophisticated design principles, prioritizing UX without sacrificing the rigors of data security—a duality that caters to the discerning standards of MBA-level professionals. User Experience (UX) Operational Excellence in HR Data Security : Bob's infrastructure is architected for resilience, maintaining data integrity and confidentiality across all facets of HR management—from entry and storage to analytics and reporting. System Design : The platform's security framework is interlaced within its operational fabric, ensuring real-time protection and proactive risk management in all HR processes. Integrated Security HiBob's Innovation: A Convergence of Security and Usability : Bob exemplifies HiBob's innovative spirit, where the integration of robust security measures within a user-friendly interface is not an afterthought but a foundational element of the system’s design. Security-Usability Convergence : The platform is constructed with a foresight that anticipates potential security threats, ensuring proactive measures are in place to mitigate risks before they materialize. Forward-Thinking Architecture Conclusion: HiBob's Platform as the HR Data Vanguard In sum, HiBob's platform, Bob, is a contemporary digital stronghold, a beacon for organizations that prioritize the security of their HR data while advancing their strategic HR goals. It is a revolutionary instrument that reassures leaders of the security of their HR operations, ensuring the integrity of data is unimpeachable as the organization embarks on initiatives to engage and develop its workforce. With a security-first methodology interwoven with a user-centric interface, Bob is not just a tool but a strategic asset, ensuring that your HR data strategy is robust, compliant, and ahead of the curve.

Fortify Your HR Data with HiBob's Digital Fortress

HiBob এর ডিজিটাল ফোর্টেস দিয়ে আপনার HR ডেটাকে শক্তিশালী করুন

Stärken Sie Ihre HR-Daten mit der digitalen Festung von HiBob

Fortalezca sus datos de recursos humanos con Digital Fortress de HiBob

Fortifiez vos données RH avec la forteresse numérique de HiBob

HiBob के डिजिटल किले के साथ अपने HR डेटा को मजबूत करें

HiBob の Digital Fortress で人事データを強化する

HiBob의 Digital Fortress로 HR 데이터를 강화하세요

Fortaleça seus dados de RH com o Digital Fortress do HiBob

Укрепите свои кадровые данные с помощью Digital Fortress от HiBob

İK Verilerinizi HiBob'un Dijital Kalesi ile Güçlendirin

Củng cố dữ liệu nhân sự của bạn với Pháo đài kỹ thuật số của HiBob

使用 HiBob 的数字堡垒强化您的 HR 数据

On War by Carl Von Clausewitz, is part of the HackerNoon Books Series. You can jump to any chapter in this book here . Attack on Fortresses Book VII: Chapter XVII. Attack on Fortresses The attack on fortresses cannot of course come before us here in its aspect as a branch of the science of fortification or military works; we have only to consider the subject, first, in its relation to the strategic object with which it is connected; secondly, as regards the choice among several fortresses; and thirdly, as regards the manner in which a siege should be covered. That the loss of a fortress weakens the defence, especially in case it forms an essential part of that defence; that many conveniences accrue to the assailant by gaining possession of one, inasmuch as he can use it for magazines and depôts, and by means of it can cover districts of country cantonments, etc.; that if his offensive at last should have to be changed into the defensive, it forms the very best support for that defensive—all these relations which fortresses bear to theatres of war, in the course of a war, make themselves sufficiently evident by what has been said about fortresses in the book on the Defence, the reflection from which throws all the light required on these relations with the attack. In relation to the taking of strong places, there is also a great difference between campaigns which tend to a great decision and others. In the first, a conquest of this description is always to be regarded as an evil which is unavoidable. As long as there is yet a decision to be made, we undertake no sieges but such as are positively unavoidable. When the decision has been already given—the crisis, the utmost tension of forces, some time passed—and when, therefore, a state of rest has commenced, then the capture of strong places serves as a consolidation of the conquests made, and then they can generally be carried out, if not without effort and expenditure of force, at least without danger. In the crisis itself the siege of a fortress heightens the intensity of the crisis to the prejudice of the offensive; it is evident that nothing so much weakens the force of the offensive, and therefore there is nothing so certain to rob it of its preponderance for a season. But there are cases in which the capture of this or that fortress is quite unavoidable, if the offensive is to be continued, and in such case a siege is to be considered as an intensified progress of the attack; the crisis will be so much greater the less there has been decided previously. All that remains now for consideration on this subject belongs to the book on the plan of the war. In campaigns with a limited object, a fortress is generally not the means but the end itself; it is regarded as a small independent conquest, and as such has the following advantages over every other:— 1. That a fortress is a small, distinctly-defined conquest, which does not require a further expenditure of force, and therefore gives no cause to fear a reaction. 2. That in negotiating for peace, its value as an equivalent may be turned to account. 3. That a siege is a real progress of the attack, or at least seems so, without constantly diminishing the force like every other advance of the offensive. 4. That the siege is an enterprise without a catastrophe. The result of these things is that the capture of one or more of the enemy’s strong places, is very frequently the object of those strategic attacks which cannot aim at any higher object. The grounds which decide the choice of the fortress which should be attacked, in case that may be doubtful, generally are— (a) That it is one which can be easily kept, therefore stands high in value as an equivalent in case of negotiations for peace. (b) That the means of taking it are at hand. Small means are only sufficient to take small places; but it is better to take a small one than to fail before a large one. (c) Its strength in engineering respects, which obviously is not always in proportion to its importance in other respects. Nothing is more absurd than to waste forces before a very strong place of little importance, if a place of less strength may be made the object of attack. (d) The strength of the armament and of the garrison as well. If a fortress is weakly armed and insufficiently garrisoned, its capture must naturally be easier; but here we must observe that the strength of the garrison and armament, are to be reckoned amongst those things which make up the total importance of the place, because garrison and armaments are directly parts of the enemy’s military strength, which cannot be said in the same measure of works of fortification. The conquest of a fortress with a strong garrison can, therefore, much more readily repay the sacrifice it costs than one with very strong works. (e) The facility of moving the siege train. Most sieges fail for want of means, and the means are generally wanting from the difficulty attending their transport. Eugene’s siege of Landreci, 1712, and Frederick the Great’s siege of Olmütz, 1758, are very remarkable instances in point. (f) Lastly, there remains the facility of covering the siege as a point now to be considered. There are two essentially different ways by which a siege may be covered: by entrenching the besieging force, that is, by a line of circumvallation, and by what is called lines of observation. The first of these methods has gone quite out of fashion, although evidently one important point speaks in its favour, namely, that by this method the force of the assailant does not suffer by division exactly that weakening which is so generally found a great disadvantage at sieges. But we grant there is still a weakening in another way, to a very considerable degree, because— 1. The position round the fortress, as a rule, is of too great extent for the strength of the army. 2. The garrison, the strength of which, added to that of the relieving army, would only make up the force originally opposed to us, under these circumstances is to be looked upon as an enemy’s corps in the middle of our camp, which, protected by its walls, is invulnerable, or at least not to be overpowered, by which its power is immensely increased. 3. The defence of a line of circumvallation admits of nothing but the most absolute defensive, because the circular order, facing outwards, is the weakest and most disadvantageous of all possible orders of battle, and is particularly unfavourable to any advantageous counter-attacks. There is no alternative, in fact, but to defend ourselves to the last extremity within the entrenchments. That these circumstances may cause a greater diminution of the army than one-third which, perhaps, would be occasioned by forming an army of observation, is easy to conceive. If, added to that, we now think of the general preference which has existed since the time of Frederick the Great for the offensive, as it is called, (but which, in reality, is not always so) for movements and manœuvres, and the aversion to entrenchments, we shall not wonder at lines of circumvallation having gone quite out of fashion. But this weakening of the tactical resistance is by no means its only disadvantage; and we have only reckoned up the prejudices which forced themselves into the judgment on the lines of circumvallation next in order after that disadvantage, because they are nearly akin to each other. A line of circumvallation only in reality covers that portion of the theatre of war which it actually encloses; all the rest is more or less given up to the enemy if special detachments are not made use of to cover it, in which way the very partition of force which it was intended to obviate takes place. Thus the besieging army will be always in anxiety and embarrassment on account of the convoys which it requires, and the covering the same by lines of circumvallation, is not to be thought of if the army and the siege supplies required are considerable, and the enemy is in the field in strong force, unless under such conditions as are found in the Netherlands, where there is a whole system of fortresses lying close to each other, and intermediate lines connecting them, which cover the rest of the theatre of war, and considerably shorten the lines by which transport can be affected. In the time of Louis the Fourteenth the conception of a theatre of war had not yet bound itself up with the position of an army. In the Thirty Years’ War particularly, the armies moved here and there sporadically before this or that fortress, in the neighbourhood of which there was no enemy’s corps at all, and besieged it as long as the siege equipment they had brought with them lasted, and until an enemy’s army approached to relieve the place. Then lines of circumvallation had their foundation in the nature of circumstances. In future it is not likely they will be often used again, unless where the enemy in the field is very weak, or the conception of the theatre of war vanishes before that of the siege. Then it will be natural to keep all the forces united in the siege, as a siege by that means unquestionably gains in energy in a high degree. The lines of circumvallation in the reign of Louis XIV., at Cambray and Valenciennes, were of little use, as the former were stormed by Turenne, opposed to Condé, the latter by Condé opposed to Turenne; but we must not overlook the endless number of other cases in which they were respected, even when there existed in the place the most urgent need for relief; and when the commander on the defensive side was a man of great enterprise, as in 1708, when Villars did not venture to attack the allies in their lines at Lille. Frederick the Great at Olmütz, 1758, and at Dresden, 1760, although he had no regular lines of circumvallation, had a system which in all essentials was identical; he used the same army to carry on the siege, and also as a covering army. The distance of the Austrian army induced him to adopt this plan at Olmütz, but the loss of his convoy at Domstädtel made him repent it; at Dresden in 1760 the motives which led him to this mode of proceeding, were his contempt for the German States’ imperial army, and his desire to take Dresden as soon as possible. Lastly, it is a disadvantage in lines of circumvallation, that in case of a reverse it is more difficult to save the siege train. If a defeat is sustained at a distance of one or more days’ march from the place besieged, the siege may be raised before the enemy can arrive, and the heavy trains may, in the mean time, gain also a day’s march. In taking up a position for an army of observation, an important question to be considered is the distance at which it should be placed from the besieged place. This question will, in most cases, be decided by the nature of the country, or by the position of other armies or corps with which the besiegers have to remain in communication. In other respects, it is easy to see that, with a greater distance, the siege is better covered, but that by a smaller distance, not exceeding a few miles, the two armies are better able to afford each other mutual support. 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. Carl von Clausewitz (2006). On War. Urbana, Illinois: Project Gutenberg. Retrieved https://www.gutenberg.org/cache/epub/1946/pg1946-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 .

Attack on Fortresses

Philochristus: Memoirs of a Disciple of the Lord by Edwin Abbott Abbott is part of the HackerNoon Books Series. You can jump to any chapter in this book . How, after the death of John the Prophet, Jesus foresaw that he also must be slain; and of the Bread of Life, and the feeding of the five thousand; and concerning the leaven of the Pharisees and Sadducees. here How, after the death of John the Prophet, Jesus foresaw that he also must be slain; and of the Bread of Life, and the feeding of the five thousand; and concerning the leaven of the Pharisees and Sadducees. Now so it was that, at this time, the more the hearts of the people were drawn toward Jesus (for though the people of Nazareth had rejected him, yet was he much honoured in the rest of Galilee), so much the more did Jesus seem to thrust them away. For he began to teach us at this time that he should give us no new law, but a certain manna or bread from heaven. Now if he had said no more than this, this was not hard to understand; for our Scribes also taught in parables after this fashion: but he added that this manna or bread from heaven should be himself, his flesh and his blood, which should be given for the life of the world. Now albeit I have myself heard the Scribes speak of “the days when Israel shall the Messiah,” meaning that Israel shall enjoy the presence of the Messiah, yet Jesus seemed to mean somewhat more than this, insomuch that his words were a stumbling-block unto many. And straightway many of them departed from him. eat 8 But when I went (according to my wont) to question Nathanael touching these words, he replied that they were hidden from him also. Notwithstanding it seemed to him that at this time our Master was receiving some new revelation, whereof these words might peradventure be a part. For he said that on the day before, when I had been absent, mention had been made of the coming Passover, and how Jesus would not be present thereat; and from mentioning the sacrifice of the Passover they came to speak of other sacrifices; and one said that Jesus had come to take away sacrifice, for that he had said that God desired mercy, and not sacrifice, and that the right sacrifice was that the whole nation should serve the Lord and do His will. Then another, quoting the Scripture, said, “Nay, but the people may perchance stand in the place of the fuel and the fire: but where is the lamb for the burnt-offering?” Then answered another from the same Scripture, and said, “God will provide himself a lamb for the burnt-offering.” And at these words, said John, “the countenance of Jesus changed as if he had heard some new word from God.” Hereat I marvelled greatly, and wondered what new thing the Lord was preparing for us and for our Master. And the words of Judas came to my mind that, because John the son of Zachariah had been slain, therefore Jesus had begun to imagine that he also must needs be slain. But it was but for an instant; for I durst not so much as entertain the thought of so great an evil. But, as I now judge, the Lord Jesus began at this time to see clearly that he must needs die for Israel, even as John the son of Zachariah had died, and that he must needs rise again (according to the Prophets); even as the common people spake, saying that John the Baptist was at this very time risen from the dead. For he perceived that the needs of the world, that is to say the will of the Father, required that he should rise again from the dead. Moreover as John the son of Zachariah had gained strength through death, so that all men still loved and honoured John, and were more ready to die for him dead than living; even so Jesus perceived that he also should have more strength to help us after his death than before his death. But touching the manner of his rising again, and the time of it, and whether he should appear in his own shape (as he did indeed), or in some other shape (as did Elias in the shape of John the Baptist), concerning all this, what was revealed unto him I know not; the Lord only knoweth. But that he should of a certainty rise again from the dead, this was without doubt revealed unto him; and, as I conceive, about this time. For this cause, because he perceived that by the giving of his body and blood to die for men, his spirit would pass into his disciples (even as the spirit of John the son of Zachariah had passed into the disciples of John), for this cause, I say, he spake at this time (as he did also afterwards), saying that he would give himself to be the food of men, even the Bread of Life. For his spirit was a spirit of sonship to God, and of brotherhood to men; and except the world should receive this spirit into itself, the world could not be quickened, and the nations of the earth could not pass into the family or kingdom of God. From this time also he began to be very careful, even to disquietude, concerning us his disciples, what should be our estate when he should have departed from us; and he desired to impart to us this Bread of Life that we also in turn might impart it to the multitude. Moreover he would fain exercise us already in imparting this Bread of Life, yea, before he had passed away; to the end that, by beginning in his presence, we might learn by degrees to be steadfast in the ministering of the Bread even though he were absent from us. And for this he found occasion not many days afterwards. For about the tenth day before the Passover, Jesus being still on the other side of the lake (but I had been sent with Judas on an errand to Capernaum), it came to pass that much people resorted to him; some from Capernaum, and others from the parts round about the village wherein he had lodged. For, because of the Passover, which was at hand, many were going up to Jerusalem. Also of the Galileans some came; howbeit not James nor Barabbas, nor any of them which had most authority with the Galileans. Now Jesus himself ministered unto certain of them the Bread of Life, and forgave sins, and healed the sick. But afterwards, because of the multitude of them which came unto him (for they were more than five thousand) he caused the disciples to divide them into companies and to minister the Bread unto the people. So they ministered as Jesus bade them, and the grace of the Lord was with them; insomuch that Thomas (who had been at the first loth to minister the Bread, as not being worthy) came afterwards to Jesus saying, “Of a truth the crumbs of thy Banquet which are fallen from the table of the guests do suffice unto them that minister: for the Lord hath increased the Bread of Life within us.” So mightily did the Bread of our Master increase in the hands of the Twelve. And Matthew said that Jesus had not only spread a table in the wilderness for the hungry, but that he had also fulfilled his saying, “Give and it shall be given unto [pg 215]you. For,” said he, “behold, to each of the disciples there cometh back his basketful of the fragments of the Feast.” And the like happened on another occasion, when they ministered the Bread unto another very great multitude about four thousand in number. All this I heard when I returned with Judas from Capernaum, bringing word that the Thracians had left the town. So we returned to Capernaum, and there we kept the Passover; for Jesus would not go up to Jerusalem to keep it, though we were very desirous that he should go up; but he said that his hour had not yet come. But scarcely had we been in Capernaum five or six days, and the Feast of the Passover was still not ended, when we fled (upon some new rumour of danger) from Capernaum again to the eastern side of the lake. Now while we were rowing across, some of us murmured (though not so loud methought that Jesus could hear) concerning our many flights and wanderings, and we wondered why our Master would not suffer the common people to make him king. In the midst of our disputing Jesus called unto us from the hinder part of the boat and said, “Beware of the leaven of the Pharisees and of the leaven of the Sadducees.” Then we looked one at another, for we felt that we were guilty; for in the haste of our embarking, because we had come on board before it was well dawn (for fear of the arrival of the Thracians, which was reported to us) we had forgotten to bring with us any unleavened bread; and the feast of the Passover wanted yet two days before it should have an end, and behold, we were going to a Gentile country where our customs were not regarded, so that we could not easily obtain such bread as was needful. Therefore we confessed to Jesus, and said that indeed we were verily guilty of sore neglect. But when Jesus heard our words, he rebuked us for our want of understanding; and he asked us whether we did not remember how the disciples had ministered the Bread of Life to the four thousand and to the five thousand; and he made mention of the saying of Thomas, one of the Twelve, how the bread had been multiplied in the hands of the Twelve, and also of the saying of Matthew the son of Levi, how the fragments of the Feast had returned to them that ministered, and had satisfied them. So we perceived that he spake not of the leaven that leaveneth bread of corn, but of the leaven which leaveneth and corrupteth the bread of the soul. Yet forasmuch as the Pharisees agree not with the Sadducees (neither do they teach the same doctrine, nor observe the same customs) I could not understand what this “leaven of the Pharisees and Sadducees” might be. But when I asked Nathanael thereof, he said that perchance Jesus desired to warn us lest we should be led away in our hearts by the desire of this world, and by the haste to be prosperous. “For,” said Nathanael, “the Sadducees love place and wealth and ease, and the Pharisees love power with the people, and the salutations of the rich, and the respect of the poor, and the name and reputation for piety; and these sects do both go straight towards their several ends. But, though several in appearance, their ends are really the same. For both the Pharisees and Sadducees serve themselves, and live for their own pleasure. And methinks our Master feareth lest we too in the same way may follow him not out of love and out of faithfulness, but from a desire to be prosperous.” “But are we not,” asked I, “to be prosperous in the end?” “Yes, assuredly in the end,” replied Nathanael; “but the end may perchance be somewhat farther off than we suppose, and our course may perchance be somewhat slow. For in all works there are two courses, the course of men and the course of God. Now men work visibly and speedily, and with much stir and noise; but the Father in Heaven worketh for the most part invisibly and slowly, and very gently. Now it may be that the slow ways are best. But in any case I begin to perceive that our Master loveth the slow ways best, according to his saying that the Kingdom of Heaven is like unto the wheat, which is sown and watered and resteth long unseen in the earth, and springeth up at last and by degrees, and putteth forth, first the blade, and then the ear and then the full corn; and all this by slow ways, quietly and gently, while the husbandman riseth and sleepeth and goeth in and out, and taketh no heed how great a work the gentle hand of the Lord is working around him.” Thus spake Nathanael, and I gave heed unto his words; for he seemed day by day to grow in the love and knowledge of our Master, and behold, the knowledge of Jesus seemed to bestow upon him knowledge of all spiritual things, so that he was not like the same Nathanael whom I had first known now a year ago. And the other disciples also were greatly changed from their former selves. For we had now been a full year with the Lord Jesus; and it was the sixteenth year of Tiberius Cæsar. 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. Edwin Abbott Abbott (2015). Philochristus: Memoirs of a Disciple of the Lord. Urbana, Illinois: Project Gutenberg. Retrieved https://www.gutenberg.org/cache/epub/48843/pg48843-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 , located at . www.gutenberg.org https://www.gutenberg.org/policy/license.html

How, after the death of John the Prophet, Jesus foresaw that he also must be slain

On War by Carl Von Clausewitz, is part of the HackerNoon Books Series. You can jump to any chapter in this book here . Fortresses (Continued) Book VI: Chapter XI. Fortresses (Continued) We have discussed the object of fortresses: now for their situation. At first the subject seems very complicated, when we think of the diversity of objects, each of which may again be modified by the locality; but such a view has very little foundation if we keep to the essence of the thing, and guard against unnecessary subtilties. It is evident that all these demands are at once satisfied, if, in those districts of country which are to be regarded as the theatre of war, all the largest and richest towns on the great high roads connecting the two countries with each other are fortified, more particularly those adjacent to harbours and bays of the sea, or situated on large rivers and in mountains. Great towns and great roads always go hand in hand, and both have also a natural connection with great rivers and the coasts of the sea, all these four conditions, therefore, agree very well with each other, and give rise to no incongruity; on the other hand, it is not the same with mountains, for large towns are seldom found there. If, therefore, the position and direction of a mountain chain makes it favourable to a defensive line, it is necessary to close its roads and passes by small forts, built for this purpose only, and at the least possible cost, the great outlay on works of fortification being reserved for the important places of arms in the level country. We have not yet noticed the frontiers of the state, nor said anything of the geometrical form of the whole system of fortresses, nor of the other geographical points in connection with their situation, because we regard the objects above mentioned as the most essential, and are of opinion that in many cases they alone are sufficient, particularly in small states. But, at the same time, other considerations may be admitted, and may be imperative in countries of a greater superficial extent, which either have a great many important towns and roads, or, on the contrary, are almost without any, which are either very rich, and, possessing already many fortresses, still want new ones, or those which, on the other hand, are very poor, and under the necessity of making a few answer, in short, in cases where the number of fortresses does not correspond with the number of important towns and roads which present themselves, being either considerably greater or less. We shall now cast a glance at the nature of such other considerations. The chief questions which remain relate to 1. The choice of the principal roads, if the two countries are connected by more roads than we wish to fortify. 2. Whether the fortresses are to be placed on the frontier only, or spread over the country. Or, 3. Whether they shall be distributed uniformly, or in groups. 4. Circumstances relating to the geography of the country to which it is necessary to pay attention. A number of other points with respect to the geometrical form of the line of fortifications, such as whether they should be placed in a single line or in several lines, that is, whether they do more service when placed one behind another, or side by side in line with each other; whether they should be chequer-wise, or in a straight line; or whether they should take the form of a fortification itself, with salients and re-entering angles all these we look upon as empty subtilties, that is, considerations so insignificant, that, compared with the really important points, they are not worth notice; and we only mention them here because they are not merely treated of in many books, but also a great deal more is made of this rubbish than it is worth. As regards the first question, in order to place it in a clearer light we shall merely instance the relation of the south of Germany to France, that is, to the upper Rhine. If, without reference to the number of separate states composing this district of country, we suppose it a whole which is to be fortified strategically, much doubt will arise, for a great number of very fine roads lead from the Rhine into the interior of Franconia, Bavaria and Austria. Certainly, towns are not wanting which surpass others in size and importance, as Nuremburg, Wurzburg, Ulm, Augsburg, and Munich; but if we are not disposed to fortify all, there is no alternative but to make a selection. If, further, in accordance with our view, the fortification of the greatest and wealthiest is held to be the principal thing, still it is not to be denied that, owing to the distance between Nuremburg and Munich, the first has a very different strategic signification from the second; and therefore it always remains to be considered whether it would not be better, in place of Nuremburg, to fortify some other place in the neighbourhood of Munich, even if the place is one of less importance in itself. As concerns the decision in such cases, that is, answering the first question, we must refer to what has been said in the chapters on the general plan of defence, and on the choice of points of attack. Wherever the most natural point of attack is situated, there the defensive arrangements should be made by preference. Therefore, amongst a number of great roads leading from the enemy’s country into ours, we should first of all fortify that which leads most directly to the heart of our dominions, or that which, traversing fertile provinces, or running parallel to navigable rivers, facilitates the enemy’s undertaking, and then we may rest secure. The assailant then encounters these works, or should he resolve to pass them by, he will naturally offer a favourable opportunity for operations against his flank. Vienna is the heart of South Germany, and plainly Munich or Augsburg, in relation to France alone (Switzerland and Italy being therefore supposed neutral) would be more efficient as a principal fortress than Nuremburg or Wurzburg. But if, at the same time, we look at the roads leading from Italy into Germany by Switzerland and the Tyrol, this will become still more evident, because, in relation to these, Munich and Augsburg will always be places of importance, whereas Wurzburg and Nuremburg are much the same, in this respect, as if they did not exist. We turn now to the second question Whether the fortresses should be placed on the frontier, or distributed over the country? In the first place, we must observe, that, as regards small states, this question is superfluous, for what are called strategic frontiers coincide, in their case, nearly with the whole country. The larger the state is supposed to be in the consideration of this question, the plainer appears the necessity for its being answered. The most natural answer is, that fortresses belong to the frontiers, for they are to defend the state, and the state is defended as long as the frontiers are defended. This argument may be valid in the abstract, but the following considerations will show that it is subject to very many modifications. Every defence which is calculated chiefly on foreign assistance lays great value on gaining time; it is not a vigorous counterstroke, but a slow proceeding, in which the chief gain consists more in delay than in any weakening of the enemy which is effected. But now it lies in the nature of the thing that, supposing all other circumstances alike, fortresses which are spread over the whole country, and include between them a very considerable area of territory, will take longer to capture than those squeezed together in a close line on the frontier. Further, in all cases in which the object is to overcome the enemy through the length of his communications, and the difficulty of his existence therefore in countries which can chiefly reckon on this kind of reaction, it would be a complete contradiction to have the defensive preparations of this kind only on the frontier. Lastly, let us also remember that, if circumstances will in any way allow of it, the fortification of the capital is a main point; that according to our principles the chief towns and places of commerce in the provinces demand it likewise; that rivers passing through the country, mountains, and other irregular features of ground, afford advantages for new lines of defence; that many towns, through their strong natural situation, invite fortification; moreover, that certain accessories of war, such as manufactories of arms, &c., are better placed in the interior of the country than on the frontier, and their value well entitles them to the protection of works of fortification; then we see that there is always more or less occasion for the construction of fortresses in the interior of a country; on this account we are of opinion, that although states which possess a great number of fortresses are right in placing the greater number on the frontier, still it would be a great mistake if the interior of the country was left entirely destitute of them. We think that this mistake has been made in a remarkable degree in France. A great doubt may with reason arise if the border provinces of a country contain no considerable towns, such towns lying further back towards the interior, as is the case in South Germany in particular, where Swabia is almost destitute of great towns, whilst Bavaria contains a large number. We do not hold it to be necessary to remove these doubts once for all on general grounds, believing that in such cases, in order to arrive at a solution, reasons derived from the particular situation must come into consideration. Still we must call attention to the closing remarks in this chapter. The third question Whether fortresses should be disposed in groups, or more equally distributed? will, if we reflect upon it, seldom arise; still we must not, for that reason, set it down as a useless subtilty, because certainly a group of two, three, or four fortresses, which are only a few days’ march from a common centre, give that point and the army placed there such strength, that, if other conditions allowed of it, in some measure one would be very much tempted to form such a strategic bastion. The last point concerns the other geographical properties of the points to be chosen. That fortresses on the sea, on streams and great rivers, and in mountains, are doubly effective, has been already stated to be one of the principal considerations; but there are a number of other points in connection with fortresses to which regard must be paid. If a fortress cannot lie on the river itself, it is better not to place it near, but at a distance of ten or twelve miles from it; otherwise, the river intersects, and lowers the value of the sphere of action of the fortress in all those points above mentioned.(*) (*) Philippsburg was the pattern of a badly-placed fortress; it resembled a fool standing with his nose close to a wall. This is not the same in mountains, because there the movement of large or small masses upon particular points is not restricted in the same degree as it is by a river. But fortresses on the enemy’s side of a mountain are not well placed, because they are difficult to succour. If they are on our side, the difficulty of laying siege to them is very great, as the mountains cut across the enemy’s line of communication. We give Olmütz, 1758, as an example. It is easily seen that impassable forests and marshes have a similar effect to that of rivers. The question has been often raised as to whether towns situated in a very difficult country are well or ill suited for fortresses. As they can be fortified and defended at a small expense, or be made much stronger, often impregnable, at an equal expenditure, and the services of a fortress are always more passive than active, it does not seem necessary to attach much importance to the objection that they can easily be blockaded. If we now, in conclusion, cast a retrospective glance over our simple system of fortification for a country, we may assert that it rests on comprehensive data, lasting in their nature, and directly connected with the foundations of the state itself, not on transient views on war, fashionable for a day; not on imaginary strategic niceties, nor on requirements completely singular in character an error which might be attended with irreparable consequences if allowed to influence the construction of fortresses intended to last five hundred, perhaps a thousand, years. Silberberg, in Silesia, built by Frederick the Great on one of the ridges of the Sudetics, has, from the complete alteration in circumstances which has since taken place, lost almost entirely its importance and object, whilst Breslau, if it had been made a strong place of arms, and continued to be so, would have always maintained its value against the French, as well as against the Russians, Poles, and Austrians. Our reader will not overlook the fact that these considerations are not raised on the supposed case of a state providing itself with a set of new fortifications; they would be useless if such was their object, as such a case seldom, if ever, happens; but they may all arise at the designing of each single fortification. 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. Carl von Clausewitz (2006). On War. Urbana, Illinois: Project Gutenberg. Retrieved https://www.gutenberg.org/cache/epub/1946/pg1946-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 .

Fortresses (Continued)

The Fortresses

I swear if I hear anyone saying cryptocurrency… Jokes aside, did you ever speak with someone who understands nothing about blockchain, and the first thing they say is " What's that? " Now you have two choices : Blue : Explain everything from the start, you can start with explaining cryptography, public/private keys, consensus mechanism, cryptocurrency, you can talk about smart contracts and maybe throw some NFT/ 69 million dollars stuff to look cool. Red : Use the magic word, "it's BiTcOiN" Now don't get me wrong, it's not like I don't like to explain Blockchain, or share my knowledge with others but it really depends on who is asking right ? So from me, if it's not someone interested, or my internship interviewer, I ain't wasting my time. If you are as lazy as me to explain to someone you just met who may or may not know how to turn on his computer what blockchain is, and you said Bitcoin and he is like “oww, I heard about that” AND YOU ARE TIRED OF IT ! then this story is for . YOU Blockchain is not Bitcoin : I am tired of people centralizing the word "blockchain" in "cryptocurrency". Let alone Bitcoin, the main reason behind it is decentralization right? Blockchain is a database that stores information in a form of blocks, and one of it's many use cases is indeed cryptocurrency. But the true potential of this technology is far more important than digital money. and it's use cases are a lot wider than you think Let's start with something evident Smart Contracts : A wise man once said : - Human Potential for evolution is limitless. Netero, HxH And where there is room for creativity, Humans will always shine, They will always find innovative ways to integrate smart contracts and make our daily life better. Smart contracts allow us to make deals with parties we don't trust, since the only thing between both parties is a list of conditions, that if fulfilled, the contract will execute automatically. They are way cheaper than your usual traditional contract, they are secure and cannot be tempered with, they are faster since everything is online and no physical presence is required. I will let you imagine the use cases for such a contract, or you can search online for information about them. Semantic Blockchain : This one is my favorite, the integration of blockchain with Artificial Intelligence. A semantic blockchain is a smart decentralized network, where the user experience is greatly improved, where all the data on the network is linked. To reach a semantic blockchain, the use of Natural language processing, machine learning, and different semantic web approaches and techniques is necessary. It's still a concept, but achieving it is only a matter of time. And I am not going to dive any more into this idea, because I don't think a small sub-section is fair enough, so maybe I will talk about it in an independent story. Multi-Dimensional Distributed Ledger: we all know that blockchain is a chain of blocks, but can you imagine this chain of blocks being only one point of view ? can you imagine that you can change your point of view to find out that there is an infinite number of blocks just behind the one you are seeing? What if each block is a part of a chain and at the same time a genesis block for another chain of blocks? Can you imagine how important that is? if you can't, don't worry, I will explain the concept in detail in another story SOON!

#ForTheLastTime Blockchain is More Than Just Crypto

Southeast Asia’s Impenetrable Blockchain Fortress

Optionals in Swift are one of the language's most convenient and powerful tools, allowing you to handle missing values safely and prevent crashes. Using Optionals is an essential part of iOS development, especially when dealing with data from users or external sources. In this article, we’ll dive into both basic and advanced methods for working with Optionals, showing how to use them in real-world scenarios to improve code reliability. What Are Optionals and Why Do We Need Them? Optionals in Swift allow a variable to hold a value or be empty (nil). This is particularly useful when data comes from unstable sources, like user input, databases, or servers, where data presence isn’t always guaranteed. Key Benefits of Optionals: Safety: Missing data doesn’t lead to app crashes.


Clarity: Using ? indicates that a value may be absent. Simple Example: var userName: String? = "Alice"
userName = nil  // Now the variable can have no value In this example, userName can either be a string or nil. If the value is missing, Swift allows you to handle it smoothly, making the app more resilient. Working with Optionals in Swift Method

When to Use

Example Code



Forced Unwrapping

If you’re sure the value isn’t nil.

let unwrappedName = userName!



Optional Binding (if let)

For safely unwrapping and handling missing data.

if let unwrappedName = userName { ... } else { print("No name provided") }



guard let

Checks value and exits function if data is nil.

guard let unwrappedName = userName else { return }



Nil-Coalescing (??)

To set a default value if the variable is nil.

let providedName = userName ?? "Unknown"



Optional Chaining

For safe access to nested values.

let userNameLength = user?.profile?.name?.count Example 1(Simple): Forced Unwrapping Forced unwrapping is used when you’re certain the value won’t be nil. This method can cause a crash if the variable is empty, so it’s best avoided unless you’re confident in the value’s presence. let unwrappedName = userName!
print("User Name: \(unwrappedName)") Forced unwrapping is useful when data is hard-coded or validated by logic. Optional Binding (if let): Safely Extracting Values Optional Binding with if let checks for the presence of a value and only uses it if it exists, avoiding errors. if let unwrappedName = userName {
    print("User Name: \(unwrappedName)")
} else {
    print("No name provided")
} This method is particularly handy when working with data from the network or databases, where information may be missing, such as when loading a user profile from an API. Nil-Coalescing (??): A Default Value for Empty Variables The Nil-Coalescing operator (??) assigns a default value if the variable is nil, making code simpler and more readable. let providedName = userName ?? "Guest"
print("User Name: \(providedName)") Nil-Coalescing is useful when you want to avoid empty values and need a standard default. Example 2 (Advanced): Error Control and Protection Let’s move on to advanced examples that demonstrate how Optionals help manage nested data and protect against unpredictable errors. guard let: Reliable Value Checking guard let checks the value and exits the function if the data is nil, which is useful for mandatory data. func greetUser(_ name: String?) {
    guard let unwrappedName = name else {
        print("No name provided")
        return
    }
    print("Hello, \(unwrappedName)!")
} In real work, guard let is convenient for mandatory data checks, like validating form fields. If the value is empty, you can immediately exit the function. Optional Chaining: Safe Access to Nested Values Optional Chaining (?.) allows you to access nested data without the risk of a crash. If any object in the chain is nil, the entire result will be nil. let userNameLength = user?.profile?.name?.count Optional Chaining is particularly useful when working with JSON data and complex structures. For example, if you’re loading a user profile from an API, Optional Chaining simplifies checking each field. Practical Applications of Optionals in iOS Projects Example 1: Retrieving User Profile Data from an API API responses may contain empty fields, and Optionals help handle these situations gracefully without causing crashes. struct UserProfile {
    var name: String?
    var age: Int?
}

func displayUserProfile(user: UserProfile) {
    let displayName = user.name ?? "Guest"
    print("User Profile: \(displayName)")
} Here, if the user’s name isn’t specified, a default value—“Guest”—will be used. Example 2: Registration Form Validation Optionals and guard let allow for proper handling of required and optional form fields. For example, checking if an email address is provided during registration. struct RegistrationForm {
    var username: String
    var email: String?
}

func registerUser(with form: RegistrationForm) {
    guard let email = form.email else {
        print("Email not provided")
        return
    }
    print("Registering user with email \(email)")
} Conclusion: Why Optionals Are Essential for Professionals Optionals are a critical part of writing reliable code in Swift. Using Optional Binding, guard let, Nil-Coalescing, and Optional Chaining shows a commitment to building robust and secure applications. In my iOS development experience, I consistently use these techniques to write resilient code that withstands unpredictable conditions and missing data. Optionals in Swift are one of the language's most convenient and powerful tools, allowing you to handle missing values safely and prevent crashes. Using Optionals is an essential part of iOS development, especially when dealing with data from users or external sources. In this article, we’ll dive into both basic and advanced methods for working with Optionals, showing how to use them in real-world scenarios to improve code reliability. What Are Optionals and Why Do We Need Them? What Are Optionals and Why Do We Need Them? Optionals in Swift allow a variable to hold a value or be empty (nil). This is particularly useful when data comes from unstable sources, like user input, databases, or servers, where data presence isn’t always guaranteed. Key Benefits of Optionals: Safety: Missing data doesn’t lead to app crashes. Clarity: Using ? indicates that a value may be absent. Safety: Missing data doesn’t lead to app crashes. Safety: Missing data doesn’t lead to app crashes. Safety: Clarity: Using ? indicates that a value may be absent. Clarity: Using ? indicates that a value may be absent. Clarity: ? Simple Example: Simple Example: var userName: String? = "Alice"
userName = nil  // Now the variable can have no value var userName: String? = "Alice"
userName = nil  // Now the variable can have no value In this example, userName can either be a string or nil. If the value is missing, Swift allows you to handle it smoothly, making the app more resilient. userName Working with Optionals in Swift Working with Optionals in Swift Method

When to Use

Example Code



Forced Unwrapping

If you’re sure the value isn’t nil.

let unwrappedName = userName!



Optional Binding (if let)

For safely unwrapping and handling missing data.

if let unwrappedName = userName { ... } else { print("No name provided") }



guard let

Checks value and exits function if data is nil.

guard let unwrappedName = userName else { return }



Nil-Coalescing (??)

To set a default value if the variable is nil.

let providedName = userName ?? "Unknown"



Optional Chaining

For safe access to nested values.

let userNameLength = user?.profile?.name?.count Method

When to Use

Example Code Forced Unwrapping

If you’re sure the value isn’t nil.

let unwrappedName = userName! Optional Binding (if let)

For safely unwrapping and handling missing data.

if let unwrappedName = userName { ... } else { print("No name provided") } guard let

Checks value and exits function if data is nil.

guard let unwrappedName = userName else { return } Nil-Coalescing (??)

To set a default value if the variable is nil.

let providedName = userName ?? "Unknown" Optional Chaining

For safe access to nested values.

let userNameLength = user?.profile?.name?.count Method When to Use Example Code Method Method When to Use When to Use Example Code Example Code Forced Unwrapping If you’re sure the value isn’t nil. let unwrappedName = userName! Forced Unwrapping Forced Unwrapping Forced Unwrapping If you’re sure the value isn’t nil. If you’re sure the value isn’t nil. If you’re sure the value isn’t nil. let unwrappedName = userName! let unwrappedName = userName! let unwrappedName = userName! Optional Binding (if let) For safely unwrapping and handling missing data. if let unwrappedName = userName { ... } else { print("No name provided") } Optional Binding (if let) Optional Binding (if let) Optional Binding (if let) For safely unwrapping and handling missing data. For safely unwrapping and handling missing data. For safely unwrapping and handling missing data. if let unwrappedName = userName { ... } else { print("No name provided") } if let unwrappedName = userName { ... } else { print("No name provided") } if let unwrappedName = userName { ... } else { print("No name provided") } guard let Checks value and exits function if data is nil. guard let unwrappedName = userName else { return } guard let guard let guard let Checks value and exits function if data is nil. Checks value and exits function if data is nil. Checks value and exits function if data is nil. guard let unwrappedName = userName else { return } guard let unwrappedName = userName else { return } guard let unwrappedName = userName else { return } Nil-Coalescing (??) To set a default value if the variable is nil. let providedName = userName ?? "Unknown" Nil-Coalescing (??) Nil-Coalescing (??) Nil-Coalescing (??) To set a default value if the variable is nil. To set a default value if the variable is nil. To set a default value if the variable is nil. let providedName = userName ?? "Unknown" let providedName = userName ?? "Unknown" let providedName = userName ?? "Unknown" Optional Chaining For safe access to nested values. let userNameLength = user?.profile?.name?.count Optional Chaining Optional Chaining Optional Chaining For safe access to nested values. For safe access to nested values. For safe access to nested values. let userNameLength = user?.profile?.name?.count let userNameLength = user?.profile?.name?.count let userNameLength = user?.profile?.name?.count Example 1(Simple): Forced Unwrapping Forced unwrapping is used when you’re certain the value won’t be nil. This method can cause a crash if the variable is empty, so it’s best avoided unless you’re confident in the value’s presence. let unwrappedName = userName!
print("User Name: \(unwrappedName)") let unwrappedName = userName!
print("User Name: \(unwrappedName)") Forced unwrapping is useful when data is hard-coded or validated by logic. Optional Binding (if let): Safely Extracting Values Optional Binding with if let checks for the presence of a value and only uses it if it exists, avoiding errors. if let if let unwrappedName = userName {
    print("User Name: \(unwrappedName)")
} else {
    print("No name provided")
} if let unwrappedName = userName {
    print("User Name: \(unwrappedName)")
} else {
    print("No name provided")
} This method is particularly handy when working with data from the network or databases, where information may be missing, such as when loading a user profile from an API. Nil-Coalescing (??): A Default Value for Empty Variables The Nil-Coalescing operator ( ?? ) assigns a default value if the variable is nil, making code simpler and more readable. ?? let providedName = userName ?? "Guest"
print("User Name: \(providedName)") let providedName = userName ?? "Guest"
print("User Name: \(providedName)") Nil-Coalescing is useful when you want to avoid empty values and need a standard default. Example 2 (Advanced): Error Control and Protection Let’s move on to advanced examples that demonstrate how Optionals help manage nested data and protect against unpredictable errors. guard let: Reliable Value Checking guard let: Reliable Value Checking guard let checks the value and exits the function if the data is nil, which is useful for mandatory data. guard let func greetUser(_ name: String?) {
    guard let unwrappedName = name else {
        print("No name provided")
        return
    }
    print("Hello, \(unwrappedName)!")
} func greetUser(_ name: String?) {
    guard let unwrappedName = name else {
        print("No name provided")
        return
    }
    print("Hello, \(unwrappedName)!")
} In real work, guard let is convenient for mandatory data checks, like validating form fields. If the value is empty, you can immediately exit the function. guard let Optional Chaining: Safe Access to Nested Values Optional Chaining ( ?. ) allows you to access nested data without the risk of a crash. If any object in the chain is nil, the entire result will be nil. ?. let userNameLength = user?.profile?.name?.count let userNameLength = user?.profile?.name?.count Optional Chaining is particularly useful when working with JSON data and complex structures. For example, if you’re loading a user profile from an API, Optional Chaining simplifies checking each field. Practical Applications of Optionals in iOS Projects Example 1: Retrieving User Profile Data from an API API responses may contain empty fields, and Optionals help handle these situations gracefully without causing crashes. struct UserProfile {
    var name: String?
    var age: Int?
}

func displayUserProfile(user: UserProfile) {
    let displayName = user.name ?? "Guest"
    print("User Profile: \(displayName)")
} struct UserProfile {
    var name: String?
    var age: Int?
}

func displayUserProfile(user: UserProfile) {
    let displayName = user.name ?? "Guest"
    print("User Profile: \(displayName)")
} Here, if the user’s name isn’t specified, a default value—“Guest”—will be used. Example 2: Registration Form Validation Optionals and guard let allow for proper handling of required and optional form fields. For example, checking if an email address is provided during registration. guard let struct RegistrationForm {
    var username: String
    var email: String?
}

func registerUser(with form: RegistrationForm) {
    guard let email = form.email else {
        print("Email not provided")
        return
    }
    print("Registering user with email \(email)")
} struct RegistrationForm {
    var username: String
    var email: String?
}

func registerUser(with form: RegistrationForm) {
    guard let email = form.email else {
        print("Email not provided")
        return
    }
    print("Registering user with email \(email)")
} Conclusion: Why Optionals Are Essential for Professionals Optionals are a critical part of writing reliable code in Swift. Using Optional Binding, guard let , Nil-Coalescing, and Optional Chaining shows a commitment to building robust and secure applications. In my iOS development experience, I consistently use these techniques to write resilient code that withstands unpredictable conditions and missing data. guard let

Stories, News & Mentions about FORTMESA

Fortmesa’s Stories on HackerNoon