[Feb 10] - Interesting things I learnt this week

This is second of my experiment series to compile a few interesting things which I read about during the week. I hope I can continue this for this year at least.

1. Eagle 7B  - The race for better models is on. Gemini from Google is there but its another closed source one. But this one is open source. It claims to have transformers with 1 Trillion Tokens Across 100+ Languages. 

My Take: Models are going to be get better in the open source world with each passing day. Very soon we will have GPT4 level models running on our local laptops and phones. The open source is going to be a big part of it. How people build on top of these models is going to become even more interesting. I have not tried this model yet, but I am guessing it will be faster than llama2 

2. Text Generation WebUI - This is an amazing tool which starts a webservice on your machines and makes loading and configuring various LLMs a breeze. It will autodownload models once you have given hugginface project name. 

My Take: I dont know what more can ask for. Probably one of the best tools out there to try all the customised model and prompt deployment that I have come across. Downloads and loads the models with ease. Not for average usage but more for prompt engineers and those looking to experiment with LLMs

3. Canon's new chip making stamp machine - Canon announced a new chip making machine that stamps chip designs onto silicon wafers rather than etching them using light. The process, says Canon, will be “one digit” cheaper and use up to 90 percent less power than Netherlands-based ASML’s market-dominating and light-based extreme ultraviolet (EUV) technology.

My Take : It's made as a big deal announcement as if something revolutionary has been created but as noted in the article the tech has been around for sometime. But I am still hopeful they will shake things up here with atleast the less complex chips moving to this process. 

4. Gemini from Google - Bard is now Gemini and it has an Android app which replaces Assistant.

 My Take : Having teeny tiny bit of contribution to this, I don't think it's right of me to talk much about it right now. But it does a whole lot of things and is moving in sort of right direction with miles and miles to go.

 

Comments

Post a Comment

Popular posts from this blog

[1st December 2024] Interesting Things I Learnt This Week

Image
1. C++ Pitfalls - this article, explains some of the pitfalls you can fall into when programming in C++ and shares their experience with them. This includes Operator precedence, Arithmetic conversion rules, Right bit-shift, Implicit conversions and Order of evaluation.  My Take : We've all read about JavaScript's quirks, leading to unexpected outputs. But let's remember that such behaviors aren't unique to JavaScript. Even languages like C and C++ have their share of ambiguities and compiler-specific behaviors. While it's tempting to dive deep into these intricacies, I've found that focusing on clear, consistent, and unambiguous code is often more practical. However, understanding these nuances is essential for any experienced programmer. It helps us avoid pitfalls and write robust, reliable code. Remember, mastering a language isn't just about writing "Hello World." It involves delving into its intricacies, including its counterintuitive and ambi...
Read more

[17th November 2024] Interesting Things I Learnt This Week

Image
 1. Booleans are a trap : Booleans, while seemingly simple, can introduce complexity and limitations into domain modeling. When used to represent complex states, booleans can lead to unclear code and potential errors. To avoid these pitfalls, consider using enums or enum sets. These approaches provide a more expressive and maintainable way to model complex states in your applications. My Take : I wish I had learned this earlier in life. When working with Google Docs, I realized the limitations of booleans. Expanding boolean-based behaviors often led to adding more fields, making the system complex. Enums would have provided a simpler solution. The problem wasn't just the booleans themselves, but also the need to pass them through multiple layers of the stack, often requiring additional parameters. Another important aspect of enums is the inclusion of an " enum not specified " state. This state explicitly indicates that an enum value hasn't been set, which can be usef...
Read more

[15th December 2024] Interesting Things I Learnt This Week

Image
1. Why you should never use !! in Kotlin - Using double-bang operator(!!) is a bad practice; multiple alternatives cover every other possible case. Using it is a hack and a shortcut that will backfire while not saving you much time at the time of writing using it. You shouldn’t use it unless you're writing a short personal script. My Take : The double-bang operator (!!)  which throws null pointer exception in Kotlin might very well be considered " Billion Dollar Mistake ." While it offers a concise way to assert that a variable is not null, I believe it's preferable to have slightly more verbose code that explicitly handles nullability and avoids potential runtime exceptions. Null pointer exceptions have plagued programmers for decades, and introducing a feature that can easily lead to them seems counterproductive. I'm uncertain whether all Kotlin linters currently check for excessive or inappropriate use of the !! operator, but if yours don't, I strongly re...
Read more