AethiopeRoot

joined 4 weeks ago
MODERATOR OF
[–] AethiopeRoot@lemmy.zip 1 points 15 hours ago
[–] AethiopeRoot@lemmy.zip 1 points 4 days ago

🤣next level of brainwashing even we humans can't even comprehend

[–] AethiopeRoot@lemmy.zip 8 points 5 days ago* (last edited 5 days ago) (3 children)

I just checked out bazzite...didn't even know anything about it...feels like I have been missing a lot....thanks mate

[–] AethiopeRoot@lemmy.zip 1 points 5 days ago (7 children)

Now I only use the damn windows os for games...otherwise windows sucks

 

Malawi’s banking sector is poised for a record-breaking year, with four listed banks projected to rake in a staggering K630 billion in profits in 2025, a whopping 88 percent jump from K335 billion in 2024.

Analysts have attributed this feat to a number of factors, including robust loan growth, sky-high interest rates and lucrative lending to the government.

The four banks have published trading statements, which show that National Bank of Malawi (NBM) plc expects profit of up to K211 billion from K98  billion in 2025 while FDH Bank plc projects its profit to rise to K152 billion from K74 billion the previous year.

NBS Bank plc expects profit to range between K145.5 billion and K150.5 billion from K72.9 billion in 2024 while Standard Bank plc projects its 2025 profit to be between K112.3 billion and K120.9 billion from K86.4 billion in 2024.

The expected profit is coming at a time the banks’ balance sheets are showing that the sector remained resilient up to the third quarter of 2025, maintaining adequate capital, satisfactory earnings, sufficient liquidity, improved asset quality and growth.

The Reserve Bank of Malawi (RBM) Financial Stability Report for October 2025 indicated that the banks’ capital and liquidity improved and remained above prudential thresholds.

Reads the report in part: “Likewise, asset quality significantly improved with the non-performing loans ratio dropping to 5.1 percent, reducing the sector’s exposure to credit risk. Total industry assets increased by 15.6 percent to K8.5 trillion.

 

I got badly tilted these last few weeks and lost about 400 points of rating, from 1150 to 750 (chess.com blitz). Although I could see that the lower I got, the more mistakes my opponents made, I still lost almost every game, and it took me a while to get back to playing correctly.

## 700-rated players aren’t complete beginners and can’t be beaten without thinking

That’s one of the main things that kept me tilted: the lower I got, the more I expected to beat my opponents easily and without thinking. That doesn’t work: these players know some opening theory, spot many tactics, know some thematic ideas. It’s clear that they’re invested in chess and have learned material. If you play badly you will lose.

Although I’m low-rated myself, I would say this applies to everyone when playing lower-rated players, whatever the rating difference is. For example, in his speed runs, Daniel Naroditsky sometimes gets in a worse position, has to spend some time thinking, and gets back on track by playing a crazy complicated idea.

700 rated players are terrible at endgames

The previous paragraph is true for everything except endgames: I almost always won badly losing endgames, for example, knight+pawns vs rook+passed pawns, or even pawns vs rook+pawns. Don’t be afraid of a draw and get into the endgame if you’re low on time or don’t see a way forward in the middle game.

700-rated players attack a lot, and sloppily

That’s another thing that kept me tilted: compared to higher-rated opponents, these players attack more, even when it doesn’t work. I often panicked and lost material, or even resigned thinking they were mating attacks. However they’re often unsound, and by not panicking and taking enough time to play precise moves I could get rid of them.

700 rated players blunder unprovoked

The more moves in the game the more likely it is that they blunder. So stay concentrated, and don’t be afraid to play waiting moves or slightly improving moves rather than something more aggressive when low on time: even if you don’t see a way forward a blunder will likely happen.

What I recommend to get better when at this rating

Play solidly, only play fancy stuff when you’re sure it works: Keep your pieces defended, develop before attacking, and don’t be afraid to be a little passive. Put your pieces on good squares, for example, rooks or bishops facing the opponent’s queen, even if there are many pieces in between. When you want to play a tactic, a sacrifice, take a little time calculating, and only play it if you’re sure it works, or at least you’re sure you won’t end up in a worse position or down material.

It’s OK if you don’t attack because your opponent will eventually make a mistake.

Learn practical endgame basics, and practice endgames: At this level, endgame play is so bad that you will be able to win consistently with minimal practice. Not only will practicing endgames help you win games that already get to an endgame, but you’ll also be more confident simplifying and winning games that currently end in the middle game.

What to practice: king + several pawns vs king, using your rook to help pawns promote, basic ideas of rook endgames (get your rook in the opponent’s camp, get your rooks on the 7th rank…), how to get passed pawns. You don’t need to learn things such as Philidor/Lucena or theoretical endgames yet, just simple ideas so you make progress rather than playing random/ineffective moves.

Keep your threats in mind and check for your opponent’s mistakes: you might have a check, see a pawn that is only defended by a piece, your rook on the same column as the opponent’s queen. Don’t do anything yet (unless you see a working tactic!), but play solidly, and your opponent will eventually make a mistake, or a tactic will appear (he will move the defender, or you’ll end up able to fork rather than just check…)

Don’t do one-move threats: Don’t waste time with these. Just get your piece to a better spot. For example, when your rook is attacked by a bishop, don’t move it to attack the bishop back. Move it to a good square. Not only you will get it to a better spot, but also you won’t risk blundering by moving the piece multiple times without thinking much.

Don’t panic: When low on time, play safe moves that don’t require too much thinking. When down material keep calculating and playing solidly. Many times you’ll be able to get back on your feet. And don’t forget your opponent will likely play worse in these situations: when you’re down on time he might play quickly to flag you, when you’re down on material he might think he has already won and concentrate less.

 

Malawi News:

Illovo Sugar Malawi says floods in Nkhotakota have heavily affected its operations. Managing Director Ronald Ngwira says machinery, sugarcane fields and other property were damaged.

NationOnline:

Damaged sections of the M5 road have also disrupted sugar transportation, despite the company having 73,000MT in stock to last until April. Ngwira warns prolonged rains up to May could affect production.

[–] AethiopeRoot@lemmy.zip 7 points 1 week ago

Thanks mate

[–] AethiopeRoot@lemmy.zip 1 points 1 week ago

The full pgn of he game:

[Event "Rated Rapid game"] [Site "https://lichess.org/dFLFTPqF"] [Date "2026.01.04"] [White "The-Duke-of-Cork"] [Black "Aethiope"] [Result "0-1"] [WhiteElo "1318"] [BlackElo "1330"] [WhiteRatingDiff "-6"] [BlackRatingDiff "+21"] [Variant "Standard"] [TimeControl "600+0"] [ECO "A40"] [Opening "Queen's Pawn Game"]

  1. d4 { [%eval 0.17] [%clk 0:10:00.03] } c6 { [%eval 0.25] [%clk 0:10:00.03] } 2. Bf4 { [%eval 0.19] [%emt 0:00:00.56] [%clk 0:09:59.47] } Nf6 { [%eval 0.25] [%emt 0:00:04.96] [%clk 0:09:55.07] } 3. Nf3 { [%eval 0.15] [%emt 0:00:00.72] [%clk 0:09:58.75] } d5 { [%eval 0.28] [%emt 0:00:05.12] [%clk 0:09:49.95] } 4. Nc3 { [%eval 0.00] [%emt 0:00:00.88] [%clk 0:09:57.87] } c5 $2 { Mistake. Nbd7 was best. [%eval 1.11] [%emt 0:00:02.08] [%clk 0:09:47.87] } ( 4... Nbd7 5. a3 Qb6 6. Rb1 Nh5 7. Bd2 Nhf6 ) 5. e3 $6 { Inaccuracy. dxc5 was best. [%eval 0.49] [%emt 0:00:01.76] [%clk 0:09:56.11] } ( 5. dxc5 e6 6. b4 Nc6 7. Nb5 e5 8. Nxe5 Bxc5 9. Nxc6 bxc6 ) 5... cxd4 { [%eval 0.66] [%emt 0:00:02.24] [%clk 0:09:45.63] } 6. Qxd4 { [%eval 0.31] [%emt 0:00:09.76] [%clk 0:09:46.35] } Nc6 { [%eval 0.22] [%emt 0:00:00] [%clk 0:09:45.63] } 7. Qa4 { [%eval 0.00] [%emt 0:00:04.24] [%clk 0:09:42.11] } Bd7 { [%eval 0.00] [%emt 0:00:05.44] [%clk 0:09:40.19] } 8. Bb5 $6 { Inaccuracy. O-O-O was best. [%eval -0.58] [%emt 0:00:01.04] [%clk 0:09:41.07] } ( 8. O-O-O e6 9. e4 a6 10. exd5 b5 11. Qxb5 axb5 12. dxc6 b4 ) 8... e6 { [%eval -0.62] [%emt 0:00:02.24] [%clk 0:09:37.95] } 9. Bxc6 { [%eval -0.66] [%emt 0:00:08.4] [%clk 0:09:32.67] } Bxc6 { [%eval -0.74] [%emt 0:00:03.28] [%clk 0:09:34.67] } 10. Qd4 { [%eval -0.77] [%emt 0:00:10.96] [%clk 0:09:21.71] } Bd6 $6 { Inaccuracy. Be7 was best. [%eval -0.01] [%emt 0:00:09.92] [%clk 0:09:24.75] } ( 10... Be7 11. O-O O-O 12. Rfd1 Qc8 13. Qd3 Rd8 14. a4 Be8 15. a5 Qc5 16. Be5 ) 11. Ne5 { [%eval -0.52] [%emt 0:00:05.6] [%clk 0:09:16.11] } O-O { [%eval -0.46] [%emt 0:00:03.92] [%clk 0:09:20.83] } 12. O-O { [%eval -0.47] [%emt 0:00:05.2] [%clk 0:09:10.91] } Qb6 $4 { Blunder. Be8 was best. [%eval 2.06] [%emt 0:00:10.16] [%clk 0:09:10.67] } ( 12... Be8 ) 13. Qd1 $4 { Blunder. Qxb6 was best. [%eval -1.29] [%emt 0:00:22.48] [%clk 0:08:48.43] } ( 13. Qxb6 ) 13... Qc7 $6 { Inaccuracy. Qxb2 was best. [%eval -0.47] [%emt 0:00:04.88] [%clk 0:09:05.79] } ( 13... Qxb2 14. Nd3 Qxc3 15. Bxd6 Rfc8 16. Be5 Qc4 17. Bxf6 gxf6 18. Rb1 Qe4 19. Re1 ) 14. Nxc6 { [%eval -0.48] [%emt 0:00:08.08] [%clk 0:08:40.35] } Qxc6 { [%eval -0.28] [%emt 0:00:07.28] [%clk 0:08:58.51] } 15. Bxd6 { [%eval -0.34] [%emt 0:00:08.4] [%clk 0:08:31.95] } Qxd6 { [%eval -0.25] [%emt 0:00:01.44] [%clk 0:08:57.07] } 16. Qf3 { [%eval -0.58] [%emt 0:00:02.08] [%clk 0:08:29.87] } Rac8 { [%eval -0.52] [%emt 0:00:06.08] [%clk 0:08:50.99] } 17. Nb5 $6 { Inaccuracy. Rfc1 was best. [%eval -1.26] [%emt 0:00:01.84] [%clk 0:08:28.03] } ( 17. Rfc1 ) 17... Qb6 { [%eval -1.32] [%emt 0:00:04.16] [%clk 0:08:46.83] } 18. a4 $2 { Mistake. Qe2 was best. [%eval -2.71] [%emt 0:00:13.44] [%clk 0:08:14.59] } ( 18. Qe2 a6 19. Nd4 Qxb2 20. Rab1 Qxa2 21. Rxb7 Rb8 22. Rb3 e5 23. Rxb8 Rxb8 ) 18... a5 $4 { Blunder. Rxc2 was best. [%eval -0.13] [%emt 0:00:07.12] [%clk 0:08:39.71] } ( 18... Rxc2 19. b3 Rfc8 20. Nd4 R2c5 21. h3 h6 22. Qf4 Qd8 23. b4 Rc4 24. b5 ) 19. c3 { [%eval -0.14] [%emt 0:00:06] [%clk 0:08:08.59] } Rc5 { [%eval -0.02] [%emt 0:00:03.12] [%clk 0:08:36.59] } 20. h3 { [%eval -0.06] [%emt 0:00:05.2] [%clk 0:08:03.39] } Ne4 { [%eval -0.04] [%emt 0:00:09.52] [%clk 0:08:27.07] } 21. Qg4 { [%eval -0.15] [%emt 0:00:26.16] [%clk 0:07:37.23] } Re8 { [%eval -0.01] [%emt 0:00:02.56] [%clk 0:08:24.51] } 22. b4 $2 { Mistake. Rfd1 was best. [%eval -1.48] [%emt 0:00:07.6] [%clk 0:07:29.63] } ( 22. Rfd1 g6 23. Qf3 h5 24. Qe2 Kg7 25. Qc2 Rec8 26. Rd4 Rc4 27. Rdd1 Nd6 ) 22... Rc4 { [%eval -1.47] [%emt 0:00:05.68] [%clk 0:08:18.83] } 23. Qf4 { [%eval -1.54] [%emt 0:00:23.04] [%clk 0:07:06.59] } axb4 { [%eval -1.45] [%emt 0:00:02.24] [%clk 0:08:16.59] } 24. Nd6 $4 { Blunder. cxb4 was best. [%eval -6.26] [%emt 0:00:05.22] [%clk 0:07:01.37] } ( 24. cxb4 h6 25. Rfd1 Rxb4 26. Rdc1 Qa5 27. Qc7 Qxc7 28. Rxc7 Ra8 29. Rxb7 Rbxa4 ) 0-1
 

As it necessary? 👀are people no longer playing for the sake of tactic and strategy? Are they into playing perfect moves only until they win? I'm asking because I have received almost 17 resigns this week from fellow random chess players.

[–] AethiopeRoot@lemmy.zip 2 points 1 week ago

Leider nein. Ich war auf der Arbeit.

[–] AethiopeRoot@lemmy.zip 14 points 1 week ago (2 children)

For real....we live together...her real name isn't maths BTW.. neither am I Aethiope

 

**🎉 JavaScript Turns 30 Years Old

Back in May 1995, a 33 year old Brendan Eich built the first prototype of JavaScript in just ten days, originally codenamed Mocha (and then LiveScript). On December 4, 1995, Netscape and Sun Microsystems officially announced 'JavaScript' in a press release as "an easy-to-use object scripting language designed for creating live online applications that link together objects and resources on both clients and servers."

Over thirty years, JavaScript has cemented its place at the heart of the Web platform, and more broadly in desktop apps, operating systems (e.g. Windows' use of React Native), mobile apps, and even on microcontrollers.**

 

**🎉 JavaScript Turns 30 Years Old

Back in May 1995, a 33 year old Brendan Eich built the first prototype of JavaScript in just ten days, originally codenamed Mocha (and then LiveScript). On December 4, 1995, Netscape and Sun Microsystems officially announced 'JavaScript' in a press release as "an easy-to-use object scripting language designed for creating live online applications that link together objects and resources on both clients and servers."

Over thirty years, JavaScript has cemented its place at the heart of the Web platform, and more broadly in desktop apps, operating systems (e.g. Windows' use of React Native), mobile apps, and even on microcontrollers.**

52
submitted 3 weeks ago* (last edited 3 weeks ago) by AethiopeRoot@lemmy.zip to c/memes@lemmy.ml
 

Got confused b4 I learned this for the first time LOL

 

Recommend me any good finance related projects that may try to solve an actual problem being faced in the industry now.

 

I'm new to Lemmy BTW.

Just want to make some friends
view more: next ›