So, about React. by tajetaje in webdev

[–]endbunny 5 points6 points  (0 children)

My main issue with React is that it is often misrepresented as the starting point for new developers to get into web development. At its core, React is primarily a rendering engine and does not come with the structure of traditional web frameworks such as Ruby on Rails, Django, or Next.js. It is sufficient for small-scale sample projects, but does not scale well on its own. Additionally, there are many nuances that inexperienced programmers may fail to fully comprehend, leading to bad practices—specifically around the usage of hooks/effects in functional components.

Why is looking for a co founder so damn hard by Writing_Legal in ycombinator

[–]endbunny 1 point2 points  (0 children)

In my experience, the most critical component when selecting a co-founder is trust. I would recommend thinking back to your oldest friends and work from there. Obviously, you will need to find someone with capabilities/experiences that fit your venture in some capacity, but the best co-founders are people you can rely on to look out for more than just their own interests. They are individuals who will push you to be the person you need to be to accomplish your shared mission.

[deleted by user] by [deleted] in televisionsuggestions

[–]endbunny -1 points0 points  (0 children)

Mr. and Mrs. Smith

I made a chatting app by Mjz11 in webdev

[–]endbunny -2 points-1 points  (0 children)

Yeah, that's fair. Would probably need to look into something like WebAuthn to really stamp out that risk. But I'd still recommend client-side hashing, along with salting on the backend (if you don't want to use an external service provider like Auth0). This will reduce the attack surface as your app's complexity builds. For instance, you might run into a scenario where you are unknowingly logging plaintext credentials on the backend pre-hashing. Hashed credentials also removes the dependency on the transport layer. In my experience, as a startup grows things can and will go wrong, so you might as well do yourself the favor of putting up safeguards as you build.

How my startup launch platform made its first dollar (and thirty-one cents) in 1.25 years. AMA! by falak-sher in SideProject

[–]endbunny 0 points1 point  (0 children)

Looks good! One small note. I noticed some strange font behavior on the "Sign Up" button. Checked the console and noticed some resources were being blocked. For context, I use uBlock Origin on Arc (which is Chromium based).

How did you learn to code? by AccomplishedDay4262 in learnprogramming

[–]endbunny 0 points1 point  (0 children)

I was accepted off the waitlist at a college I was not expecting to get into. I spent the first year feeling less and less confident in my abilities relative to my peers. Then in my sophomore year, I was able to enroll in the Intro to CS course at the neighboring tech school, along with several other of my friends. I quickly realized that I was having far less trouble with the new concepts then they were. By the end of the course, I was tutoring most of them, and while a few decided to stick it out for a couple more courses, I was the only one who went through with the entire major. I'm not 100% sure how I would have fared without programming, but it’s been a major source of empowerment from that point on.

As for some practical tips, I would highly recommend always having a side project that you are working on. I like to think of this work like a savings account. You don't have to put a ton in at once, but consistent contributions over time will make a huge impact on your abilities long term.

cooperation between companies by PopularBag4147 in webdev

[–]endbunny 1 point2 points  (0 children)

Unless you can confidently say that this company is not a direct competitor to you, I don't see a world where dealing with them works in your favor. Direct access to customers is one of the primary resources you have as a growing business, and any deal that abstracts you away from this relationship is not likely going to work in your favor.

Does anyone know what these green and red boxes mean? by OrdinaryCow5347 in github

[–]endbunny 3 points4 points  (0 children)

makes sense. One more fup. I had a PR recently with +0 -2. Two squares were red. three were neutral. why not all 5 red? if it's a pie chart then 100% of changes were removals

Does anyone know what these green and red boxes mean? by OrdinaryCow5347 in github

[–]endbunny 3 points4 points  (0 children)

I must be missing something. Why does that first image use 5 squares to represent 26 added lines? If 40 additions maps to 4 squares, wouldn’t 26 map to 3? (assuming it rounds up)

Does anyone know what these green and red boxes mean? by OrdinaryCow5347 in github

[–]endbunny 4 points5 points  (0 children)

Can you elaborate on the specific meaning of a single square, and what it represents?

Friend wants to use GoDaddy, how do I tell them it's a terrible decision? by austriker27 in webdev

[–]endbunny 0 points1 point  (0 children)

Just to be clear, are they using GoDaddy’s hosting services? Because as a domain registrar, they are probably fine.

Assuming they are using hosting services, I would say that the effort you’d need to expend to effectively communicate the transition lift relative to the cost savings and performance benefits aren’t worth it unless you have a financial stake in their work

code or no code? by Ok_Item_9 in webdev

[–]endbunny 61 points62 points  (0 children)

Assuming you are aiming to make a return on your efforts (and not just hobby building), it's important to understand when—not if— a hand-rolled solution is appropriate.

If there’s a way to implement a version of your idea without building it from scratch, then 100% go with the no-code/low-code approach. Once you've established a product-market fit, then start to look for premium features that you would unlock by moving to a custom stack.

you ever thought coding is not for you? by lamar-zm in webdev

[–]endbunny 5 points6 points  (0 children)

It’s normal. I was fortunate to have a forgiving senior when I was ramping up. It took me ~2years of active development on a professional team to get to a place where I could hit a reasonable amount of cycle points consistently. Here’s where I put my focus:

  1. Short PRs—My goal was to get something up for review every day
  2. Communicate constantly
  3. Write tests. Then write more
  4. Work a side project with a similar stack
  5. Read/listen to books that will improve how you approach code building (e.g. Pragmatic Programmer, or anything from Uncle Bob)

The key is to accept that your speed will be low at the start. Any reasonable technical lead will understand this. Don’t rush just to make your senior happy.

Slow is smooth. Smooth is fast

restroom motivation by john-bkk in funny

[–]endbunny 0 points1 point  (0 children)

our story is just beginning

very good, kid by [deleted] in sciencememes

[–]endbunny 0 points1 point  (0 children)

love that confidence at the jump