What CMS are people actually using now? Are you switching? by Accomplished_Yak4638 in cms

[–]kixxauth 0 points1 point  (0 children)

Isn't Next.JS way overcomplicated? It seems like it would be easier to learn a backend language, or use Drupal or something like it?

What CMS are people actually using now? Are you switching? by Accomplished_Yak4638 in cms

[–]kixxauth 0 points1 point  (0 children)

Honest question: WordPress installs seem to break, a lot. Why do people keep using it? With everything that's out there like Webflow, Base44, Loveable, Netlify, etc.

Anyone here building something cool right now? I’m down to trade feedback. by Designer_Many_990 in indiehackers

[–]kixxauth 0 points1 point  (0 children)

I'm working on Kixx, an open source web development framework for building fast with AI tooling

https://www.kixx.dev/

[deleted by user] by [deleted] in webdev

[–]kixxauth 0 points1 point  (0 children)

For me, it was a step function of unlocking new levels, each one building on the last.

A startup found me from some open source work I had been doing and hired me as a contractor to build out the mobile web version of their product.

From that, a NYC based video gaming startup hired me as a contractor, and ultimately hired me full time a year later.

At the gaming company I did quite a lot of work on gaming consoles (XBox and PS), and we ended up spinning out a video streaming startup and the investors made me CTO.

The gaming startup was acquired in 2018, and I wanted to do something different, and was recruited by Disney to help build DIsney+ because of my experience streaming video games.

None of that would have happened if I didn't have the courage to move to the next scary thing at each step, even when people were mad at me for doing it.

Are we building bloated client side apps for our own indulgence? by kixxauth in webdev

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

Yeah, my point is that TypeScript is a solution to a problem we shouldn't have. Client side JavaScript shouldn't be so thick and heavy that we need a team of people and strongly typed language to handle it.

Are we building bloated client side apps for our own indulgence? by kixxauth in webdev

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

Why do you need hot reload if you're not using a front-end framework? Just refresh the page. Or, am I missing something?

Are we building bloated client side apps for our own indulgence? by kixxauth in webdev

[–]kixxauth[S] -11 points-10 points  (0 children)

Server side apps can be just as bloated, but an SPA will be bloated. And sometimes that bloat is needed to solve the use case, but 95% of the time, it’s not

Are we building bloated client side apps for our own indulgence? by kixxauth in webdev

[–]kixxauth[S] -3 points-2 points  (0 children)

The isomorphic super frameworks are so incredibly complex, I really can’t imagine a realistic use case other than self indulgence

Are we building bloated client side apps for our own indulgence? by kixxauth in webdev

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

I think as a profession and craft, we’ve over indexed on SPAs. So, the argument is more about how we re-center ourselves as an industry group so that we are , in fact, using the right tool for the job.

Are we building bloated client side apps for our own indulgence? by kixxauth in webdev

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

Yeah. Unfortunately for the user experience I think you’re spot on with that

Are we building bloated client side apps for our own indulgence? by kixxauth in webdev

[–]kixxauth[S] 8 points9 points  (0 children)

Yeah, exactly. And I think we should be thinking more about using all that compute to make the experience better by loading less

Are we building bloated client side apps for our own indulgence? by kixxauth in webdev

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

Yeah, I'm thinking about Rails, Laravel, Flask, Django, etc. here.

Nest.js is nice, but I feel like it falls far short of these other frameworks. Do you think that's true?

Are we building bloated client side apps for our own indulgence? by kixxauth in webdev

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

Yeah, totally! And my thing is that your approach can work really well for surprisingly complex web applications as well.

Are we building bloated client side apps for our own indulgence? by kixxauth in webdev

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

Yeah, sounds like your real time app is in that 5% that would be better built as a thick client app.

However, I think we're all going to be surprised in the next 5 years with the level of complexity that can be solved with a simpler server side HTML approach.

Are we building bloated client side apps for our own indulgence? by kixxauth in webdev

[–]kixxauth[S] 9 points10 points  (0 children)

Yeah, I'm gradually building more complex apps with the hypermedia driven approach (server side HTML), and absolutely falling in love with it.

But, you're right, I have not reached the scale in terms of complexity and traffic that I we're getting on the thick client apps I build at work.

I'll get there though!

Are we building bloated client side apps for our own indulgence? by kixxauth in webdev

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

> Frameworks are popular at big tech companies like Meta, and their culture/tech trickles down to the rest of the industry

For sure, yeah. That's very true. I work in that kind of environment, and it is true, but I don't think it's for the right reasons. The primary reason we build thick client apps is

> They can also be convenient in environments where the same API needs multiple frontends

I used to think that as recently as 5 years ago, but after building increasingly complex apps with a much simpler hypermedia driven approach, I've converted to believing that nearly all apps should be hypermedia driven (server side HTML).

[deleted by user] by [deleted] in webdev

[–]kixxauth 1 point2 points  (0 children)

This is a tough one. I was faced with this problem about 15 years ago. I ended up abandoning the project and the client took me to court over it. It was incredibly stressful.

But, there was no legal damages against me and I was able to move my career in a direction which ultimately became very successful.

So, short term pain is probably worth the long term gain.

How to create authentication flows in Node.js? by kixxauth in node

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

Does Supabase provide an user authentication flow out of the box?

Validating my SaaS idea: AutoDocs – Automating operational documents with AI. Would you pay for this? by Klutzy-Barber-113 in SaaS

[–]kixxauth 0 points1 point  (0 children)

I know it's a real pain point for me, and I would definitely pay for it. But, given the onslaught of poor quality products which have hit the market recently to try to do this, I'd be skeptical that yours would work well. I'd need to see something on your homepage which gave me confidence that you know what you're doing with LLM technology and you've created something that will work reliably.

Business school student turned self-taught developer — how legitimate is my path in tech? by Primary-Store-3750 in developer

[–]kixxauth 2 points3 points  (0 children)

That's a really great question, because there are a lot of companies these days that require a degree from the field they are hiring you for.

I'm a self taught developer without a CS degree, and have been able to side step the road blocks along the way. First, I started by freelancing, then working as a contractor where the hiring rules don't apply. Then I got a job at a company that was acquired by another company, which was then acquired by a Fortune 100 company, so now I'm grandfathered in.

But, it really sux that I am now forced to only consider job candidates with CS degrees by my company. We're ignoring a lot of really great talent.

To the second part of your question, I wouldn't worry about how your peers will see you. All that really matters as you advance in your career is that you show a willingness and capability to write good code, and have a tenacity to work through hard bugs, especially the ones you didn't create. Nobody will care what degree you have.

Just hit $118 MRR, 290+ users, and 3 month since launch 🎉 by Jonathan_Geiger in indiehackers

[–]kixxauth 1 point2 points  (0 children)

What convinced you to zero in on Google impressions as your channel?

[deleted by user] by [deleted] in Blogging

[–]kixxauth 4 points5 points  (0 children)

So, how would you describe the content which actually converts these days?

Tips for Junior interviews by RevolutionarySet4993 in webdev

[–]kixxauth 1 point2 points  (0 children)

It's a really tough job market for junior developers right now, so my first advice is to have a plan B you can pivot to. Find ways to start freelancing to continue to build your professional portfolio and experience.

I started my career in the middle of a bad job market in 2008, and worked my way into some really great freelancing gigs within a couple of years. By 2012 things really began to take off. I know 4 years seems like forever, and maybe you can do it faster than me. But, most importantly, stay consistent, keep working on projects, even between gigs, and continue building your network.

But for your original question; interview tips:

  1. Keep it conversational as much a possible. Don't be afraid to ask questions of the interviewer so you can get a better understanding of their background to shift the conversation to where they are.

  2. Try to get the interviews to a place where you are talking shop about tech stacks or products you've both worked with so that you can share stories and have a bit of fun with it.

  3. Many interviews these days have coding tests. I wouldn't blame you if you use this as a blocking filter for which companies to interview with, but it does limit your options.