#tradcode 검색 결과
2023 feels like it will be the year in which Investors start asking startups why they are using #tradcode rather than why they are using #NoCode 90% of the time it is the right decision to derisk.
Shipping very small small, incremental, valuable features is a habit. Get addicted to it. Big Bang is for #TradCode not #NoCode
Recently read a response to a post about #NoCode on a blog. Said it was "a cancer". Wow - that is some hard triggering of one #tradcode bro.
That's quite enough baiting of #tradcode double digit Xers triggered by #nocode. Off to pressure wash the patio ☺️
Whether it is #tradcode or #lowcode or #nocode or a #pretotype made of straw ... our job is to solve problems.
That is what we have got to, and it enables us to be nimble with features that suddenly get prioritised. We are #NoCode not #TradCode so getting stuck in complex integration pipelines is not our bag. Interested to know what others are doing.
The more experience I have with @bubble the less time I actually spend in the #Bubble editor 🤷♂️ Yup, two hours dicking around in the Google Developer Console 🙄 Connecting #NoCode tool to more #TradCode tools is as inevitable as it is annoying.
2) #NoCode Data Modeler Understanding data in #NoCode applications can be tricky. Help for people in this area, particularly in proprietary databases such as Airtable or Bubble, is needed. Also, helping people who are familiar with #TradCode databases like MySQL transition.
The thing I like about AI is that even #TradCode will have to admit that not everything needs YOUR code to work.
10) #TradCode Snippiter Sometimes we need code. What we DON'T want is the wrap-around code-related ecosystem. We want some Javascript to take something, do something and return the answer IN OUR PLATFORM. Apify have done this really well with their markeplace.
There has been a bit of talk within #nocode about "shift right testing" - that is testing in post-production. @stripe asked me if I wanted to use their new invoice functionality today. Broke it in 5 minutes and reverted🤷♂️ It really is a thing even in #tradcode
I definitely agree with your analogy. #NoCode difficulty slope makes it accessible to the masses. I tend to use #tradcode when a complex backend is required such as platforms, marketplaces, SaaS... For simple content APIs, automation, prototyping, #NoCode does a real great job
Sadly a lot of #tradcode people think otherwise. Which I think is a good thing 🙂
The attitude of *some* in the #tradcode community. They act like they are the only ones who have the magic to make websites. 🤷♂️
I guess Im misunderstood. It was already engraved in our mem.but unfortunately not in the mem.of the team.But this time I don't expect double price nor user or row count. You've to either be cheap or have almost 0 learning curves to replace #tradcode I think they understand that.
Recently read a response to a post about #NoCode on a blog. Said it was "a cancer". Wow - that is some hard triggering of one #tradcode bro.
That's quite enough baiting of #tradcode double digit Xers triggered by #nocode. Off to pressure wash the patio ☺️
Regardless of database tech, having a 'business' meaning for a field being blank/null beyond just 'this field is empty' is usually a bad idea for many reasons. We shouldn't always hark back to to our #tradcode cousins...but in this case we should.
Correct. #tradcode should be gated off from the real world. We should not be beholden to them. The reason that #nocode exists in the first place is that these people were not able to do their jobs properly. Me included. We failed.
That is what we have got to, and it enables us to be nimble with features that suddenly get prioritised. We are #NoCode not #TradCode so getting stuck in complex integration pipelines is not our bag. Interested to know what others are doing.
Whether it is #tradcode or #lowcode or #nocode or a #pretotype made of straw ... our job is to solve problems. Even though they might be our own for now.
Maybe they got burned by the developers of the legacy app? #tradcode can be pretty awful for many.
Ultimately, no. You don't NEED any trace apart from a satisfied user. Perhaps you can achieve that with #NoCode tools ("fix on the phone") but it is beyond most #TradCode teams. Why would we not strive for that though?
Here is a @bubble conundrum for you all... User Auth is in a #tradcode app and unlikely to be able to do OAUTH provision. So we need to do some sort of 'secure' link into our app. Can't have separate logins. Help 🙂
The thing I like about AI is that even #TradCode will have to admit that not everything needs YOUR code to work.
Anything from the #TradCode world that we could use as data test cases ? Like counting up a decimal over 100k records Or doing a Group By where there are 100 groups of 1000 records each? Would be interesting to test against the new "approx" feature in Bubble too.
Apify and their marketplace are brilliant. We do exactly this to get JSON of a site (which is actually our site but the #TradCode people who built it seem unable or unwilling to provide API access)
10) #TradCode Snippiter Sometimes we need code. What we DON'T want is the wrap-around code-related ecosystem. We want some Javascript to take something, do something and return the answer IN OUR PLATFORM. Apify have done this really well with their markeplace.
2) #NoCode Data Modeler Understanding data in #NoCode applications can be tricky. Help for people in this area, particularly in proprietary databases such as Airtable or Bubble, is needed. Also, helping people who are familiar with #TradCode databases like MySQL transition.
2023 feels like it will be the year in which Investors start asking startups why they are using #tradcode rather than why they are using #NoCode 90% of the time it is the right decision to derisk.
You are, of course, entirely right. But hindsight is a wonderful thing and applying modern #TradCode values to early #NoCode is unfair. If you are old enough to have had to use a phone line to dial up to the internet ... even the internet looked like it was a bit rubbish.
Something went wrong.
Something went wrong.
United States Trends
- 1. Vikings 32.5K posts
- 2. Wentz 9,402 posts
- 3. Chargers 41.7K posts
- 4. Herbert 12K posts
- 5. #Skol 3,876 posts
- 6. #911onABC 12.4K posts
- 7. Brosmer 1,510 posts
- 8. #TNFonPrime 1,793 posts
- 9. Ladd 3,914 posts
- 10. Oronde Gadsden 3,319 posts
- 11. #Blackhawks 1,450 posts
- 12. $UNI 2,244 posts
- 13. #BoltUp 2,515 posts
- 14. Dallas Turner N/A
- 15. Pacers 13.5K posts
- 16. Taylor Raddysh N/A
- 17. Quentin Johnston N/A
- 18. Rempe 3,899 posts
- 19. Al Michaels N/A
- 20. Justin Jefferson 2,581 posts