ShapelessOne

785 posts

ShapelessOne banner
ShapelessOne

ShapelessOne

@ShapelessNinja

New Zealand Katılım Temmuz 2016
142 Takip Edilen69 Takipçiler
Sabitlenmiş Tweet
ShapelessOne
ShapelessOne@ShapelessNinja·
My new product commercial for Firelaces is LIVE! 🔥 Created with #Veo3, @suno, and @elevenlabs – 100% AI-generated and stitched together in Adobe Premier Pro. Generative AI is unlocking insane possibilities. The future is here! #AI #GenerativeAI #aivideo
English
0
0
2
113
ShapelessOne retweetledi
Chubby♨️
Chubby♨️@kimmonismus·
Google cooked so hard. Not gonna lie, this feels like the future is here. Now develop Google Glasses with enough battery power, a good chip, and a look like Ray-Bans, and you'll have an instant hit. 100%.
English
481
2.1K
17.5K
3.1M
ShapelessOne
ShapelessOne@ShapelessNinja·
@TomFrankly @NotionHQ I need this too! I've been waiting patiently for a long time assuming this crucial database feature must be in the works
English
0
0
1
137
Thomas Frank
Thomas Frank@TomFrankly·
The feature I most want in @NotionHQ: (This is a nerd rant and I realize there are higher-priority things they should make) Imagine two databases: Recipes and Ingredients. Recipes has fields like: - Cook time - Servings - Cuisine style - Ingredients Ingredients has fields like: - Price - Purchase link - Nutrition facts In Notion, you can easily link these databases together: Recipes ↔ Ingredients But here's the problem: How do you store the quantity of each Ingredient for each Recipe? This is called a many-to-many relationship in database-speak: - An Ingredient can be part of many Recipes - A Recipe can have many Ingredients But to model this relationship well, you typically need three tables (or "databases" in Notion-speak): - Recipes - Ingredients - Recipes-Ingredients This third table is the junction table – each row references both a Recipe record and an Ingredient record. This is what I want in Notion. I want junction tables. With this junction table, you can create an individual record that has both a Recipe (e.g. "Tacos") and an Ingredient (e.g. "Diablo Sauce"). This would allow you to: - Specify the quantity of Diablo Sauce for this particular recipe - Use that quantity to do useful calculations – e.g. pulling the nutrition facts from the Ingredient record and adjusting them based on the quantity Technically, you can sometimes model this relationship in Notion today. It's what Relations do. And if there isn't any unique information about the relationship (e.g. Ingredient quantity per Recipe), then the way Relations currently work is fine. But if there is unique information – like Ingredient quantities – you're in for a world of pain. If Notion was to make junction tables easy to build, it'd unlock so much. It's not just Recipes and Ingredients – it's all types of many-to-many relationships with unique information at the intersections: - Workout Routines and Exercises (the junction record is a Set, which can record the exercise, routine, weight, reps, etc) - Videos and B-Roll Items (you could build a b-roll library and add items to multiple videos, each with their own timecode) - Habits and Days (yep, this is the reason habit tracking is hard in Notion) There have been many times when I've stared building something cool in Notion, only to run into this exact wall. Up until recently, I didn't really understand what that wall was. So, if nothing else, hopefully this tweet-rant helps anyone else who has run into a similar wall understand the problem. Hopefully, Notion will solve it one day! It'd go a very long way to truly democratizing tool-making.
English
28
5
149
21.6K
ShapelessOne retweetledi
National Emergency Management Agency
The National Emergency Management Agency is closely monitoring the impacts for New Zealand from the global IT outages. It is likely that banking systems, communications and transport (particularly air travel) will experience disruption. More soon.
National Emergency Management Agency tweet media
English
75
145
517
62.8K
ShapelessOne
ShapelessOne@ShapelessNinja·
@TomFrankly @NotionHQ I'm working on the same thing and finding the same challenges. I've just kept mine simple for now since I don't have a lot of time for it 😅 I'd certainly be interested to see what you come up with.
English
0
0
0
111
Thomas Frank
Thomas Frank@TomFrankly·
Weekend tinkering: I'm currently trying to build a tricked-out recipe tracker in @NotionHQ. I'd love to have a complete meal management system - recipes, ingredients, meal plans, macros, price per serving, the whole shebang. So far, it seems technically possible in Notion – but it's clunky. This kind of set up requires joins – for example, an ingredient in the Ingredients database will need a different quantity for each recipe. In Notion, accomplishing this requires a "middle" database that connects Recipes and Ingredients. In the future, I'd love to see the capability to do actual SQL-style joins in Notion in order to make this part of the process smoother! Still, I'm going to work on this in my free time while it's fun. Perhaps it'll be the thing that finally gets me to go out and learn SQL (maybe I should get @aarondfrancis new course 😛)
Thomas Frank tweet media
English
17
3
78
10.8K
Zawwar Khan
Zawwar Khan@zawwarkhan_·
Whoever can find out how to crack the operational hurdles of infant formula and can tie it to the right mom influencers....They will have a 9-10 figure brand on their hands
English
14
0
21
0
ShapelessOne
ShapelessOne@ShapelessNinja·
I'm more than an IT guy :D This was fun to make. Only took 1.5 hours from start to finish using Suno, Viggle, and Adobe Premiere Rush. #AIMusic #aivideo #AI
English
1
0
0
57
Roman Khan - Founder of Peak 21. We acquire brands
Step 5: Put your job descriptions live on all relevant job sites. We use - X job boards in Eastern Europe - X in LATAM - X in Asia For anyone who follows me and re-tweets this thread - I'll DM the list of job sites - a lot of them are overlooked by the Twitter VA agencies :)
English
21
16
28
6.2K
ShapelessOne retweetledi
Roman Khan - Founder of Peak 21. We acquire brands
Step 4: Implement screening exercises that weeds out 98% of candidates. If you execute the above correctly, then you'll hopefully get 100's of candidates. Time is money. Spend time on promising candidates only. E.g For ad ops we have a xls file that they have them re-format. We then have a lookup that allow us to look for mistake. 1 mistake => You're out. E.g For customer service we have a typeform they have to fill out - simulating prospective tickets and measuring WPM. We then export all the results, filter by WPM. People under a certain WPM => You're out. If you want these example files then re-tweet this thread and I'll DM you my files and process.
English
8
14
19
6.6K
Roman Khan - Founder of Peak 21. We acquire brands
Step 2: Create a job description that speaks to a VA's needs. The 3 super important (and most overlooked) things to highlight in the job descriptions are: A. Expected working hours (this is what candidates care about) B. That you're hiring for the long term and will provide stability C. Growth of your company When you talk to our VAs you'll hear that the main concern often is the stability of their pay cheque. Imagine going from UpWork task to UpWork task. Arbitraging $1 more per hour makes no sense if they can get a stable pay cheque. Bonus hack: At scale we'll pay our VA's bi-weekly as expenses come up more frequently as cashflow is king. If you follow me, then I'll DM you our job description templates as they vary by country and we adjust them accordingly
English
4
0
19
6.7K
Project Kyzen
Project Kyzen@projectkyzen·
Tell us you've been in #ProjectKyzen without telling us you've been in Project Kyzen 😏 ❤️ Like & 🔁 Repost for a chance to win a new Kyzen outfit 🔥 T&Cs link in bio #Promotion
Project Kyzen tweet media
English
19
54
71
2.5K