michael ronny

Programmer

[michael ronny @michaelronny]

@Lfc_ola_ John Arne Riise

[michael ronny @michaelronny]

@LFC_Sam__ sell

[michael ronny @michaelronny]

@AnythingLFC_ out

[michael ronny @michaelronny]

@LFCTransferRoom out

[Console Age @console_age]

@ardisatriawan Jawaban serius, karena rasa lard lebih ringan & netral. Tallow rasanya terlalu daging, duck fat ada rasa khas yg jg bs mendominasi. Selain itu kombinasi lemak jenuh & tak jenuh juga lebih sempurna pada lard, jadi hasil goreng dengan tallow akan lebih keras atau berminyak.

[michael ronny @michaelronny]

https://t.co/4jQMKlXrAZ

[Dr Milan Milanović @milan_milanovic]

This is what great writing looks like:

[Peter Xing @peterxing]

Elon v Yann diss track part 3

[michael ronny @michaelronny]

@FabrizioRomano J be

[Massimo @Rainmaker1973]

Gimbal anti-spill bowl

[michael ronny @michaelronny]

@kring_pajak @Iced_Affogato Usul Min, mungkin bisa di beri tanda merah di tempat yang kurang / harus diisi

Terima kasih

[Tansu Yegen @TansuYegen]

Phone addiction - Simon Sinek👏👏👏

[Historic Vids @historyinmemes]

Life without technology

[Alex Xu @alexxubyte]

How do companies ship code to production?

The diagram below illustrates the typical workflow.

Step 1: The process starts with a product owner creating user stories based on requirements.

Step 2: The dev team picks up the user stories from the backlog and puts them into a sprint for a two-week dev cycle.

Step 3: The developers commit source code into the code repository Git.

Step 4: A build is triggered in Jenkins. The source code must pass unit tests, code coverage threshold, and gates in SonarQube.

Step 5: Once the build is successful, the build is stored in artifactory. Then the build is deployed into the dev environment.

Step 6: There might be multiple dev teams working on different features. The features need to be tested independently, so they are deployed to QA1 and QA2.

Step 7: The QA team picks up the new QA environments and performs QA testing, regression testing, and performance testing.

Steps 8: Once the QA builds pass the QA team’s verification, they are deployed to the UAT environment.

Step 9: If the UAT testing is successful, the builds become release candidates and will be deployed to the production environment on schedule.

Step 10: SRE (Site Reliability Engineering) team is responsible for prod monitoring.

--
Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://t.co/uc5M7CdXXC

[Historic Vids @historyinmemes]

The evolution of the English language over a 1,000-year time span traces back to the 5th century when England was invaded by different tribes, including the Angles, Jutes, Saxons, and Frisians. Their languages produced what we know today as Anglo-Saxon or Old English, which sounded similar to German. In the 8th, 9th, and 10th centuries, invasions by the Vikings of Denmark, Norway, and Sweden brought another form of the same Germanic language, Old Norse, which mixed with Old English.

In the year 1066, French forces led by William the Conqueror conquered England. Over the next 300 years, thousands of French words entered the English language, especially those related to governance and food. During the English Renaissance, many Latin-based words also entered the language, partly due to English poets, writers, and playwrights. Shakespeare, for instance, wrote plays set in Italy, such as "Romeo and Juliet," "The Merchant of Venice," and "Julius Caesar."

By the mid-1500s, a modern-day English speaker would be able to communicate with some patience and concentration. While there would be some archaic pronunciations, shifting meanings, and evolving figures of speech, the language overall would be recognizable.

[michael ronny @michaelronny]

@elonmusk When will it be for the next attempt?

[michael ronny @michaelronny]

Daylight saving time: When will the clocks change this year? https://t.co/UeEI7p9QCQ