pranitpashikant Profile Banner
Pranith Profile
Pranith

@pranitpashikant

Followers
28
Following
860
Media
126
Statuses
548

Introvert . Indian . Manga

Mumbai, India
Joined May 2016
Don't wanna be here? Send us removal request.
@pranitpashikant
Pranith
5 months
Is there any configuration on clickhouse side or better solution than my current approach please let me know for production grade systems. Thank you
0
0
0
@pranitpashikant
Pranith
5 months
And when updating an existing record updated at should be now() and created at should be the initial value of creation datetime. Current approach. > Check if created at exists in the record for the epid. If exists use it same or now(). > Updated at logic is similar. 4/4
1
0
0
@pranitpashikant
Pranith
5 months
Where I need to have two common fields created at and updated at in a table. I need to use this to have same functionality of oltp in olap i.e., when inserting a new record created at should be now() and updated at should be null. 3/4
1
0
0
@pranitpashikant
Pranith
5 months
Table schema: > Empid: int > Empcode: str > Created at: DateTime Default now() > Update at: Nullable(datetime) 2/4
1
0
0
@pranitpashikant
Pranith
5 months
Hi guys, Need help in optimizing soln I am currently working on integrating clickhouse for analytics search queries. We are in initial phase of it. Ik, db supports high load insertions and deletions but slow updates. We are integrating our fastapi endpoint to clickhouse 1/4
1
0
0
@cto_junior
TDM (e/λ) (L8 vibe coder 💫)
11 months
Apply by 15th if you want govt funding for LLMs folks
@cto_junior
TDM (e/λ) (L8 vibe coder 💫)
11 months
Finally a whitepill, LFGGG!!
2
15
110
@pranitpashikant
Pranith
1 year
Happy Diwali Everyone 🪔
0
0
0
@RobKnight__
Rob Pruzan
1 year
Hi @nextjs, I’m Rob. I’m a student at the University at Buffalo. I built: - Re-implementation of React from scratch (reconciler, dom renderer, and core hooks) that went #6 on Hacker News https://t.co/JNUGjuclfG - Next.js collaborative algorithm playground w/ live code execution,
58
166
2K
@that_anokha_boy
bharat
1 year
so i put up a proxy on their app and guess what 270k coinbase engineers are calculating user's usage on client side. i blocked their log_tokens api and now i can access their all models without any usage restriction lol???
190
638
16K
@pranitpashikant
Pranith
1 year
Yo! Your boy is back after hibernation period. Highlights from the past weeks. > My laptop got broke and i need to fix that and it took 7-10 days. > Developing a production level backend in Nodejs for the SocialX1. > Getting familiar with React concepts.
0
0
0
@pranitpashikant
Pranith
2 years
> found this goldmine article of building a social media using nodejs, express. > studied about implementing authentication and going through the file structure, syntaxes of js. > will make some sample template pages tommorow https://t.co/eybmdlbq0c cc: @_nightsweekends
crio.do
@pranitpashikant
Pranith
2 years
> finished reading design of url shortening. > made utility functions for api response,error and asynchandler. > divided the project into three main phases and will complete it in the same manner. 1. Creating a basic crud chat application where user can post/follow others. 1/2
0
0
0
@pranitpashikant
Pranith
2 years
With login,logout & authentication. 2. Integrating our existing project/application with payment gateway(thinking of razorpay) and able to reflect the amount in wallet balance. 3. Finally, integrating our application features(team making,Quiz,etc). 2/2.
0
0
0
@pranitpashikant
Pranith
2 years
> finished reading design of url shortening. > made utility functions for api response,error and asynchandler. > divided the project into three main phases and will complete it in the same manner. 1. Creating a basic crud chat application where user can post/follow others. 1/2
@pranitpashikant
Pranith
2 years
Finished setting up the project structure with mongodb as a db & pushed to github. will continue work on the following topics tomorrow > custom api response, > error handling > data modeling and schemas in mongodb.
1
0
0
@pranitpashikant
Pranith
2 years
Finished setting up the project structure with mongodb as a db & pushed to github. will continue work on the following topics tomorrow > custom api response, > error handling > data modeling and schemas in mongodb.
0
0
0
@pranitpashikant
Pranith
2 years
Bhai jane ke time pe full excitement to play in turf but after playing in turf u know u are fked for the entire weekend.
0
0
0
@pranitpashikant
Pranith
2 years
Yo! > prepping fr the upcoming nws s5 fr 2-3 days so my consistency dropped will pick it up from next week. > I will start documenting in detail in doc about every day. > Going all in with the tech stack that i has yet to master lets see whether i win or lose in the end.
0
0
1
@pranitpashikant
Pranith
2 years
Guys, Any one up fr a pass i have 2 left :\
@pranitpashikant
Pranith
2 years
Yo! Pitched my side project which was in mind fr the past few months. Got in fr the s5 of @_nightsweekends hosted by @_buildspace
0
0
1
@pranitpashikant
Pranith
2 years
> finished the feature after stuggling about 2-3 weeks with it & need some optimisation & refactoring. > studied about prototypes and it's background execution in js. > finished chp 7 of designing UUID and started chp 8 of Alex wu.
@pranitpashikant
Pranith
2 years
> studied promises,async nature in js and how fetch runs in background in js > started design patterns simple factory > started chp 7 of Alex wu Designing UUID generation - Problem statement - understanding the design scope - high level design - Multimaster,UUID,ticket server,etc
0
0
0
@pranitpashikant
Pranith
2 years
Yo! Pitched my side project which was in mind fr the past few months. Got in fr the s5 of @_nightsweekends hosted by @_buildspace
0
0
3
@pranitpashikant
Pranith
2 years
> studied promises,async nature in js and how fetch runs in background in js > started design patterns simple factory > started chp 7 of Alex wu Designing UUID generation - Problem statement - understanding the design scope - high level design - Multimaster,UUID,ticket server,etc
@pranitpashikant
Pranith
2 years
Day 38:- > 2 dsa problems. > cntd chp 6(designing distributed kv store) - Handling failures in a distributed sys, gossip protocol 1. temporary failures 2. permanent failures - learned about new ds merkle tree - system architecture 1/2
0
0
0