amir_karbasi

My pleasure! I also find languages very interesting and have had the opportunity to grow up in a bilingual home and learn French and German.

One more fun fact is that potato is a direct translation of the French “Pomme de terre” (“sib zamani” or “ground apple”).

Back to the actual topic, this is a recipe that’s definitely worth trying. Persian shallots are actually more garlicky than oniony. A great addition to lamb dishes and yogurt.

Actually, in Persian, tomato is literally translated as “western plum”. This is common in our language as we usually say “western” or “foreign” as a prefix to many things that were introduced to Iran (strawberries, sit-style toilets, etc)

Doesn't look like it. From their FAQ: "Drafted is focused on single-level floor plans today. Multi-story homes, second floors, and basements are in progress and expected to become available soon."

I'd love to see a two storey use case in the future! I have a few designs for a small plot of land in Toronto (2500 sqft lot) and would love to try and make alterations based on my zoning constraints.

Let me rephrase my question. How exact must the address input be? Do I need to include unit numbers? What if the street number is off by a few due to the layout of a plaza?

Using Maps or Web Search APIs, I can find approximate locations for certain businesses based on my input. Can your API work in a similar manner?

Really cool! We're currently using map and web searches in our agent to gather this info for our tool. Does it support an approximate address? For example, if a plaza can have multiple street numbers, do I need to make a request for each possible address or would it find a certain business with an approximate address?

Looks great! I had looked at Chonkie a few months back, but didn't need it in our pipelines. I was just writing a POC for an agentic chunker this week to handle various formatting and chunking requirements. I'll give Chonkie a shot!

From my experience working with IBM products at an enterprise level, a lot of the integrations only provide basic functionality or they are used to demonstrate a happy path for the sales team. Once you go into the implementation phase, you run into multiple issues and require substantial development to actually make it work within a client's environment.

I believe that the issue is that graphic cards require really fast memory. This requires close memory placement (that's why the memory is so close to the core on the board). expandable memory will not be able to provide the required bandwidth here.

I'm personally working on a specialized system monitor software to address deficiencies with a popular enterprise IWMS. It is aimed at companies that do not want to splurge for Splunk and require some specific system admin controls and metrics. There is a forwarder and backend API which will be completely self-hosted. I'm using this project to build some expertise in Go :)

East end of Toronto (East York)

Pros: - Great variety of foods around here (I love Hakka!) - Relatively "affordable" where you can afford a semi or detached home (albeit it'll be 100 years old with a smaller backyard) - Great walkability to small markets, restaurants, breweries and Lake Ontario - Sense of community - Pretty good transit for North America (24 hour street car, subway line and a local rail within a 5 min walk) - Bike lanes becoming more common

Cons: - Generally cold climate means a short growing season for my victory garden - Our salaries lag our southern neighbours - The health care system is showing signs of failing under pressure

How was the effort to migrate from DRF to Django-Ninja? I saw Django-Ninja mentioned in another post and am thinking of switching one of my projects over from DRF. After skimming their documentation, it looks very pleasant and simple and perfect for my use case.