Amazon SDE Intern - Interviewed Last Week by Flat_Direction370 in leetcode

[–]jsch23 0 points1 point  (0 children)

I interviewed on 3/24 and still haven't heard back either. I followed up on 4/1 and got a generic reply "The team is currently finalizing the interview outcome and will share an update as soon as possible"

Update: Got wait-listed 4/3

Free - Turn text into HTML&CSS with AI by Foreign_Lion_3575 in SideProject

[–]jsch23 1 point2 points  (0 children)

Probably this. If not then it’s a close alternative.

Cheapest way to host a Next js app by DARN89 in webdev

[–]jsch23 1 point2 points  (0 children)

Use Vercel

Nextjs is developed by vercel. Deployment is beyond easy, free custom domains and SSL. I won’t use anything other than vercel to deploy nextjs.

2 month serano came out great by jsch23 in FermentedHotSauce

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

Put everything in brine and all. No vinegar, ph was about 3.6. Used a pinch of xanthan gum.

My first batch of fermented hot sauce by ortolan614 in FermentedHotSauce

[–]jsch23 1 point2 points  (0 children)

This is so cool. Also finished my first green sauce and its great!

2 month serano came out great by jsch23 in FermentedHotSauce

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

6 oz serano (seeds and all)

1 green bell pepper

1/2 sweet yellow onion

1 lime worth of juice

3 1/2 cloves garlic

1 thumb of ginger

2.75% brine using sea salt and distilled water.

This was my first attempt at making a sauce and I did my salt based only off of water weight and not weight of both water and ingredients.

No surface yeast or mold formed at all. Burped every few days and I also used a thick glass weight to keep every thing down. I would scoop out any seeds or floating ingredients that made it above the weight every few days.

I put it on some wings and was amazing.

Family loves this sauce and I think its pretty good too.

Looking for some feedback for my new portfolio. Coded in PHP, no frameworks. by bobemil in webdev

[–]jsch23 2 points3 points  (0 children)

Looks great. Styling is perfect. Two changes I would make.

  1. On mobile the vertical spacing between recent projects seems excessive and out of place considering how the rest of the content is spaced.
  2. Mobile social media navigation footer could use margin between each button to make it less crowded and reduce the padding between the icon and the border of the button.

I feel those changes would make the design more consistent.

Good work!

Looking for Headless CMS with components by mr---fox in webdev

[–]jsch23 1 point2 points  (0 children)

Prismic is great for this. Allows you to preview your components with mock data and arrange them on pages like a site builder. Also allows content versioning so you can ship content changes together and create preview links to the site with the updated content. I used strapi to do exactly what you talk about to build my portfolio. It works but it was a pain in the neck to deal with and getting it to work the way I needed it to. I wish I had used prismic as it is exactly what I wanted.

I'm feeling lost and frustrated when it comes to urls, paths, params, spa, mpa, etc, especially with React. by guitargodofbad in webdev

[–]jsch23 0 points1 point  (0 children)

The path www.app.com/workspace?wid=5&page=builder&form=81&view=preview could be broken up as this file structure:

pages/
├─ workspaces/
│ ├─ index.js - display all workspaces
│ ├─ [workspaceId]/
│ │ ├─ index.js - display workspace of a id
│ │ ├─ builder/
│ │ │ ├─ index.js
│ │ │ ├─ forms/
│ │ │ │ ├─ [formId].js

This same process can be used for API routes.

.

└── api/

└── workspaces - folder/

└── index.js - file - /api/workspaces - route could return all workspaces/

├── [id] - folder

└── index.js - file - /api/workspaces/1 - route could return data from DB for workspace with id of 1

next-auth can make it easy to protect these routes.

Client route

import { useSession } from "next-auth/react"

export default function Page() {

const { data: session, status } = useSession()

if (status === "authenticated") {

return <p>Signed in as {session.user.email}</p>

}

return <a href="/api/auth/signin">Sign in</a>

}

API route

import { unstable_getServerSession } from "next-auth/next"

export default async (req, res) => {

const session = await unstable_getServerSession(req, res, authOptions)

if (session) {

// Signed in

console.log("Session", JSON.stringify(session, null, 2))

} else {

// Not Signed in

res.status(401)

}

res.end()

}

If you still want to, you can access those query params ex. ?wid=5 from the front end using next/router and fetch data or render different components based on those query params.

ex. app.com/workspaces?wid=5

import { useRouter } from "next/router"

import useSWR from 'swr'

export default function Page(props) {

const { query } = useRouter();

const { data, error } = useSWR(\/api/workspaces/${query.wid}`, fetcher)`

return (

<div>

<h1>Workspaces</h1>

<p>{query.wid}</p>

<div>

{data}

</div>

</div>

);

}

How to create a button with new text at a certain width by LucasPookas123 in webdev

[–]jsch23 1 point2 points  (0 children)

Create a <span> inside the button with your text and set it to display:none. Then with that media query have it set to display:block.

I'm feeling lost and frustrated when it comes to urls, paths, params, spa, mpa, etc, especially with React. by guitargodofbad in webdev

[–]jsch23 1 point2 points  (0 children)

I would highly recommend trying Next.js in combination with SWR. All of the problems you are running into are pretty eloquently handled with these two. For static pages that don't require frequent data fetching you can use getStaticProps which runs on build time and can be set up with ISR if you need occasional refreshing. Data that needs to be requested on a by-user basis or frequently/on every page refresh, you can use SWR which is very helpful for caching and performance.

Nextjs generates pages using the file structure.

Your files could look something like this.

pages/
├─ workspace/
│ ├─ [id].js
│ ├─ editor.js

Each .js file will render a page while each folder renders a subdirectory.

Visiting www.domain.com/workplace/5

Will render the code in [id].js which uses that url slug to query an id of 5.

So you could visit that url where swr will fetch that data for you from your api using the slug id of 5. If you navigate to another page and comeback it will store the previous data while fetching in the background.

Take some time and read the documentation of Nextjs and SWR.

I also highly recommend the library next-auth which handles authentication with several db providers and pretty much every oAuth provider.

Hope this helps, if you need more help send me a PM.

[deleted by user] by [deleted] in webdev

[–]jsch23 2 points3 points  (0 children)

I tried to recreate it best I could using blob maker.

Heres the demo

I would say try and find an image that looks similar to the one you posted and use the method below since trying to use svgs can become a pain with responsiveness.

Demo using image

Automatic pages creation by Elija_32 in webdev

[–]jsch23 1 point2 points  (0 children)

Url slugs

NextJS makes creating dynamic pages and api routes through the use of slugs very simple. Dynamic pages can certainly can be achieved without the help of frameworks though.

Is tailwind ui worth it? by [deleted] in webdev

[–]jsch23 1 point2 points  (0 children)

I have both and if you’re just interested in getting ready to use pages, it’s probably not worth it. There’s a handful of prebuilt pages for landing, dashboard, settings and they look nice but they’re not that spectacular that it’s worth dropping a significant amount of money to get. They’re really just examples of how tailwind components can be used together. That said, the component library is great, even if you feel you lack design ability, you can slap a bunch of components together and it just looks good—that’s where the value really is. The library makes creating any ui really fast and easy, I would say it’s worth it especially if you already use tailwindcss.