Linear’s Post

The LIFT principle is a great way to better organize all sorts of information. - Locate: make things easy to find - Identify: make things easy to recognize - Flat structure as long as possible: make things easy to explore - Try to stay dry: avoid duplication and repetition https://lnkd.in/ea54DKr5

Building Cheetah Prompt: Journal #1 Today I'm excited to share the first behind-the-scenes vlog of building Cheetah Prompt, which you can watch here: https://lnkd.in/eKzm95sK Inside the link above, I share: - Why we decided to build Cheetah Prompt. - My views on building an MVP after generating millions in ARR with several different applications. - Most importantly, how Cheetah Prompt will be of value to you. I want to share one thing here that I touched upon in the video: the whole concept of "MVP" software... It's an acronym that gets thrown around in the SaaS world that I absolutely hate... In my opinion...no software should be built with the intent of rushing it out the door as the least viable product... When you hear "MVP" you instantly think of bugs, software that sucks, a clunky UI, and just an overall low-quality experience in exchange for trying software early... When building new software, there will be bugs, no doubt... You also won't be able to cram your entire vision into version 1; otherwise, you'll be building forever and spending a lot of money doing it... But whatever you build should: 1. Be well thought out. 2. Heavily tested to limit bugs. 3. Have at least 1 unique feature. 4. Be minimalist to hit a target launch date or spending amount. You can build a valuable version 1 product without it being the typical MVP... Of course, it's going to be scaled back in terms of features because you need to get your application in people's hands for feedback... But you still want the experience to be clean, well thought out, and pleasant because if it is your customers will notice... And they'll be excited for the feature packed versions that will come later down the line... That's my MVP rant, lol. I hope you enjoy journal entry #1, and I can't wait to explore things in even more depth in journal entry #2! To join the waiting list for Cheetah Prompt you can go here: https://cheetahprompt.com #CheetahPrompt #PromptEfficient #IDontBelieveInMVPs

Learn the ins and outs of creating grouped and multi-colored bars in Plotly — Jose Parreño Garcia's latest tutorial covers all the technical details and design considerations you should keep in mind.

Given an input string s, reverse the order of the words. A word is defined as a sequence of non-space characters. The words in s will be separated by at least one space. Return a string of the words in reverse order concatenated by a single space. Note that s may contain leading or trailing spaces or multiple spaces between two words. The returned string should only have a single space separating the words. Do not include any extra spaces. Example 1: Input: s = "the sky is blue" Output: "blue is sky the" Code to do that : class Solution:     def reverseWords(self, s):         split = s.split()         split = split[::-1]         return ' '.join(split)        

Differences: RecursiveCharacterTextSplitter: Splits text more intelligently by prioritizing natural breaks, starting with the largest separator (e.g., paragraph) and working down to smaller ones. It's better for preserving context in long texts. CharacterTextSplitter: A simpler, direct way to split text based on a specified separator. It works well when your splitting needs are more structured or predictable. Both splitters allow you to specify chunk size and overlap to balance between chunk size and maintaining some context across chunks. #RecursiveCharacterTextSplitter #CharacterTextSplitter

Shallow Copy and Deep Copy In general, when we try to copy one object to another object, both objects will share the same memory address. It's about how objects are saved in Stack and Heap. In the case of value types, both address and value stay in the Stack which is very easy to copy but for reference types is different. In a normal assignment, it will only copy the address (which stays in Stack) and both variables pointing to the same data so that if obj1 changes the data it reflects obj2 as well, it Shallow copy. You can do it by wrapping this.MemberwiseClone() in a class method. Deep Copy is a process of creating a new object and then copying the fields of the current object to the `newly` created object to make a complete copy of the internal reference types so obj2 will point to different addresses of heap memory, they are totally different objects. Keep in mind that deep copy is expensive and most of the time you don't need it because you just allocate more memory, ask: Do I need to create a new object? What is your thought about Shallow and Deep copy? #shallowcopy #deepcopy #softwareengineering

One of the pain points of working with Tailwind is finding sensible ways to apply conditional styles. We either do string interpolation or use a library like classNames to make the checks. Both approaches are fine. But if you're doing too many conditional class checks, you need to start thinking in components instead of styles and markup. The point of using utility classes is to have strong cohesion. So instead of altering the style of an element, render a different component that has the styles applied to them.

Here's a quick look at a new PDF + Screenshot gem I've been building. It uses Ferrum to talk to headless Chrome without any other dependencies and integrates nicely into Rails. https://lnkd.in/g65Uwx3k

A few tips to make your code instantly more readable (imo). - Add breathing space. - Handle guard / ensure clauses first. - Remove dead / unreachable code. - Group related variables. - Consistent naming. - Avoid using else, if possible—else it doesn’t matter. - Group boolean return values. - Order functions in logical manner. - Extract complex conditionals into a function. - Put variables close to where they’re used. - Use custom exceptions. Any more?

3 most confusing topics in a single cheat sheet! ✅ 1. map method 2. filter method 3. reduce method save...👇