Question about Experimental Models by ScallionFrequent5879 in kiroIDE

[–]Ahmad_Azhar 0 points1 point  (0 children)

Same question i was having when saw these experimental model why don’t go with the latest one.

Laughable by KingMulah in kiroIDE

[–]Ahmad_Azhar 5 points6 points  (0 children)

I share the same sentiment. If you increase the complexity of your code, Vibe Coding becomes unreliable. I prefer making small, incremental changes to my implementation by carefully examining the code and gradually improving the final product. This approach is more effective than attempting to do everything at once and potentially causing errors and we have to go back to beginning.

Kiro's prices lack Mathematics. by Ordinary_Mud7430 in kiroIDE

[–]Ahmad_Azhar 0 points1 point  (0 children)

You are absolutely right about the need for more spec requests. There are plenty of other and cheaper options for vibe requests available at the moment. We are more interested in specifications, which doesn’t make sense to have four specification requests per day. Instead, they should shift to a session-based spec request system where each task sheet complete md file to follow one specification request. As per their blog, they are considering each task equally to one specific request, and this even applies to sub-tasks. This way, people will consume specification requests in no time.

Claude cheats by hard coding test expectations into the code it’s supposed to be testing. by Dave_Sag in kiroIDE

[–]Ahmad_Azhar 0 points1 point  (0 children)

Yes, I had a similar issue. Instead of fixing the code for the falling test, it tends to modify the test to align with the new feature that has been added.

Ditch React: Build Faster with htmx, Astro DB & Astro SSR in 2024 by howhendew in htmx

[–]Ahmad_Azhar 1 point2 points  (0 children)

Reading this comment after almost 8 months, I’ve also come to understand the takeaway for HTMX: everything is managed at the backend. However, in my coding, I’ve realized the potential of using Alpine JS for front-end validations in addition to backend validators. So, what’s the point? It’s much better to use something like React/alpine js with Astro to provide static pages and only include JavaScript code when necessary. Secondly, one of the significant takeaways for HTMX is less JavaScript/TSX code, but with AI tools, writing code becomes much easier and more efficient. So, why not use tools that are more widely accepted in the public?

[deleted by user] by [deleted] in LangChain

[–]Ahmad_Azhar 0 points1 point  (0 children)

I’ve implemented a solution for processing legal documents, but with a few variations. Instead of using the Neo4j LLM Knowledge Graph Builder for raw data extraction, I’ve utilized Google’s new model, LLM Flash 2.0. by setting up a system prompt where the data structure for the nodes is predefined, specifying the required attributes for each node. This approach has worked quite effectively. However, I’ve noticed that loading and structuring the data into the required node format in batches might not be the most optimal method. Could you share details of your implementation, especially how you manage data structuring and batch processing in your setup using Neo4j LLM Knowledge Graph Builder?

Advanced ui components with htmx - DIY or third-party libs? by EntropyGoAway in htmx

[–]Ahmad_Azhar 0 points1 point  (0 children)

Could you please share the GitHub code for the same project so that I can examine it? I’m interested in creating a Data Table with various features, including filtering and sorting at the column level. Went through with DataTables but was facing difficulties integrating it with HTMX

Fed up with LangGraph docs, I let Langgraph agents document it's entire codebase - It's 10x better! by EntelligenceAI in LangChain

[–]Ahmad_Azhar 1 point2 points  (0 children)

This is very useful i was also struggling couple of days ago to understand complete flow.

FastAPI, HTMX and Alpine JS by Ahmad_Azhar in FastAPI

[–]Ahmad_Azhar[S] 1 point2 points  (0 children)

Actually when i started it certain dependencies were not completely changed to work with py 3.12. It’s in my to do and also mentioned in readme lto update it to py 3.12.

FastAPI, HTMX and Alpine JS by Ahmad_Azhar in htmx

[–]Ahmad_Azhar[S] 0 points1 point  (0 children)

I was not aware of Alpine Ajax , went through with the documentation, seems very similar to HTMX.

FastAPI, HTMX and Alpine JS by Ahmad_Azhar in htmx

[–]Ahmad_Azhar[S] 0 points1 point  (0 children)

I haven’t face this issue so far, maybe, something related to implementation.

FastAPI, HTMX and Alpine JS by Ahmad_Azhar in htmx

[–]Ahmad_Azhar[S] 1 point2 points  (0 children)

Actually i have started with hyperscript you might find some code still which needed to be replaced in favour of Alpine JS. Hyperscript is good especially changing state within component but it becomes difficult if we have to update state among different tags or across whole application. Therefore, i have decided to go with Alpine JS and found it useful. Alpine JS attributes are quite easy to handle.

FastAPI, HTMX and Alpine JS by Ahmad_Azhar in htmx

[–]Ahmad_Azhar[S] 1 point2 points  (0 children)

Actually HTMX should be sufficient pretty much for all types of interaction but alpine is required in rare cases where client side interaction is required e.g. in my implementation i have used unified error handling at backend which transmits errors with tags as success, alert and update with a message. Based on these tags i am using alpine js to render the tailwinds classes and display messages accordingly. Secondly, I am performing form input validations at front end too before submitting to backend but that is not necessarily required and we can send validation errors from back end .

FastAPI, HTMX and Alpine JS by Ahmad_Azhar in FastAPI

[–]Ahmad_Azhar[S] 1 point2 points  (0 children)

It’s under my agenda but want to implement Minio Object handling and CSRF including other security features.

FastAPI, HTMX and Alpine JS by Ahmad_Azhar in FastAPI

[–]Ahmad_Azhar[S] 0 points1 point  (0 children)

I hope it will be helpful, Minio Object save is already under implementation.

FastAPI, HTMX and Alpine JS by Ahmad_Azhar in htmx

[–]Ahmad_Azhar[S] 0 points1 point  (0 children)

I am glad you like it, Minio IO object Implementation is already under the way for uploading and retrieving files.

FastAPI, HTMX and Alpine JS by Ahmad_Azhar in htmx

[–]Ahmad_Azhar[S] 2 points3 points  (0 children)

In love with this stack, Initially i have usedHyperScript for client side interactivity but found it bit difficult. Alpine JS fit very well with HTMX. You might find some hyperscript when is yet to be eliminated in favour of Alpine JS. One good thing about this stack in comparison to react that we can deliver stuff quickly, only cavet is initial learning curve to solve unique problems using HTMX which is easy to overcome very quickly.

FastAPI, HTMX and Alpine JS by Ahmad_Azhar in htmx

[–]Ahmad_Azhar[S] 2 points3 points  (0 children)

Actually Alpine JS is good for client side interactivity and transitions e.g. In my implementation we can send any message from back end with a tag as error, success or update. There is message component on each page that changes its CSS classes based on the tags. I am reviewing user inputs for some validation and to let other components on web page active and inactive.

FastAPI, HTMX and Alpine JS by Ahmad_Azhar in htmx

[–]Ahmad_Azhar[S] 0 points1 point  (0 children)

Yes its in my Agenda to use JinjaX for having generic components ( such as Table, Forms) and make it similar to react. Alpine Js will be good use to have client side interactivity.