开发者

submitted by /u/fagnerbrack [link] [留言]

Slowly Changing Dimensions: Types 1-3 with Examples Alex Merced Alex Merced Alex Merced Follow Feb 19 Slowly Changing Dimensions: Types 1-3 with Examples # data # database # dataengineering # tutorial 1 reaction Add Comment 4 min read

I got some time to kill and honestly I'm just itching to solve a problem nobody gives a shit about cause there is no real money in it. IE social impact rather than financial , maybe something that helps charity and non profits, or a hobby that wishes it had a tool to make life easier but wouldn't actually pay for, etc etc submitted by /u/AssistanceAshamed609 [link] [留言]

I’m building GoWDK , a Svelte-inspired web framework for Go. Honestly, I’m starting to wonder if I’m wasting my time. I like Go, but web development in Go still feels too verbose when you want modern component-based apps. Most options either feel too backend-only, too manual, or they push you back into JavaScript-heavy stacks. So I started building GoWDK to test a different path: Go components server-side rendering simple syntax minimal JS Go-native tooling compiler-driven DX The frustrating part is that building a framework is a lot of work, and I’m not sure if Go developers actually want this kind of thing So I’m asking honestly: Would a Svelte-like framework for Go be useful to you, or am I solving a problem most Go devs don’t care about? Repo: https://github.com/cssbruno/GoWDK submitted by /u/OkSeesaw7030 [link] [留言]

submitted by /u/Short_Map_2488 [link] [留言]

Local-first agent trust console with a safe local workspace Discussion | Link

This is an updated rewrite of my 2021 article on protected routes . A lot has changed in the React ecosystem since then. React Router moved from v5 to v7, class components have faded out, and the patterns we use for authentication state have matured. This version reflects how protected routes are built in modern React applications. Almost every web application requires some form of authentication to prevent unauthorized users from accessing parts of the application meant for signed-in users only. In this tutorial, I'll show how to set up an authentication flow and protect routes from unauthorized access using modern React patterns: function components, hooks, React Router v6+, and the Context API. First things first Install the dependency: npm i react-router-dom That's it. React Router v6 and above ships as a single package, so you no longer need to install react-router and react-router-dom separately. It is worthy of note that we will not be using Redux for authentication state in this version. For something as simple as "is the user logged in?", React's built-in Context API is the standard approach today. Redux still has its place, but it is overkill here. The Auth Context Instead of writing to localStorage directly from components and reading it in random places, we centralize authentication state in a context. This gives us a single source of truth and a clean useAuth() hook we can call anywhere in the app. Create ./src/auth/AuthContext.jsx : import { createContext , useContext , useState } from " react " ; const AuthContext = createContext ( null ); export function AuthProvider ({ children }) { const [ user , setUser ] = useState (() => { // Rehydrate on page refresh const saved = localStorage . getItem ( " user " ); return saved ? JSON . parse ( saved ) : null ; }); const login = async ( username , password ) => { // In a real app, this is an API call to your backend. // We simulate it here with hardcoded credentials. if ( username . toLowerCase () === " admin

RubyConf holds a special place in my heart. It was the very first tech conference I attended after receiving a scholarship fresh out of Flatiron School back in 2017 (you can read about my experience here ), and then in 2021, it was the stage for my first conference talk in Denver. Now, in another first, I joined the Program Committee for RubyConf 2026 to help put the program together, and what a program it is! We have an absolutely amazing lineup this year, and I'm so excited to see it come to life! Who else is planning on attending? Let's make plans to meet up and say hi!

I've been using pronounciation apps for a few weeks and decided to intentionally butcher some words just to see how strict the feedback was. not subtle mistakes either. I was fully committing to the wrong pronunciation. I've noticed that it still rated some of them as correct or nearly correct. now I'm wondering how much trust I should actually put into pronunciation scores in general. do these apps genuinely analyze pronunciation, or do they sometimes just check whether you're vaguely in the right area? submitted by /u/no-cherrtera [link] [留言]