Rejoignez le club fidélité, cumulez jusqu'à 220 points et recevez un bon de réduction Onatera de 10€ utilisable lors de votre prochaine commande.

Code promo Onatera

🔻 Comment obtenir un code promo Onatera ? Sur cette page que nous mettons à jour régulièrement, vous trouverez tous les codes promo Onatera en cours de validité. Ainsi, vous avez une vue d ...

Codes promo Onatera valides en octobre 2023

Onatera

onatera

This paper is available on arxiv under CC BY-NC-SA 4.0 DEED license. Authors: (1) Flor Ortiz, University of Luxembour; (2) Juan A. Vasquez-Peralvo, University of Luxembour; (3) Jorge Querol, University of Luxembour; (4) Eva Lagunas, University of Luxembour; (5) Jorge L. Gonzalez Rios, University of Luxembour; (6) Marcele O. K. Mendonc¸a, University of Luxembour; (7) Luis Garces, University of Luxembour; (8) Victor Monzon Baeza, University of Luxembour; (9) Symeon Chatzinotas, University of Luxembou. Table of Links Abstract & Introduction System Model and Problem Statement Antenna Design and Training Data Generation Supervised Learning for Adaptive Beamforming Numerical Results Conclusions, Acknowledgment, and References VI. CONCLUSIONS We present two novel approaches to adaptive beamforming in satellite communications systems and compare them to the traditional GA. Our goal was to explore more efficient and real-time alternatives to GA, which, although effective, can be computationally expensive. Both approaches offer viable alternatives to GA for adaptive beamforming in satellite communication systems. These approaches not only reduce execution times but also maintain high system performance. Selection between the two approaches should be based on the specific requirements of the application, taking into account the trade-off between classification complexity and overall system performance. As a result, these findings open up new possibilities for implementing efficient, real-time adaptive beamforming in wireless communication systems. Future lines of research may include further optimizations of these approaches, exploration of hybrid models, or incorporation of additional features to improve performance and versatility. ACKNOWLEDGMENT This work was supported by the European Space Agency (ESA) funded under Contract No. 4000134522/21/NL/FGL named “Satellite Signal Processing Techniques using a Commercial Off-The-Shelf AI Chipset (SPAICE)”. Please note that the views of the authors of this paper do not necessarily reflect the views of the ESA. Furthermore, this work was partially supported by the Luxembourg National Research Fund (FNR) under the project SmartSpace (C21/IS/16193290). REFERENCES [1] M. Giordani and M. Zorzi, “Satellite communication at millimeter waves: A key enabler of the 6g era,” in 2020 International Conference on Computing, Networking and Communications (ICNC). IEEE, 2020, pp. 383–388. [2] A. Cornejo, S. Landeros-Ayala, J. M. Matias, F. Ortiz-Gomez, R. Martinez, and M. Salas-Natera, “Method of rain attenuation prediction based on long–short term memory network,” Neural Processing Letters, vol. 54, no. 4, pp. 2959–2995, 2022. [3] P. Angeletti and R. De Gaudenzi, “Heuristic radio resource management for massive mimo in satellite broadband communication networks,” IEEE Access, vol. 9, pp. 147 164–147 190, 2021. [4] H.-K. Lim, J.-B. Kim, K. Kim, Y.-G. Hong, and Y.-H. Han, “Payloadbased traffic classification using multi-layer lstm in software defined networks,” Applied Sciences, vol. 9, no. 12, p. 2550, 2019. [5] Z. Wang, M. Lin, S. Sun, M. Cheng, and W.-P. Zhu, “Robust beamforming for enhancing user fairness in multibeam satellite systems with noma,” IEEE Transactions on Vehicular Technology, vol. 71, no. 1, pp. 1010–1014, 2022. [6] P. J. Honnaiah, N. Maturo, S. Chatzinotas, S. Kisseleff, and J. Krause, “Demand-based adaptive multi-beam pattern and footprint planning for high throughput geo satellite systems,” IEEE Open Journal of the Communications Society, vol. 2, pp. 1526–1540, 2021. [7] I. T. Cummings, T. J. Schulz, T. C. Havens, and J. P. Doane, “Neural networks for real-time adaptive beamforming in simultaneous transmit and receive digital phased arrays: Student submission,” in 2019 IEEE International Symposium on Phased Array System & Technology (PAST), 2019, pp. 1–8. [8] J. A. Vasquez-Peralvo, J. Querol, F. Ort ´ ´ız, J. L. G. Rios, E. Lagunas, V. M. Baeza, G. Fontanesi, L. M. Garces-Socorr ´ as, J. C. M. Duncan, ´ and S. Chatzinotas, “Flexible beamforming for direct radiating arrays in satellite communications,” IEEE Access, 2023. [9] “Fnr smartspace project datasets,” accessed on October 13, 2023. [Online]. Available: https://fnr-smartspace-project.uni.lu/datasets/ [10] F. G. Ortiz-Gomez, D. Tarchi, R. Mart ´ ´ınez, A. Vanelli-Coralli, M. A. Salas-Natera, and S. Landeros-Ayala, “Supervised machine learning for power and bandwidth management in very high throughput satellite systems,” International Journal of Satellite Communications and Networking, vol. 40, no. 6, pp. 392–407, 2022. [Online]. Available: https://onlinelibrary.wiley.com/doi/abs/10.1002/sat.1422

Supervised Learning Based Real-Time Adaptive Beamforming: Conclusions, Acknowledgment, & References

Scale Vision Transformers (ViT) Beyond Hugging Face

Scale Vision Transformers (ViT) Más allá de abrazar la cara

हगिंग फेस से परे स्केल विजन ट्रांसफॉर्मर (वीआईटी)

ハグフェイスを超えてビジョントランスフォーマー (ViT) をスケーリング

Scale Vision Transformers (ViT) além de abraçar o rosto

Người vận chuyển tầm nhìn quy mô (ViT) Ngoài khuôn mặt ôm

缩放视觉变形金刚 (ViT) 超越拥抱脸

Great Expectations, by Charles Dickens is part of HackerNoon’s Book Blog Post series. You can jump to any chapter in this book here. Chapter IV. I fully expected to find a Constable in the kitchen, waiting to take me up. But not only was there no Constable there, but no discovery had yet been made of the robbery. Mrs. Joe was prodigiously busy in getting the house ready for the festivities of the day, and Joe had been put upon the kitchen doorstep to keep him out of the dust-pan,—an article into which his destiny always led him, sooner or later, when my sister was vigorously reaping the floors of her establishment. “And where the deuce ha’ you been?” was Mrs. Joe’s Christmas salutation, when I and my conscience showed ourselves. I said I had been down to hear the Carols. “Ah! well!” observed Mrs. Joe. “You might ha’ done worse.” Not a doubt of that I thought. “Perhaps if I warn’t a blacksmith’s wife, and (what’s the same thing) a slave with her apron never off, I should have been to hear the Carols,” said Mrs. Joe. “I’m rather partial to Carols, myself, and that’s the best of reasons for my never hearing any.” Joe, who had ventured into the kitchen after me as the dustpan had retired before us, drew the back of his hand across his nose with a conciliatory air, when Mrs. Joe darted a look at him, and, when her eyes were withdrawn, secretly crossed his two forefingers, and exhibited them to me, as our token that Mrs. Joe was in a cross temper. This was so much her normal state, that Joe and I would often, for weeks together, be, as to our fingers, like monumental Crusaders as to their legs. We were to have a superb dinner, consisting of a leg of pickled pork and greens, and a pair of roast stuffed fowls. A handsome mince-pie had been made yesterday morning (which accounted for the mincemeat not being missed), and the pudding was already on the boil. These extensive arrangements occasioned us to be cut off unceremoniously in respect of breakfast; “for I ain’t,” said Mrs. Joe,—“I ain’t a-going to have no formal cramming and busting and washing up now, with what I’ve got before me, I promise you!” So, we had our slices served out, as if we were two thousand troops on a forced march instead of a man and boy at home; and we took gulps of milk and water, with apologetic countenances, from a jug on the dresser. In the meantime, Mrs. Joe put clean white curtains up, and tacked a new flowered flounce across the wide chimney to replace the old one, and uncovered the little state parlour across the passage, which was never uncovered at any other time, but passed the rest of the year in a cool haze of silver paper, which even extended to the four little white crockery poodles on the mantel-shelf, each with a black nose and a basket of flowers in his mouth, and each the counterpart of the other. Mrs. Joe was a very clean housekeeper, but had an exquisite art of making her cleanliness more uncomfortable and unacceptable than dirt itself. Cleanliness is next to Godliness, and some people do the same by their religion. My sister, having so much to do, was going to church vicariously, that is to say, Joe and I were going. In his working-clothes, Joe was a well-knit characteristic-looking blacksmith; in his holiday clothes, he was more like a scarecrow in good circumstances, than anything else. Nothing that he wore then fitted him or seemed to belong to him; and everything that he wore then grazed him. On the present festive occasion he emerged from his room, when the blithe bells were going, the picture of misery, in a full suit of Sunday penitentials. As to me, I think my sister must have had some general idea that I was a young offender whom an Accoucheur Policeman had taken up (on my birthday) and delivered over to her, to be dealt with according to the outraged majesty of the law. I was always treated as if I had insisted on being born in opposition to the dictates of reason, religion, and morality, and against the dissuading arguments of my best friends. Even when I was taken to have a new suit of clothes, the tailor had orders to make them like a kind of Reformatory, and on no account to let me have the free use of my limbs. Joe and I going to church, therefore, must have been a moving spectacle for compassionate minds. Yet, what I suffered outside was nothing to what I underwent within. The terrors that had assailed me whenever Mrs. Joe had gone near the pantry, or out of the room, were only to be equalled by the remorse with which my mind dwelt on what my hands had done. Under the weight of my wicked secret, I pondered whether the Church would be powerful enough to shield me from the vengeance of the terrible young man, if I divulged to that establishment. I conceived the idea that the time when the banns were read and when the clergyman said, “Ye are now to declare it!” would be the time for me to rise and propose a private conference in the vestry. I am far from being sure that I might not have astonished our small congregation by resorting to this extreme measure, but for its being Christmas Day and no Sunday. Mr. Wopsle, the clerk at church, was to dine with us; and Mr. Hubble the wheelwright and Mrs. Hubble; and Uncle Pumblechook (Joe’s uncle, but Mrs. Joe appropriated him), who was a well-to-do cornchandler in the nearest town, and drove his own chaise-cart. The dinner hour was half-past one. When Joe and I got home, we found the table laid, and Mrs. Joe dressed, and the dinner dressing, and the front door unlocked (it never was at any other time) for the company to enter by, and everything most splendid. And still, not a word of the robbery. The time came, without bringing with it any relief to my feelings, and the company came. Mr. Wopsle, united to a Roman nose and a large shining bald forehead, had a deep voice which he was uncommonly proud of; indeed it was understood among his acquaintance that if you could only give him his head, he would read the clergyman into fits; he himself confessed that if the Church was “thrown open,” meaning to competition, he would not despair of making his mark in it. The Church not being “thrown open,” he was, as I have said, our clerk. But he punished the Amens tremendously; and when he gave out the psalm,—always giving the whole verse,—he looked all round the congregation first, as much as to say, “You have heard my friend overhead; oblige me with your opinion of this style!” I opened the door to the company,—making believe that it was a habit of ours to open that door,—and I opened it first to Mr. Wopsle, next to Mr. and Mrs. Hubble, and last of all to Uncle Pumblechook. N.B. I was not allowed to call him uncle, under the severest penalties. “Mrs. Joe,” said Uncle Pumblechook, a large hard-breathing middle-aged slow man, with a mouth like a fish, dull staring eyes, and sandy hair standing upright on his head, so that he looked as if he had just been all but choked, and had that moment come to, “I have brought you as the compliments of the season—I have brought you, Mum, a bottle of sherry wine—and I have brought you, Mum, a bottle of port wine.” Every Christmas Day he presented himself, as a profound novelty, with exactly the same words, and carrying the two bottles like dumb-bells. Every Christmas Day, Mrs. Joe replied, as she now replied, “O, Un—cle Pum-ble—chook! This is kind!” Every Christmas Day, he retorted, as he now retorted, “It’s no more than your merits. And now are you all bobbish, and how’s Sixpennorth of halfpence?” meaning me. We dined on these occasions in the kitchen, and adjourned, for the nuts and oranges and apples to the parlour; which was a change very like Joe’s change from his working-clothes to his Sunday dress. My sister was uncommonly lively on the present occasion, and indeed was generally more gracious in the society of Mrs. Hubble than in other company. I remember Mrs. Hubble as a little curly sharp-edged person in sky-blue, who held a conventionally juvenile position, because she had married Mr. Hubble,—I don’t know at what remote period,—when she was much younger than he. I remember Mr Hubble as a tough, high-shouldered, stooping old man, of a sawdusty fragrance, with his legs extraordinarily wide apart: so that in my short days I always saw some miles of open country between them when I met him coming up the lane. Among this good company I should have felt myself, even if I hadn’t robbed the pantry, in a false position. Not because I was squeezed in at an acute angle of the tablecloth, with the table in my chest, and the Pumblechookian elbow in my eye, nor because I was not allowed to speak (I didn’t want to speak), nor because I was regaled with the scaly tips of the drumsticks of the fowls, and with those obscure corners of pork of which the pig, when living, had had the least reason to be vain. No; I should not have minded that, if they would only have left me alone. But they wouldn’t leave me alone. They seemed to think the opportunity lost, if they failed to point the conversation at me, every now and then, and stick the point into me. I might have been an unfortunate little bull in a Spanish arena, I got so smartingly touched up by these moral goads. It began the moment we sat down to dinner. Mr. Wopsle said grace with theatrical declamation,—as it now appears to me, something like a religious cross of the Ghost in Hamlet with Richard the Third,—and ended with the very proper aspiration that we might be truly grateful. Upon which my sister fixed me with her eye, and said, in a low reproachful voice, “Do you hear that? Be grateful.” “Especially,” said Mr. Pumblechook, “be grateful, boy, to them which brought you up by hand.” Mrs. Hubble shook her head, and contemplating me with a mournful presentiment that I should come to no good, asked, “Why is it that the young are never grateful?” This moral mystery seemed too much for the company until Mr. Hubble tersely solved it by saying, “Naterally wicious.” Everybody then murmured “True!” and looked at me in a particularly unpleasant and personal manner. Joe’s station and influence were something feebler (if possible) when there was company than when there was none. But he always aided and comforted me when he could, in some way of his own, and he always did so at dinner-time by giving me gravy, if there were any. There being plenty of gravy to-day, Joe spooned into my plate, at this point, about half a pint. A little later on in the dinner, Mr. Wopsle reviewed the sermon with some severity, and intimated—in the usual hypothetical case of the Church being “thrown open”—what kind of sermon he would have given them. After favouring them with some heads of that discourse, he remarked that he considered the subject of the day’s homily, ill chosen; which was the less excusable, he added, when there were so many subjects “going about.” “True again,” said Uncle Pumblechook. “You’ve hit it, sir! Plenty of subjects going about, for them that know how to put salt upon their tails. That’s what’s wanted. A man needn’t go far to find a subject, if he’s ready with his salt-box.” Mr. Pumblechook added, after a short interval of reflection, “Look at Pork alone. There’s a subject! If you want a subject, look at Pork!” “True, sir. Many a moral for the young,” returned Mr. Wopsle,—and I knew he was going to lug me in, before he said it; “might be deduced from that text.” (“You listen to this,” said my sister to me, in a severe parenthesis.) Joe gave me some more gravy. “Swine,” pursued Mr. Wopsle, in his deepest voice, and pointing his fork at my blushes, as if he were mentioning my Christian name,—“swine were the companions of the prodigal. The gluttony of Swine is put before us, as an example to the young.” (I thought this pretty well in him who had been praising up the pork for being so plump and juicy.) “What is detestable in a pig is more detestable in a boy.” “Or girl,” suggested Mr. Hubble. “Of course, or girl, Mr. Hubble,” assented Mr. Wopsle, rather irritably, “but there is no girl present.” “Besides,” said Mr. Pumblechook, turning sharp on me, “think what you’ve got to be grateful for. If you’d been born a Squeaker—” “He was, if ever a child was,” said my sister, most emphatically. Joe gave me some more gravy. “Well, but I mean a four-footed Squeaker,” said Mr. Pumblechook. “If you had been born such, would you have been here now? Not you—” “Unless in that form,” said Mr. Wopsle, nodding towards the dish. “But I don’t mean in that form, sir,” returned Mr. Pumblechook, who had an objection to being interrupted; “I mean, enjoying himself with his elders and betters, and improving himself with their conversation, and rolling in the lap of luxury. Would he have been doing that? No, he wouldn’t. And what would have been your destination?” turning on me again. “You would have been disposed of for so many shillings according to the market price of the article, and Dunstable the butcher would have come up to you as you lay in your straw, and he would have whipped you under his left arm, and with his right he would have tucked up his frock to get a penknife from out of his waistcoat-pocket, and he would have shed your blood and had your life. No bringing up by hand then. Not a bit of it!” Joe offered me more gravy, which I was afraid to take. “He was a world of trouble to you, ma’am,” said Mrs. Hubble, commiserating my sister. “Trouble?” echoed my sister; “trouble?” and then entered on a fearful catalogue of all the illnesses I had been guilty of, and all the acts of sleeplessness I had committed, and all the high places I had tumbled from, and all the low places I had tumbled into, and all the injuries I had done myself, and all the times she had wished me in my grave, and I had contumaciously refused to go there. I think the Romans must have aggravated one another very much, with their noses. Perhaps, they became the restless people they were, in consequence. Anyhow, Mr. Wopsle’s Roman nose so aggravated me, during the recital of my misdemeanours, that I should have liked to pull it until he howled. But, all I had endured up to this time was nothing in comparison with the awful feelings that took possession of me when the pause was broken which ensued upon my sister’s recital, and in which pause everybody had looked at me (as I felt painfully conscious) with indignation and abhorrence. “Yet,” said Mr. Pumblechook, leading the company gently back to the theme from which they had strayed, “Pork—regarded as biled—is rich, too; ain’t it?” “Have a little brandy, uncle,” said my sister. O Heavens, it had come at last! He would find it was weak, he would say it was weak, and I was lost! I held tight to the leg of the table under the cloth, with both hands, and awaited my fate. My sister went for the stone bottle, came back with the stone bottle, and poured his brandy out: no one else taking any. The wretched man trifled with his glass,—took it up, looked at it through the light, put it down,—prolonged my misery. All this time Mrs. Joe and Joe were briskly clearing the table for the pie and pudding. I couldn’t keep my eyes off him. Always holding tight by the leg of the table with my hands and feet, I saw the miserable creature finger his glass playfully, take it up, smile, throw his head back, and drink the brandy off. Instantly afterwards, the company were seized with unspeakable consternation, owing to his springing to his feet, turning round several times in an appalling spasmodic whooping-cough dance, and rushing out at the door; he then became visible through the window, violently plunging and expectorating, making the most hideous faces, and apparently out of his mind. I held on tight, while Mrs. Joe and Joe ran to him. I didn’t know how I had done it, but I had no doubt I had murdered him somehow. In my dreadful situation, it was a relief when he was brought back, and surveying the company all round as if they had disagreed with him, sank down into his chair with the one significant gasp, “Tar!” I had filled up the bottle from the tar-water jug. I knew he would be worse by and by. I moved the table, like a Medium of the present day, by the vigor of my unseen hold upon it. “Tar!” cried my sister, in amazement. “Why, how ever could Tar come there?” But, Uncle Pumblechook, who was omnipotent in that kitchen, wouldn’t hear the word, wouldn’t hear of the subject, imperiously waved it all away with his hand, and asked for hot gin and water. My sister, who had begun to be alarmingly meditative, had to employ herself actively in getting the gin, the hot water, the sugar, and the lemon-peel, and mixing them. For the time being at least, I was saved. I still held on to the leg of the table, but clutched it now with the fervor of gratitude. By degrees, I became calm enough to release my grasp and partake of pudding. Mr. Pumblechook partook of pudding. All partook of pudding. The course terminated, and Mr. Pumblechook had begun to beam under the genial influence of gin and water. I began to think I should get over the day, when my sister said to Joe, “Clean plates,—cold.” I clutched the leg of the table again immediately, and pressed it to my bosom as if it had been the companion of my youth and friend of my soul. I foresaw what was coming, and I felt that this time I really was gone. “You must taste,” said my sister, addressing the guests with her best grace—“you must taste, to finish with, such a delightful and delicious present of Uncle Pumblechook’s!” Must they! Let them not hope to taste it! “You must know,” said my sister, rising, “it’s a pie; a savory pork pie.” The company murmured their compliments. Uncle Pumblechook, sensible of having deserved well of his fellow-creatures, said,—quite vivaciously, all things considered,—“Well, Mrs. Joe, we’ll do our best endeavours; let us have a cut at this same pie.” My sister went out to get it. I heard her steps proceed to the pantry. I saw Mr. Pumblechook balance his knife. I saw reawakening appetite in the Roman nostrils of Mr. Wopsle. I heard Mr. Hubble remark that “a bit of savory pork pie would lay atop of anything you could mention, and do no harm,” and I heard Joe say, “You shall have some, Pip.” I have never been absolutely certain whether I uttered a shrill yell of terror, merely in spirit, or in the bodily hearing of the company. I felt that I could bear no more, and that I must run away. I released the leg of the table, and ran for my life. But I ran no farther than the house door, for there I ran head-foremost into a party of soldiers with their muskets, one of whom held out a pair of handcuffs to me, saying, “Here you are, look sharp, come on!” 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. Dickens, Charles, 1998. Great Expectations. Urbana, Illinois: Project Gutenberg. Retrieved April 2022 from https://www.gutenberg.org/files/1400/1400-h/1400-h.htm#chap04 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 .

Great Expectations: Chapter IV

Let’s talk about my first time at AWS re:Invent in Las Vegas, my mistakes, and the horrendous lack of diversity and inclusion at this conference. I went to AWS re:Invent in Las Vegas this year. As I went about my daily routine, I figured it would be a good idea to write a review of the tech conference from my perspective. Here are some of the mistakes I made that you can avoid the next time you’re headed to one of these events. For a thorough survival guide view the . The Ultimate Guide to AWS re:Invent 2018 For some reason I dropped the ball on this one. I did not download the app until Sunday night. The app is where the session catalog is located, as well as the WiFi password! Always read your emails for important information. Download the AWS re:Invent app. I found some of the best talks in rooms that held a couple hundred people. Those sessions were the best for drop-in sessions after the smaller room sessions were filled to capacity. Go to talks in the larger rooms. Sometimes I did not get into a session and had no alternative sessions to jump into at that time slot. After this happened, I spent each night, on the app, adding a bunch of sessions to my schedule to make sure I had options for the day. Sign up for everything that is remotely interesting. The events are hosted in a number of hotels on the Las Vegas strip. The hotels with the most events are the Venetian, Aria, Bellagio, and MGM. I stood at Park MGM which is connected to the Aria, so I minimized some of my walking distances. However most of the talks I was interested in were at the Venetian which meant I would be using the shuttle system a bit. Book a hotel near the events. Although the strip is highly connected, on the first day I did not know of this fact so it took me 1 hour to get to a session. After this I learned the AWS shuttles are the best way to get to and from events in different hotels. Always use AWS shuttles between venues. I learned this one by reading the signs which read “queuing starts 1 hr prior to session start time.” At that moment I learned why I arrived 15 mins early there was a line that curved around the bend for the session. Get to the sessions interesting sessions 1 hour early. I was hungry fairly often, especially because I was dashing between sessions. There are ton of snacks around the venues, primarily around the breakfast and lunch times. Stack up on snacks. I ducked out of the second keynote 10 minutes before it ended and they announced managed Kafka. Always stay to the end or you might miss something. Watch the Keynotes in full. I noticed that after the product announcements there were new sessions in the catalog labeled [NEW-LAUNCH]. I got into a few, but to be honest, it was a shitty experience to have to ditch my whole schedule and scramble to a new session. After product reveals signup for sessions. Whenever you get your badge scanned a B2B company jumps for joy because they got your email for a lifetime. Be smart and use your work email unlike me who used their personal email. Use your company email. I did not spend enough time at the expo because it was massively overwhelming. But I managed to go for a few hours and get free swag. Here I learned about chaos engineering which is freaking awesome! Go to the Expo. I found this was a cool way to meet other people at the events. You can also increase your follower count as #awsreinvent will be trending. Tweet about it. Thank you for reading! Just kidding. You honestly thought I was going write a tech article on one of the largest tech events of the year, for one of the richest companies in the world, without sharing a few cold, hard truths on diversity and inclusion 🙃? Diversity in tech What I love about these large tech conferences is that they exacerbate every stereotype, every privilege, and every shortcoming that exists in the technology industry. Every aspect in which the tech industry could do better is highlighted, clear as day, at these events. Diversity sucks. In 2017 there were approximately 43,000 people at re:Invent and this year they expected an even larger crowd according to the . Guess how many people of color I saw at this event. I found maybe one for every finger on my left hand. Maybe AWS had a secret events list just for minorities and I did not get the invitation. Conference wide that number could be 2% but even at that rate those numbers are abysmal. (I don’t have any data to support this claim.) Amazon new blog Ok but let’s be optimistic. Well Amazon is not the only company responsible for the diversity in tech problem so we can’t pin it on them. But this is their conference, so surely they made sure their panel of speakers diverse because they prize diversity and inclusion. You woulda thought thats what happened. I saw zero people of color on stage. Oh, I saw one woman! But she didn’t even give the presentation on the topic. She came from behind the stage to answer questions because I think she was in charge of the service. If that was the case, WHY DIDN’T SHE PRESENT FROM THE JUMP!? These are the things that annoy me about the tech overlords. Amazon, you are one of the richest companies on the planet, maybe even in history, with the richest man in the world at the helm of your universe conquering death star, and you’re telling me that you could not afford to put one of your best, brightest, most overpaid, employees to solve the representation problem at your tech conference!? If you’re really customer obsessed fix the diversity problem at your conference. But wait theres more! You know this recap would not be complete without someone doing the most to exclude the minorities by saying something prejudice that perpetuates the alienation we feel on the daily. Inclusion sucks. There was a re:Invent sponsored pub crawl within the various casinos. My coworker, who is black, and I were lost and confused so we decided to ask questions to other conference participates. Mind you, we both had our badges visible and we had branded AWS bags with out things. Clearly, we belonged at this conferences. Right? We saw a group of people (all white obviously) walking by that had AWS badges like ours. We asked the group for directions to the pub crawl, and I kid you not, the brogrammer of the group looked at us laughed, walked away, and said it was a private event. As common as these things are, anger is never really the first response, instead we were shocked that such an interaction even occurred. Did you know the conference has a ? Let’s look at the behavior section. code of conduct Behavior 1. You will behave in a way as to create a safe and supportive environment for all event participants. Thanks for creating an unsupportive environment for us, you dick. 2. You will not engage in disruptive speech or behavior or otherwise interfere with the event or other individuals’ participation in the event. Because of your comments and behavior, you interfered with us participating in the pub crawl event, you dick. 3. You will not engage in any form of harassing, offensive, discriminatory, or threatening speech or behavior, including (but not limited to) relating to race, gender, gender identity and expression, national origin, religion, disability, marital status, age, sexual orientation, military or veteran status, or other protected category. Thanks for offending us, you dick. 4. You will comply with the instructions of event and venue staff. Thanks for violating the code of conduct, you dick. 5. You will comply with all applicable laws. Not sure if you broke a law but you’re still a dick. And there you have it folks, even in our precious tech bubble, full of all its free snacks, high salaries, ping-pong tables, innovative disruption, and feel good talks about unlimited paid time off, even in 2018, there are some groups of people that just live a different experience within the tech world. Message to the brogrammer, we still made the pub crawl, you dick. Cheers!Dec 2, 2018 👋🏽Hi! I’m Steven Natera. Follow me on Twitter . I’m actively involved in the , specifically . I like writing about code, startups, React and Kubernetes. If you‘re a hacker or maker where we share the dope shit we’re building. @StevenNatera open source community GatsbyJS join the Dope Technophiles newsletter

AWS re:Invent 2018 Recap - The Minority Perspective

In this article we take a second look at compound components by building a Stepper for to different views in steps. A Stepper component. Last time on building compound components, Steven wrote an article to show how you can . He used a convoluted multi-step form application to demonstrate the concept. The audience members replied with a bit of confusion. Will the React community ever understand how easy it is to build compound components? Find out next time on building compound components! build a compound component in 3 easy steps Well… let me start by saying the recap is true. I’m sorry I let you down. I told you building compound components in React would be easy. If you read my last article you built the component in three steps. Mission accomplished in that regard, but the accompanying multi-step form example was a bit harder to follow. In this article you are going to build a Stepper component you can use to create multi-step views. As with the previous article, compound components can be written in three easy steps. The first step is to draw our desired JSX markup as shown on line 15 to 21. Now that you have your JSX mock up structure, you need to determine the types of props you want in your components. The Step component will be the target component to receive props. The props you want are listed below with their intended functionality. isActive — determines if the step should be active displayPrevious — controls display of the previous button displayNext — controls display of the next button displaySubmit —controls display of the submit button goToPreviousStep — a step function to go backward goToNextStep — a step function to go forward With these components you can go from one page to the next. You can control when to show the buttons based on the current active step of the StepList. You can see how to setup your Step component below. Our Step component is ready to receive props. Next, use the parent component StepList to pass the desired props to its Step component children. When you use the React API to pass props you avoid having to annotate JSX directly which allows for cleaner code. In the end you have what looks like enhanced HTML. And there you have it, a Stepper component built with compound components. Now you can create multi-step flows in your application. You can . find a working demo at this code sandbox The benefits of this advanced React pattern is clean code. When you pass props to child components in this manner you decouple the presentation layer from the logic layer allowing you to reuse these components in many projects without having to spend hours fixing it to a specific projects needs. Another thing to note is that with any software pattern, they are, well, opinionated. Some people working with React might comment that this code is brittle or inflexible because you cannot add a here and there. Well I say that’s right, compound components enforce a constraint of allowing certain components to be nested within each other. But you’ve already seen this imposed restriction in other languages. div The last time you used a tag, you probably did not throw in a tag before the tag just for funsies. The reason why you do not do that is because you understand the HTML rules for writing web markup. In that same regard, when you use the compound component pattern certain restrictions are put in place in order to write clean, and reusable code. If you don’t like the prescription, code in whatever style best fits your needs… ul div li Share this post with a friend to make them dope! 👋🏽Hi! I’m Steven Natera. Follow me on Twitter . I’m actively involved in the , specifically . I like writing about code, startups, React and Kubernetes. @StevenNatera open source community GatsbyJS

How to build a Stepper with compound components

GREETINGS FROM THE UNIVERSE. HERE ARE THIS WEEK’S TOP TECH STORIES. HACKER NOON Deep Thoughts, Drama & Actionable Tips for Crypto & Software Development. Deep Developer Thoughts by COMPUTER SCIENCE: EXPECTATION OF COMMUNITY VS REALITY Piyush Badkul by How To Tell Your Own Story: Hype Reels Meg Adams by Just-In-Case vs. Just-In-Time Learning Osman Ahmed Osman by The most common problem I’ve seen in product/engineering process Lily Chen Deep Crypto Thoughts by Crypto Moats Robert Miller by Digital Asset Ownership: Why It Matters & How Blockchain Will Save The Day Luke Lappala by Facebook’s (hypothetical) crypto strategy Monica Desai by Why the Price of Bitcoin Doesn’t Matter Beautyon Crypto Drama by Has Craig Wright Committed Perjury? New Information in the Kleiman Case Peter McCormack Developer Drama by Why Developers Should NOT Use MacBook Pro Charlee Li Actionable Developer Tips by Build a realtime map using Kotlin Neo Ighodaro by How to Make Mountains Memorable With Perlin Noise John David Martin by 3 easy steps to writing compound components Steven Natera by React 16.0–16.3 new features for every day use Artem Sapegin Actionable Crypto Tips by A HUGE List of Crypto Influencers to Follow on Youtube Crowdcreate by Investing VS Trading In Cryptocurrencies Hansel by Portfolio Diversity: A Technical Analysis ShrimpyApp by Trading: earning an income or building wealth? AndyN Until next time, don’t take the realities of the world for granted. Kind Regards, , David Smooke AMI Network

Beyond the Ice Cube Tray

Let’s dive into the world of clean React code with compound components. After implementing my first compound component in React, I’m officially addicted to this pattern. As the self-proclaimed expert on the matter (actually I learned from and his ), I’m going to teach you how to learn the best advanced React pattern out there in a few simple steps. Why? Because you deserve a better codebase! Ryan Florence talk on compound components At this point you might be thinking, who is this guy? He’s not , who wrote . He’s not our beloved React prophet . Well, my response to you is you’re correct! Kent C. Dodds the course on compound components Dan Abramov You want to make the JSX markup easy to read by grouping related components. The approach is extensible as adding another step or button is as simple as adding another component to the relevant component group. The logic that powers the fundamental components at the bottom will come from the component above. StepList and ButtonList make up the first level of the related components. A renders a given component if its the active step. goes back a step if possible. moves forward a step if possible. displays the submit message but only if its the last step. and pass down props to that determine which buttons to render on a given step and what step is active. Step Previous Next Submit StepList ButtonList Step 2. Determine what props your components will need From here you think about what props each container component needs. needs to determine the current step to present to the user. Use a current step prop. shows the , , and buttons on certain steps. An active step and total steps help determine when to show each button. You need a submit function because this is a form. Now that you have the props, you’re done! Well, not exactly. StepList ButtonList Previous Next Submit Don’t do this! We want to pass props indirectly. With you props in mind, you might be tempted to write your props directly on your components like you see above but there is a cleaner way to pass props. The better way is to pass your props indirectly. How you ask? The React API has a couple useful methods you can use to create new components from existing ones. That’s where and will become useful. React.Children React.cloneElement Step 3. Wire your components with the React API The best part of React is that a component is a regular objects. As with any object, you can manipulate them to pass around different props and functionality without having to annotate JSX components directly. will allow you to iterate over the children of a component. will allow you to create new component with additional props from an existing component element. React.Children React.cloneElement Here you iterate the children in using . As you iterate, use to create a new component with the desired props you want to pass down the component tree. FormWizard React.Children React.cloneElement The advancement functions, and , are used by and buttons. The is used by . We add these props to the new component to pass downward. The prop helps both the components and form buttons determine if they should render. onNextStep onPreviousStep Next Previous handleSubmit Submit ButtonList activeStepIndex Step The new component will get an prop from to know when to render a step. The functions and state props in the component go to the corresponding buttons that need them. Our form hides the previous button on the first step, hides the next button on the last step, and shows the submit button on the last step. Outside these cases the buttons are visible. Step isActive StepList ButtonList Finally, use the props passed to the base components to determine what should be rendered. See, simple! Sorta. I admit there is a lot to wrap your head around. But here’s the best part, Oprah and I are both Aquarius (what’s the plural of Aquarius? Aquarii?) therefore: you get a demo, you get a demo, everybody gets a demo! Here is a of the guide. demo With React 16.3 you could use the to make the FormWizard even more flexible in regards to props. Since your application is only a few levels deep you should follow the advice given in the docs. Use Context when you are passing down the same data to many components, at multiple levels. Context API If you enjoyed this dope techno guide then where we share the dope shit we’re building. Now go forth and spread the word of compound components. Share this post with a friend to make them dope! join the Dope Technophiles newsletter Cheers!May 12th, 2018 👋🏽Hi! I’m Steven Natera. Follow me on Twitter . I’m actively involved in the , specifically . I like writing about code, startups, React and Kubernetes. @StevenNatera open source community GatsbyJS

3 easy steps to writing compound components

I recently had an interviewer ask me about multithreading in NodeJS. I claimed to be proficient in NodeJS but the interviewer, as well as myself, quickly recognized there were a few fundamentals concepts I had not taken the time to research. After the interview I decided to read up on the NodeJS event loop and multithreading. A Node.js application runs on a single thread. In this thread an event loop listens for events and then triggers the events associated callback function upon detection. By this simple illustration we can already see that Node.js does not support multithreading because each application is run on a single thread. Once again if an interviewer asks if Node.js supports multithreading you can confidently say no. Although multithreading is not supported there is a way to harness the power of a multicore system by using processes. Node.js has a module called designed to support a multiprocessing alternative. Let’s view some code from the Node.js . cluster docs const cluster = require('cluster');const http = require('http');const numCPUs = require('os').cpus().length; if (cluster.isMaster) {// Fork workers.for (var i = 0; i < numCPUs; i++) {cluster.fork();} cluster.on('exit', (worker, code, signal) => {console.log(`worker ${worker.process.pid} died`);});} else {// Workers can share any TCP connection// In this case it is an HTTP serverhttp.createServer((req, res) => {res.writeHead(200);res.end('hello world\n');}).listen(8000);} The cluster module allows you to spawn multiple child processes that can share a common port. In this example the worker processes are listening for an http connection on port 8000. With the child processes in place the system can handle greater loads. Hooray! We’ve managed to successfully implement a multicore Node.js application however with every design decision there are trade-offs to evaluate. In this case our trade-offs are associated with the concepts of multithreading and multiprocessing. Threads share the same memory space and creating new threads do not take up much of the system resources. Processes run in separate memory allocations with a complete copy of the program increasing the memory overhead of the application. In situations where memory might be scarce, Node.js might be the least effective tool for application code. If I explained these concepts to my interviewer I would have surely impressed him. No harm done though. In the end the experience gave me an opportunity to learn something new. April 12, 2016 👋🏽Hi! I’m Steven Natera. Follow me on Twitter . I’m actively involved in the , specifically . I like writing about code, startups, React, and Kubernetes. @StevenNatera open source community GatsbyJS

Multithreading, Multiprocessing and the NodeJS event loop

Building a jobs board with Gatsby.js, a case study

Harnessing Blockchain Technology to Lay the Foundation for Tomorrow’s DNA Ecosystem The flexibility of blockchain infrastructures has captivated innovators, entrepreneurs and developers across a number of verticals (more so than ever in the past year). Many are beginning to truly appreciate the properties that make distributed ledger technologies so valuable, notably where data security is concerned. Blockchains are perhaps best described, in simple terms, as append-only databases that are controlled by a consensus mechanism made up of numerous participants (without a hierarchy or centralized overseer). Compared to a traditional database, this means that there is no central point of failure for an attacker to target. The participants in question will each maintain a copy of this ledger, synchronising it with that of their peers when a ‘block’ (chunk of data) is added to the network. This may not seem particularly exciting at first glance, but it is, in fact, a very powerful tool — each block added to the ledger is cryptographically linked to the prior one, meaning that any attempt to alter the information will be automatically rejected by the rest of the participants. As such, blockchains are often touted as being and . immutable tamper-proof The security of such networks stems from this structure, the topology at the peer-to-peer level and the use of robust cryptography (private/public keypairs) to ensure that only the individual uploading data can decrypt it or demonstrate ownership. Towards Medical Applications Home genetic testing has been garnering a lot of attention from consumers recently as services like Ancestry or 23AndMe have cropped up to provide insights into the health of the user — at the cost, of course, of the sharing of genomic data. It’s hard to imagine a source of data more personal to an individual than their genetic information. It stands to reason that it’s crucial that said data is kept both secure and private — easier said than done in an age of digitisation of information, home DNA testing kits and rampant data breaches. Most companies go to lengths to anonymize your data before sharing it, and to keep it secure. But sharing this type of sensitive personal information comes with an inherent risk. Consumer genetic testing firms are not typically bound by HIPAA, which means the flow of personal information is completely unregulated. And the more places data flows, the more chances there are for it to leak. may initially seem ideally suited to these ends, though it’s just a partial solution — one of the trade-offs of an immutable distributed ledger is that its throughput is somewhat lacking (remember that every participant must record every interaction), and storing even small amounts of data is an expensive and time-consuming task. Blockchain technology Evidently, in designing a platform for mass adoption, a sort of hybridised approach is best. Leveraging the features of blockchain technology and combining it with more scalable storage mediums, vastly superior alternatives to the existing ‘data silo’ phenomenon can be built. With such alternatives, secure repositories of data that are controlled entirely by the individual are anchored in the blockchain, which provides an unalterable record of the interactions occurring across the network. True Self-Sovereignty Third-party custodians and data security are not concepts that go hand-in-hand. We’ve seen the catastrophic consequences that breaches like that of Equifax and Facebook can have on the lives of their victims. It’s not something that can be allowed to continue in transitioning masses of genetic information into the digital realm. DNA is not as easily changed as a username/password. With a tech stack built on top of a blockchain, we can reverse some of the damaging patterns that have emerged as a result of a trust-heavy data ecosystem, putting individuals wholly back in control of information that belongs to them in the first place. Though the concept of an entirely ‘self-sovereign identity’ has existed for a couple of decades now, we’re finally beginning to perfect the technologies that would make truly private and secure interactions in the digital space possible.

Stories, News & Mentions about ONATERA

Categories

Trending Topics

Stories, News & Mentions about ONATERA

Onatera’s Stories on HackerNoon

Onatera's News & Mentions

Categories

Trending Topics