Abeni Codes
Ir al canal en Telegram
I post about my insights, new discoveries, projects and advices related to tech mainly and other topics once in a while. You can DM me @abeni_al7 for professional or collaborative queries.
Mostrar más169
Suscriptores
Sin datos24 horas
Sin datos7 días
+630 días
Carga de datos en curso...
Canales Similares
Sin datos
¿Algún problema? Por favor, actualice la página o contacte a nuestro gerente de soporte.
Nube de Etiquetas
Menciones Entrantes y Salientes
---
---
---
---
---
---
Atraer Suscriptores
septiembre '26
septiembre '26
+7
en 0 canales
agosto '26
+4
en 0 canales
Get PRO
julio '26
+5
en 1 canales
Get PRO
junio '26
+8
en 0 canales
Get PRO
mayo '26
+8
en 0 canales
Get PRO
abril '26
+49
en 0 canales
Get PRO
marzo '26
+8
en 1 canales
Get PRO
febrero '26
+8
en 0 canales
Get PRO
enero '260
en 0 canales
Get PRO
diciembre '25
+2
en 0 canales
Get PRO
noviembre '25
+3
en 0 canales
Get PRO
octubre '25
+1
en 0 canales
Get PRO
septiembre '25
+1
en 0 canales
Get PRO
agosto '250
en 0 canales
Get PRO
julio '250
en 0 canales
Get PRO
junio '25
+1
en 0 canales
Get PRO
mayo '25
+5
en 0 canales
Get PRO
abril '25
+8
en 0 canales
Get PRO
marzo '25
+4
en 0 canales
Get PRO
febrero '25
+5
en 0 canales
Get PRO
enero '25
+10
en 0 canales
Get PRO
diciembre '24
+73
en 0 canales
| Fecha | Crecimiento de Suscriptores | Menciones | Canales | |
| 22 septiembre | 0 | |||
| 21 septiembre | 0 | |||
| 20 septiembre | 0 | |||
| 19 septiembre | 0 | |||
| 18 septiembre | 0 | |||
| 17 septiembre | 0 | |||
| 16 septiembre | 0 | |||
| 15 septiembre | 0 | |||
| 14 septiembre | +1 | |||
| 13 septiembre | 0 | |||
| 12 septiembre | 0 | |||
| 11 septiembre | 0 | |||
| 10 septiembre | 0 | |||
| 09 septiembre | 0 | |||
| 08 septiembre | 0 | |||
| 07 septiembre | 0 | |||
| 06 septiembre | 0 | |||
| 05 septiembre | 0 | |||
| 04 septiembre | 0 | |||
| 03 septiembre | +1 | |||
| 02 septiembre | +5 | |||
| 01 septiembre | 0 |
Publicaciones del Canal
| 2 | The AI Coding Advantage: Master Domain Driven Design First
AI coding agents can write code at remarkable speed, but speed without direction often produces software that is technically correct yet architecturally fragile.
This is where Domain Driven Design (DDD) becomes a force multiplier.
When you understand the domain, define clear bounded contexts, model business rules through entities, value objects, aggregates, and domain services, AI agents stop generating disconnected code and start building systems that reflect the business itself. Instead of spending hours fixing architecture after the fact, you spend minutes guiding the agent with the right language and boundaries.
The quality of an AI-generated codebase is rarely limited by the intelligence of the model. It is limited by the clarity of the architecture provided by the developer.
Domain Driven Design transforms AI from a code generator into an implementation partner. The better your domain model, the better your prompts become. And the better your prompts become, the closer the generated code is to production quality.
In the age of AI-assisted development, learning DDD is no longer just about writing better software. It is about gaining the ability to direct AI toward building the software you actually intended. | 121 |
| 3 | @efode_dev mentored me when I had very basic skills a couple of years ago. He is honestly the most technically proficient person I've personally worked with. You might find useful things to learn on his channel. Join his channel. | 99 |
| 4 | https://www.linkedin.com/safety/go/?url=https%3A%2F%2Flnkd%2Ein%2FgitxVsRz&urlhash=anGT&mt=aakGimVQrEBq4gf2hOlt1axb1XPJZ3VvHDxEt6vTMPBcfKEBN3rDmb1V5JZEU7xrqe5pIAIhc8DbJpGZE_yjfLO8JDHCK2tUfv5vvWFecqvxScQsBx63yPtsEpk&isSdui=true | 1 |
| 5 |  @backendlife | 97 |
| 6 | If you understand this meme, we coded in the same language once upon a time. | 96 |
| 7 |  Sin texto... | 137 |
| 8 | Also if you have an unfair advantage, you're supposed to use it. | 143 |
| 9 | You will watch less capable people win because they were in the right room, born in the right place, or lucky in timing.
That will feel unjust because it is unjust. The lesson isn't "work hard and you'll get what you deserve."
It's: the world doesn't owe you a correlation between effort and outcome, so build systems and habits that work even when the universe isn't being FAIR to you. | 130 |
| 10 | This weekend I built a clone of cut, the Unix command. I built it as part of these Coding Challenges I've been doing, which have taught me a lot so far.
When I was building this CLI tool, most of the lessons were in the edge cases since the implementation itself was relatively simple.
Here's what I learned:
- A good CLI tool does one thing well and integrates with other tools. cut reads from a file or stdin, selects fields with -f, splits on a custom delimiter with -d, and pipes seamlessly with head, tail, and other tools. This project allowed me to appreciate this philosophy.
- Interfaces are amazing when it comes to supporting different sources and also unit testing functions easily. I used io.Reader and io.Writer here, which allowed me to support both files and stdin with the same implementation.
- We need to think in terms of edge cases. The happy path of this project is straightforward. Two things I missed in my first implementation were:
* Files might start with a UTF-8 BOM (Byte Order Mark) that needs stripping.
* Lines shorter than the requested field shouldn't crash the program.
Code: https://github.com/abeni-al7/aben-cut
I have written unit tests and end-to-end tests inside. If you are interested, take a look at it. I highly recommend building such things to keep our technical abilities sharp. | 149 |
| 11 |  Sin texto... | 159 |
| 12 | I built Lacon, a huffman coding based text file compression tool. I used Go to build it and it taught me a lot of things and made me see some of the theoretical concepts I knew in practice.
Compression is an amazing concept to learn in practice. It made me appreciate the cleverness of the people that come up with algorithms that solve very specific problems in a very efficient way.
Huffman coding has a few basic steps. It scans the file, counts the frequency of each character in the file, and assigns shorter binary codes for the most frequent ones and longer codes to the least frequent ones. Compared to giving the same 8-bit length representation for all characters in a file, this results in a significantly lower file size. The significance of the compression totally depends on the distribution of characters in the text file.
While building this tool I used:
- Min-heaps to efficiently build the Huffman tree which is a special binary tree which has the most frequent characters at a shallower depth than the rarer ones.
- Binary trees to generate prefix codes that would be decoded unambiguously.
- Bit level I/O to read and write individual bits when compressing and decompressing which was admottedly the most challenging part for me.
My code is public on GitHub for anyone who wants to look at it and give me feedback (https://github.com/abeni-al7/lacon). I have also built a CLI and a web interface so that it is easy to access it and try it out (https://lacon-jet.vercel.app/). | 778 |
| 13 |  @backendlife | 156 |
| 14 |  Sin texto... | 135 |
| 15 |  Is the interview process for other roles really just convo and stuff? | 142 |
| 16 |  Sin texto... | 154 |
| 17 |  Its fully Confirmed now That Anthropic is adding Ethiopia to Supported Countries List!!!
Its rolling from Claude code first! | 122 |
| 18 | The one thing I understood that made Software Engineering approachable for me was that everything is a tradeoff.
There is no perfect solution to any problem. No solution comes with only upsides. The solution to a problem also introduces another overhead.
Our job is to balance the pros and cons of our chosen approach so that it fits into the requirements of the business we're solving the problem for. | 122 |
| 19 | Using AI for developing Software can indeed speed up delivery if done the right way. I personally like the plan, test, code, refactor loop better when working with AI agents to do this in a safe way. Reviewing the code generated is also a non-negotiable, as code by itself is a liability, and we do not want a lot of code in our codebase for which we have no context for how it works. This is also why I am skeptical of posts where people are claiming to have been generating thousands of lines of code per day.
In contrast, always using AI for coding also wears out our coding skills over time. I fear that this, in turn, might wear out our code reviewing skills as well in the long run. This is why I think we should still be coding by hand from time to time.
Although I myself have been using AI for coding at work for a long time now, I have recently decided to avoid AI while doing projects for my own learning. I think this would help me train my coding muscles and stay sharp in my reviewing skills as well.
I still use AI for writing tests, refining my documentation, and doing small refactors in my personal projects. But I have decided not to write my own projects from scratch with AI. | 120 |
| 20 | Learn AI for free directly from top companies.
1 - Anthropic:
anthropic.skilljar.com
2 - Google:
grow.google/ai
3 - Meta:
ai.meta.com/resources/
4 - NVIDIA:
developer.nvidia.com/cuda
5 - Microsoft:
learn.microsoft.com/en-us/training/
6 - OpenAI:
academy.openai.com
7 - IBM:
skillsbuild.org
8 - AWS:
skillbuilder.aws
9 - DeepLearning.AI:
deeplearning.ai
10 - Hugging Face:
huggingface.co/learn | 98 |
