matt_lo

Random idea…

1. Chunk one inside a YT video 2. Chunk two inside a TikTok video 3. Chunk three on an X thread

And then just post the manifest somewhere that can be read by a client, that then pulls the data in (video, doc, anything)

Obv, not meant for speed or good UX, but if we’re going down the route of decentralization, we can probably leverage social platforms to host chunks of data.

use AI to rewrite all the spells from all the books, then try to see if AI can detect the rewritten ones. This will ensure it's not pulling from it's trained data set.

So this is why RAM prices are increasing...

Color ink sold separately

5 minutes of typeracer saves 1 hour of procrastination

Typing fast is a way to unlock the brain. Anything past 90, you start to focus on exactly what is needed to type accurately with speed.

I average around 106-130 (depending on recent races) for the past 15 years, and it's still one of the best ways to "get into dev mode" really quickly.

What platforms do you typically use?

Great book. I think it’s more ideal for folks who solution design day-to-day. Better when you have experiences to relate back with.

I use Todoist to log work for my company ChipBot.

I have a groups like feature requests and backlog for catch-all tasks. Then for deadlines I use "Mid January" or "End of January" and move tasks into them, based on a rough hour estimate. Story points doesn't matter because I'm not quantifying complexity across a team members. It's just me working on it.

I work on the tasks that have the highest priority, build locally, test them in a QA instance, and then ship them to prod. I usually run smoke tests in prod just to make sure I don't break something.

I used to use GitHub tickets and JIRA, but over time I needed organization that didn't cause a lot of busy work. For myself, Todoist (paid plan) works.

If I need to add members in the future, I'll go back to using GitHub (kanban, labels, milestones). Most likely my marketing team will need a Kanban before I add another developer.

Other notes:

Use tools that get objectives done and don't create micro tasks.

Finally, create tasks during off time like during lunch, while working out, or on a walk break. I generally plan 2-3 days in advance on the exact work I need to get done. Don't over work yourself.

I wouldn't say it's significant. It's a handful of customers who play occasionally. No where near as much as I do.

I run a support bot business.

I play Fortnite almost every day for varying reasons:

- I have adult customers who like playing/talking with someone who makes what they buy.

- I have former colleagues I talk to and catch up with.

- I have gaming friends who want someone whose competitive to play with.

- I use it to decompress for the day... or add a ton of stress, depending on whether I can "edit my builds" fast enough for the dub.

tl;dr: From my perspective, Fortnite is a social network.

Right now most chatbot widgets are scripted and require forethought from the admin or business owner. So it's pretty hard figuring out the comment questions on your own or formulating them over time. Even harder when you don't know your customer journey or haven't solidified the ideal customer fit.

This is exactly why I created a bot [1] that blends chatbots and Stack Overflow together. You can have an automated first-line support system without scripting or conversational dances.

- Instead of conversations, you can reuse previous question/answers. - Instead of guessing FAQs, you can let your users define them for you. - When questions don't exist, they get catched in the traditional support flow (email). Then overtime, this effort declines.

[1] https://getchipbot.com

Both. IPs should appreciate in value because of the limited allocations.

Eventually Amazon is going to rule us all.

I wish this was a React lib with components styled already.

Value-add is for engineers who use React day to day already or want to use a minimal API to work to build their UI.

Don't take my word. Checkout the popularity of React, it's proliferation into the marketplace, and it's use on production environments. Also Vue is another popular alternative that UI engineers like to use, which also has SSR.

You can run server side rendering. This is becoming increasingly common to do in new projects.

If you're raising 1M+ in the midwest, it's straight forward. Get a meeting with a VC associate in the region (Chicago: HP VC, Origin, OCA) and they will tell you exactly what they're looking for in a Series A.

I've never had any success with getting institutional money at the seed stage, but if you do get it, it's even easier to bypass some of the troublesome checklist items you get in the A round.

you weren't the only one :P

Adwords is almost useless at this point, though neither of us has had any prior experience so it could just be us not using the tools to their full potential.

For our B2C company, AdWords turned out to be a stable revenue driver for us. I had little experience in it (I'm a software engineer) and it took about $3k burned over 60 days to really understand how to build a profitable acquisition model using AdWords. I bought a couple books and worked on a bunch of multi-variant testing. I eventually obtained a sustainable and predictable process of obtaining revenue.

Never use AdWords Express, spend about 160 hours minimum of learning how marketing and PPC works, and use only data to drive decisions. ROI comes 4 months later when first starting out. If you're an engineer, AdWords API is a really useful to combine CRM and user data to discover new keywords and personas.

All the false positives from perceived success.

At first when I landed, I thought this was another Facebook tech site since the template was reused from the old site of Jest and React Native.

EPIC

I built https://learnfrontend.com as an effort for me to A) teach people front-end development and B) to quit my consultant job so I can focus on making a difference in people's lives. The site features a news aggregate, videos, articles, goals, and interactive training platform.

The site is built on Symfony 2.5, PHP 5.5.x, Postgres, AngularJS 1.2.x, and SCSS. I use Jenkins for CI, Doctrine2 as the ORM, Redis for session I/O, Composer/Bower for dependency resolution, GitHub for documents, tickets, code reviews (pull requests to my self). HAProxy is on standby for the need to load balance and I have a job on Jenkins to scale up and down to a box if needed. I'm currently adding a Docker/Vagrant setup to I can easily manage dev environments (I don't think I'll do the same for production, we'll see). Stripe handles payments, I bought some cheap SSL cert (Stripe handles PCI info outside the server I/O). New Relic is used to monitor both QA, production and my jenkins deploy box. DNS is handled by GoDaddy. I have a Cron handling the news aggregate refresh, diff logic to populate new articles to a mobile curator app I built, and an approve/deny system that determines which articles are allowed to be propagated to the users. Videos are hosted through a third party service and assets internally are handled stored through S3 with CloudFront URL signing assets.

Although it just released, I have received a large amount of important feedback thats going to dramatically change the site. This includes offering more to the user for free, create more interactive components (my writing is too boring / too technical), and improve the marketing (showing the actual tools). I have some POCs in the works for a simulated IDE on edge Chrome/Firefox (uses WebWorkers to observe stackoverflow-able code w/o crashing browser, ScalaJS and Angular port on ScalaJS as MVC frontend; the experience is very much a level up from CodeAcademy's IDE-tutorial).

I'm also in a transitionary period where I want to build the new tools and reconstruct the existing ones in Scala (using Play as the framework). I have more time than before since I saved a significant amount of money to pursue this (I built v1 part time, 30 hours a week for 6 weeks with 30k lines of code added). The force behind this decision is I want more experience with functional programming while leveraging what I know already (JVM / Java).

One of the critical experiences I've had was actually materializing an idea and shipping it. Failing fast and often is an important strategy that's working for me after launching v1.

TL;DR: Built an e-learning site. I learned from failures. Building next version thats going to be rainbows and shit (thats the plan at least).

TL;DR: I use Angular (or * framework) simply because I can rapidly develop the features and adhere to ALL the requirements. ExtJS doesn't suck, but it typically doesn't fit into scope or doesn't fit all the requirements.

ExtJS is a great way to facilitate development when working with large data sets that involve (as you mentioned) CRUD utilities along with business validation constraints. With that being said, these kind of tools (And KendoUI too IMO) are being stuck inside intranet systems where the custom widgets and tools remain proprietary. No visibility == no hype.

I work exclusively on FE stacks and if the choice is Angular or any other top TODOMC* frameworks, typically that means the requirements don't fit well with ExtJS. Most JS-engine driven apps typically require a responsive implementation (cross platform is a big business trend), ability to incorporate a comprehensive design, and being able to do it within a reasonable amount of time (which is associated with budget).

ExtJS has a ton of overhead (especially browser performance and scalability in SPA sites), a large learning curve (IMO), and requires a ton of time to implement custom designs. This doesn't mean there aren't great tutorials or start kits, but its not something you can master within a week. Responsive support OOTB isn't there (KendoUI has solutions for this on their framework) and the only choice for reusable code for portable devices is an adaptive approach using Sencha Touch. This doesn't mean ExtJS is a bad choice, but typically ExtJS excels in desktop apps that are data driven with designs that were made for ExtJS (its rare to not recognize an Ext app if its built on Ext).

There's my two cents. I'm sure Sencha is going to destroy me if they ever read this.