What is Reddit's opinion of
DEV Community?
From 3.5 billion Reddit comments
➔ DEV Community website
By popularity on Reddit, this Service is:
100 reviews of this app found across Reddit:
The video interploates between individual images it has generated.
The program (RunwayML) has image generation algorithms that have generic models (objects, landscapes etc) and you can refine them by feeding it with similar images on top of that.
Here's an article on the jist of it:
https://dev.to/jochemstoel/runwayml-next-generation-machine-learning-for-creators-1b4p
I didn't really do much myself apart from knock up a dirty python script to source a load of images. But it killed an afternoon of boredom and I quite liked the results!
(disclaimer: I am not the author of this article)
Ran across this uncharacteristically high-quality post on DEV.to today, and thought I'd share it here. It is a nice aggregation of the state of different UI crates.
I may be wrong but the way you speak make me think you come from a more rigid OOP language.
Welcome to the jungle.
Depending if your developing an API, a server serving webpages, using or not SSR, building a desktop app, or a CLI app... What will make your life more easy won't be the same.
​
In today development, usually we don't group file by concerns (like a controllers folder or a single folders), but more by functionality, you can take a look at this example for inspiration : https://dev.to/lars124/how-i-structure-my-rest-apis-11k4
For entry point nothing is standard too : main, index, app.. Nothing mandatory...
People, please don’t go to this site. They ripped it off of Christopher Noring. Idk what kinda fishy shit the site owners (and OP) are up to but, it’s no bueno.
Here’s the original: https://dev.to/softchris/5-part-docker-series-beginner-to-master-3m1b
Hey, I created Edabit! Sounds like you would really like this post I made on learning to code. It's pretty much exactly what you're describing and the entire reason I created Edabit in the first place! :)
I couldn’t view the site because it insists on trying to contaminate my computer with Obfuscript[0]. Please label any site that:
- uses javascript of any kind
- uses non semantic tags such as <div> or <span> [1]
- uses images
- is displayed in anything other than the browser default font
- changes the colors of the page beyond what my browser preferences specify
- is hosted by a cloud provider [2]
Thank you.
[0] https://www.gnu.org/philosophy/javascript-trap.en.html
[1] https://dev.to/kenbellows/stop-using-so-many-divs-an-intro-to-semantic-html-3i9i
More info (from the author of FastAPI) on the drama that pulled this from 3.10 at the last minute to protect Pydantic/FastAPI/etc...
A best of both worlds approach is being worked on for 3.11
I usually get news from Reddit. A lot of people post interesting projects, tips & tricks and discussions that lead you to good sources. I would suggest to subscribe to: r/python r/learnpython r/pythontips r/pythoncoding
For tutorial/articles checkout https://realpython.com https://dev.to/t/python
For video tutorials checkout https://m.youtube.com/user/sentdex
I’m sure there’s a lot more! Any other suggestions?!
body-parseris pretty awful and is used by many node applications. Send it incorrect JSON inputs and it'll error out, potentially killing the application if not handled correctly.Sending node a burst of concurrent connections along a request path that will cause a lot of IO events to trigger may also cripple node, as the standard library (which a lot of developers utilise) is generally blocking: https://nodejs.org/en/docs/guides/blocking-vs-non-blocking/
If you're trying to be reeeeally crafty, a major weakness in the NPM ecosystem was exploited to effectively install malware into a package that was a dependency of countless other packages causing it to be downloaded if
npm installwas run during the time it was live. This ecosystem is incredibly intertwined with pretty bad security practices. If you had a target application in mind, you could try to figure out a particular node module they were using, find out all of its dependencies (and dependencies of dependencies), and somewhere along the line you attack the weakest link to publish a malicious version of a package that is eventually installed onto the server in question (as well as likely many others!).
There's a lot of others out there but that should give you some starters :)
Repost of a comment I gave last time this came up:
Theirs nothing inherently wrong with the bootcamp route but if you're going to spend the money on it, I would dip my toe in the water first. Software engineering is one of the most egalitarian industries you can be in, and to boot, everything you could possibly want to learn is free online.
Want to be a front end developer? Here's the first link I found which looks fine to me: https://dev.to/theme_selection/how-to-become-a-pro-front-end-developer-5gbo
Read. Figure out how to build a website. Figure out how to host it somewhere (free services abound). Learn by doing. If you have a computer, any sort of computer, you can build a website. It will be shit but it will be a start. All the bootcamp will do is teach you the same things but charge you for it. The best thing you can do for yourself is give yourself a head start on what they teach you my doing your own learning.
I'll repeat what I've posted in other threads, but as someone that hires software engineers and has been a software engineer for ~20 years (shoot me now) here is my advice:
> Their blockchain is already 40% larger than BTCs and it’s only 2.5 years old vs 9 years for BTC.
That's not blockchain, that's "the size of datadir" which has a lot of cruft.
Actual blockchain size as of Nov 29, 2017:
> Currently, the raw historical block data containing the blocks and transactions is approximately 12-15GB in size and the latest state around 1-2GB.
https://dev.to/5chdn/the-ethereum-blockchain-size-will-not-exceed-1tb-anytime-soon-58a
This set is a follow up from the previous set simple CSS loaders.
This time I've written up my thoughts behind making them.
That's a little disingenuous: https://dev.to/5chdn/the-ethereum-blockchain-size-will-not-exceed-1tb-anytime-soon-58a
Ethereum does not need to store the full state like bitcoin does, it was designed with merkle patricia trees in mind and state syncing that obviates the need to actually download and store every block ever created. My full node right now runs 105 GB, which is lower than bitcoin and bitcoin cash.
I think the point is that it is organized... but in a way that isn't necessarily logical. You're grouping them by the type of thing they are, rather than the function they provide. Look at the examples here, and how they divide the reactive properties into groups by functionality, rather than whether they're methods/computed/data.
Let's leave Vue behind for a second. Think about it that way: what if in TypeScript you had to declare variables like this:
array { dialogs, popups, listItems }
boolean { isDialogOpen, isPopupOpen, isLoaded }
string { dialogsTitle, popupsButtonTitle }
as opposed to
// Dialogs dialogs: array isDialogOpen: boolean dialogsTitle: string
// Popups popups: array isPopupOpen: boolean popupsButtonTitle: string
// Is loaded isLoaded: boolean
Technically, the first way is more "organized". But it's organized in an arbitrary way, that spreads blocks of functionality across various sections.
Plus, in the second way, you could encapsulate one of those bits of functionality (that includes mixed computed, data and methods) into a separate function, and reuse it in other places.
I agree that languages should have efficient memory handling like this, but I also want to say that garbage collection gets a lot of unfounded criticism. For example, I read this article recently about optimising the number of allocations in a C# program. Skipping to the results, at the start the program takes 8.8s to run, and there's 7.4GB allocated over its lifetime. Now that sounds bad, but then you look at the peak working set, and see that the most memory allocated at any one time was just 16.7MB. The author applies a variety of different strategies to reduce allocations, and by the end, the program is down to just 32KB allocated over its lifetime, but still takes 6.7s to run; you'd really expect a larger performance boost than that, but no it turns out those allocations were very cheap. Even just after their first attempt to reduce allocations, they have it down to 4.2GB allocated, and the program already takes only 6.9s to run. Extrapolating from there, from all the rest of the work they did to remove the rest of the ~4GB of allocations, they only gained ~150ms in run time, and in doing so they made the code far less readable and intuitive.
While this chart is technically correct, it's not the full picture. You can run a fully verified node with significantly less space:
https://dev.to/5chdn/the-ethereum-blockchain-size-will-not-exceed-1tb-anytime-soon-58a
Sharding will furthermore reduce the size required even further.
I suggest checking out this project which Richard Feldman created especially as an example of an Elm app with multiple pages at “real world” scale.
Here is a writeup of how it works:
https://dev.to/rtfeldman/tour-of-an-open-source-elm-spa
It uses a lot of techniques that you might not need, or might not need at first – start simple and only add abstractions as you need them. The basic thing is that the app’s model ends up having a union type of all the pages in the app:
https://github.com/rtfeldman/elm-spa-example/blob/master/src/Main.elm#L31-L41
Like medium.com, dev.to articles generally have the quantity-over-quality factor associated with it
Personally, I'm still a fan of both websites since it lets people easily create and share content.
Everyone at our company (Xojo) works remotely and I've personally been working remotely from home full-time for over 10 years now. I don't think I could back to an office at this point.
> The total data directory size of the entire chain of blocks is the blockchain.
That's under 100 GB. That's the entire chain of blocks. The whole chain, including all the blocks with all the transactions. No blocks or transactions thrown away. The whole blockchain.
I know you read /u/5chdn 's piece, but you might want to go through it again slowly, as the various options can be quite confusing, and some of the terms have different meanings to the way they're used in Bitcoin: https://dev.to/5chdn/the-ethereum-blockchain-size-will-not-exceed-1tb-anytime-soon-58a
So what's the thing you've got the number from, the archive node? Trying to put things in Bitcoin terms, I guess the states you keep in an archive node would be more like snapshots of each individual intermediate UTXO set. AFAIK nobody actually keeps such a thing and you wouldn't really want to in the UTXO world (possibly one of the meta-protocol clients might for some reason?). If you've got the blockchain, you can recreate this at any point in history by replaying the transactions, so you're not losing any data by not running an archive node.
Git is a very useful concept to learn even for hobbyist developers and pretty much mandatory to know in a professional environment. Github is just a web based version of Git that makes the process much easier!
You can read more about the concepts of Git here (Bit long but comprehensive):
https://dev.to/unseenwizzard/learn-git-concepts-not-commands-4gjc
For an even quicker and easier start, Github has good introductory hands-on tutorials:
https://lab.github.com/githubtraining/introduction-to-github
and a follow up specifically for you:
https://lab.github.com/githubtraining/uploading-your-project-to-github
The hard bit would be learning how the algorithm works.
Once you know that, brute-forcing it is no problem.
To figure out the algorithm, you can look for patterns in the cipher text, or hit a PoW with a spanner until they tell you.
Thanks for this. I was concerned too when I first had a look at wasm and all the first links I've found were boasting generate, node, npm and other nonsense.
The useless nightmare of webpack and other tools managing at the same time to claim simplify things and making even the simplest ones painful, obscure and magical should absolutely be avoided in Rust. We don't want people to randomly copy recipes into configuration files until something seems to work.
I found a tutorial when i googled "i hate powershell". It gave me a new perspective on it and now i start to even like using it.
Edit: Found it!
Counterpoint: https://dev.to/paragonie/php-72-the-first-programming-language-to-add-modern-cryptography-to-its-standard-library
Enjoy your RSA-PKCS1v1.5 stones while PHP developers get to enjoy their Curve25519 hammers.
It's good to see progress with ROCm on RDNA 2. As for Pytorch, I documented my struggles in this article: https://dev.to/fredwessberg/training-esrgan-seemingly-impossible-67k. In the end, I actually gave up. For some things still, CUDA is simply a requirement. But I'm glad to see that landscape change slowly into something that is less prone to vendor lock-in.
Everything that you do, plus
- Posting in Reddit (in similar subreddits)
- Finding related questions in Quora and answering them
- Post in related forums (for me I run a dev blog, so dev.to and hashnode.com)
- Send a broadcast message to all FB Messenger subscribers (via MFY.im)
Microsoft has some good docs, you can start with this to get a feel for it. https://docs.microsoft.com/en-us/aspnet/core/tutorials/web-api-vsc
We host all our of services in docker on Linux, so when the time comes for you to try that, here is a beginners guide https://dev.to/schwamster/docker-tutorial-with-for-aspnet-core
Hopefully this gets you started. If you have more questions I can try to answer as well.
Every connection I ever made was made through Meetup.com.
Don't discount the value of a local dev meetup group. (Protip: don't show up like a beggar, handing your business card out to every person you meet. Engage normally, and try to give as much as you receive).
There are a number of online communities that you can engage with as well. Just for the sake of naming names, there's Code Newbies and Dev.to.
But literally, for any technology or concept that you're using, you can find a slack group somewhere out there for it.
Finally, if you have a few dollars to spend, you can also attend tech conferences. The "hallway" conference (i.e., talking to people in the hallway between talks) is infamous for connection building. They tend to get pretty pricey, though, so unless you have a decent job, I'd suggest going with the first two suggestions for the immediate future.
As stated in the issues linked by wsppan, you shouldn't take for granted that there will be an http server in the stdlib.
It will take a while before you will see a fully-featured, production ready HTTP server implementation, so here's a hot take: instead of waiting till then, write the HTTP layer in Go or Elixir and use Zig to implement the business logic.
For Elixir, you can use https://github.com/ityonemo/zigler and for Go you just need to look into the C FFI interface and if you need cross-compilation you can use Go with Zig cc, roughly as explained here https://dev.to/kristoff/zig-makes-go-cross-compilation-just-work-29ho
You could also find an http server implemented in C and use that from Zig, but cross-compilation might be more problematic at that point, depending on how portable the C project is.
Pure functions are good for many reasons, independently of the programming language:
- Their behavior is predictable
- They are easy to test (and refactor)
- They are easy to compose with other functions
- They are easy to execute in parallel
Take a look here to learn a bit more.
Of course, trying to apply a strict functional mindset to a non-functional language may have... side effects. :-) Read this to understand what I mean.
I just offered something similar yesterday. I started a Discord https://discord.gg/rF5FJ5E for helping people working in areas I'm experienced.
If you're curious about my experience, I have an active AMA on Dev.to
TL;DR, what I know
- Machine Learning (classical, deep, both math and software architecture)
- Most major programming languages (C, C++, x86, Java, Python, JS, Haskell etc)
- Distributed computing
- Performance in computing
- Cloud technologies (pretty much have used every AWS service), terraform, ansible, Docker
- Game development
- Game engine development
- Product management
- Design work
- Dealing with college bullshit
Feel free to join the discord and ask questions, dm me on reddit or twitter.
/u/DevMentor if you (or anyone else) wants to help me out and be a "coach" in the discord, let me know.
I don't see any of the problems you do. We currently use it in a very large app, as our main dashboard.
Tools, Resource Tools, Actions, and Custom Buttons are all possible. I am running multiple packages that extend Nova, from the Nova Packages website.
You complain about buttons, I can put buttons and links on the left navigation, but I can also put them right on top of any resource. This is done with nova's "custom-detail-toolbar". Here is a tutorial on how to do it: https://dev.to/jake/laravel-nova-adding-custom-buttons-to-resource-toolbars-1ob5
Our database currently has just over 280 million records in it, Nova is handling it fine.
lol "completely worthless"
You'll be happy to know that you are very mistaken.
Try this tutorial:
https://dev.to/aurelkurtula/creating-a-basic-website-with-expressjs-j92
This. The WYSIWYG post editor, built-in support for things like spoilers and emoji, and infinite scroll are going to help with retention for people who are new to this site. But the comments section really should feel like a proper page switch, even if you are doing it in JavaScript.
I'm going to sound like a broken record when I say this, but their models should be Discourse and DEV. Both of them do page switching in JavaScript, they save your scroll position despite using infinite scroll (Discourse even helpfully lights up the thread you were just in, to make absolutely sure you don't lose your place), and they do it without replacing the actual pages with lightboxes. They act exactly like normal links, except opening them in the same tab is faster than opening them in a new one. Copying Twitter's lazy design is lazy.
Archive nodes are more than full nodes, especially in Ethereum. Archive nodes store the state trie at every point in the past in addition to all blocks. Full nodes just store all the blocks and prune the excess data from the state trie. Archive nodes are more like storing a copy of the UTXO set at every Bitcoin block, which is not something that Bitcoin nodes do. For more information on this distinction, you can read this article:
https://dev.to/5chdn/the-ethereum-blockchain-size-will-not-exceed-1tb-anytime-soon-58a
The best approach I found so far is to view each Page as an entire Elm application, each with its own model, update and view.
In your Main.elm you tie this together by saving some common context data that will be needed by all pages (something like a session) and either all the models of all the pages OR just the model of the current page.
type alias Model = { session : Session , pageOne : Pages.One.Model , pageTwo : Pages.Two.Model , currentPage : Route }
or
type Page = One Pages.One.Model | Two Pages.Two.Model
type alias Model = { session : Session , currentPage : Page }
Each approach has its own tradeoffs. The elm-spa-example uses the second approach.
> they too would be able to purchase the console for $500 “in an hour from now”.
Negative. Scalpers are a problem but they make up a small fraction of the actual demand. Scalpers are maybe 5% of an entire market. https://dev.to/driscoll42/ps5-xbox-ebay-stockx-scalping-market-over-half-a-million-sold-for-104-million-in-scalper-profits-bbo So the people paying scalpers money aren't going to get a console it'll just sell out 3% slower.
I tend to agree, however just to play devil's advocate: Mocked and stubbed out functionality is more unit-like and avoids the "mystery guest" conundrum found in a lot of testing harnesses. It also is a bit more SOLID and doesn't violate the Liskov Substitution Principle (e.g. stubbing out a hash with a hash no matter the values).
Test suites should act as another form of documentation and the simpler the tests, the more likely new engineers will grok the codebase sooner.
But if you are going to mock out the tests, those interactions should also be tested via integration tests. Anyway, I go back and forth: I like following the rule "don't mock what you don't own".
I wouldn't be the best person to provide career advice, but wanted to respond to this point:
>It is really my first experience doing any sort of coding (if SQL counts).
SQL is absolutely coding. While the most common kinds of programming follow the imperative paradigm (e.g. procedural and object-oriented code), SQL is one of several types of programming in the other major paradigm family--declarative programming.
Imperative programming focuses on giving the computer a set of explicit directions that will lead the computer to the desired result. Declarative programming instead focuses on giving the computer a detailed technical description of the desired result and leaving the actual mechanism of how to find upon that desired result up to the computer.
The fact that SQL is declarative rather than imperative doesn't mean it isn't coding. Often, complex manipulation of data sets can be done much more efficiently by an RDBMS via SQL than would be possible via an imperative language... The imperative language usually takes longer to write the code to do it and will often be computationally inefficient at doing it as the RDBMS is already heavily optimized for doing the vectorized arithmetic.
The following article is a really valuable piece I read last year that I strongly advise looking into if you're not sure if SQL should be considered "coding":
https://dev.to/geshan/you-can-do-it-in-sql-stop-writing-extra-code-for-it-lok
Properly used, SQL can replace a lot of completely unnecessary imperative code when working on data sets and will do so much more efficiently than anything a non-genius coder is likely ever to write.
Solve your own problems first. Scratch every little itch you can think of, and do it with Python. You will end up with a bunch of little scripts and things that individually don't mean much but collectively grow and sharpen your skills.
/u/M34k3 is right. Think small. Write a Python script that scrapes a weather API and emails you every morning with the weather forecast for your area. Write one that emails you a daily digest of Dev.to posts that mention Python, ranked by the number of likes or comments or something. Write one that pulls royalty free images from the internet, overlays corny motivational quotes, and posts them to a dumb Instagram account. None of those ideas will make you rich, but they'll teach you skills.
From https://dev.to/rtfeldman/tour-of-an-open-source-elm-spa
> Fair warning: This is not a gentle introduction to Elm. I built this to be something I'd like to maintain, and did not hold back. This is how I'd build this application with the full power of Elm at my fingertips. > > If you're looking for a less drink-from-the-firehose introduction to Elm, I can recommend a book, a video tutorial, and of course the Official Guide.
The links to those are in the article.
type Username
= Username String
This is about encapsulating the String type. This protects any random String value to be used as Username or vice versa.
As a general advice on your question. The functional programming style makes for very declarative code. So I'd say read the code function by function. When you see another function being called, just assume for a second it just does what is says it does. Once you've figured out the exact purpose of the current function you can move on to the next.
This question comes up often on the mailing list and is something the community is working hard to provide better initial documentation around!
One amazing reference that was produced recently is Richard's elm-spa-example: https://dev.to/rtfeldman/tour-of-an-open-source-elm-spa.
I've written a couple applications with a similar structure and I plan to refactor them soon to be extremely similar to this, as it works very well as the application grows.
One tip though—make sure not to prematurely-modularize! I did that recently with a small internal utility with a few standalone widgets—one per page. Every widget's page was its own entire module subdirectory with its own view, update, model, etc. While the separation is quite clean, it's a ton of boilerplate for widgets that often could've been written as just 20-30 more lines in the top level module view/model files.
Increasing a dynamically allocated disk just increases the free space available on said disk. However, you still have to expand the partitions / filesystem within the VM to occupy said free space if you want to take advantage of it.
See - https://dev.to/rishiabee/how-to-expand-a-linux-partition-using-gparted-31c3
IIRC if you have $100k-$300k and the will to administrate it, you can make your own TLD.
I think it is worth it. I think this blog post can be helpful.
I could get some job offers with that.
I dual boot between Linux and Linux w/XFCE desktop environment - and the one thing i really, really find useful is a file manager with optional dual pane support
Honestly - it's the greatest thing since sliced bread - press F3 and you've got dual pane mode.
That and Terminator for a terminal - i can split it into multiple terminal windows with a right click.
Add those 2 features to Explorer and Windows Terminal and i'd be really impressed.
Spring is largely based on DDD (Domain Drive Design) When you get into any real professional java development, you need to understand how to abstract and model a business domain.
https://dev.to/colaru/creating-a-domain-model-rapidly-with-java-and-spring-boot-i85
IP Address isn't ideal if your users are behind a firewall and sharing a public IP.
A quick google for "django allow only one session at a time" resulted in this find:
​
https://dev.to/fleepgeek/prevent-multiple-sessions-for-a-user-in-your-django-application-13oo
​
That seems to detail a more durable approach. You should build what your use case demands, though. But the shared IP is something that can be overlooked.
I'm not an expert in marketing. But here is what I usually I do
- Write quality, in-depth content that you're passionate about and you've in-depth knowledge
- Post of relevant groups related to your nice. My nice is web development. So after I publish a post, I post them in development subreddits, some forums like Dev.to, Hashnode, some FB groups etc.
- I don't spend time building DA, PA or backlinks (expect to post like above). I believe if you write quality content those are built automatically. PS: I got a backlink from Hacker News without doing anything! I don't even check my DA yet!
- Avoid keyword research and keyword stuffing
​
I recently started another blog (wpspeedmatters.com) that focus on WordPress speed optimization. That one is also getting really good traction. The FB group I started is something I would highly recommend. You can share new posts. Moreover, you get to know what are the real problems of people in your nice and focus on content beneficial for them. Find similar groups/forums related to your nice. Spend a lot of time in that. Analyze the visitor's problems and write accordingly
Medium.com is NOT a good place to go. You'll see a lot of articles pointing there, but they're often either behind paywalls or click-baity titles.
and twitter are usually where I'm at to find new information. You can also find useful stuff on css-tricks and some other developer focused places, just have to look around.
I assume it's a piss-take of go's continued lack of generics. Though they'll probably add them eventually and then in typical go/google cultist style they'll have been a brilliant idea all along. https://dev.to/deanveloper/go-2-draft-generics-3333
I hadn't heard of event projection so I Googled it and read this additional article, which others here may find useful: https://dev.to/barryosull/event-sourcing-what-it-is-and-why-its-awesome . I still don't completely get it but at least now I have the beginnings of an understanding of it.
Do you have SSH access? If you don't, follow this article
If you do, follow this one
https://github.com/petehouston/laravel-deploy-on-shared-hosting/blob/master/README.md
That's a feature.
Many major tech companies have divisions writing in Clojure. It solves problems better than typed languages.
https://dev.to/danlebrero/the-broken-promise-of-static-typing
I have seen exactly one site (https://dev.to) where the attempt, while not a huge improvement, hasn't been a regression. I'd be willing to believe there are a couple more out there. Most of the time, it's a lie. Most attempts, such as Facebook, Youtube, and now Reddit, all feel significantly worse.
I can't seem to get past first round. Ugh. But these articles are cool: https://www.quora.com/How-can-I-overcome-the-discouragement-from-being-rejected-by-all-the-top-tech-companies-I-have-applied-to
https://dev.to/theobendixson/fail-your-whiteboard-interview-dont-mope-about-it-monetize-it-e18
Check out dev.to
It's similar to Medium, but built specifically for software developers. Ben Halpern built it after success of his (at the time) satirical dev twitter account ThePracticalDev.
Edit: Also checkout IRC chats; I know ##javascript and #reactjs are fairly popular and active. (I'm on both)
With github, you will be using a webhook to interact with s3. Youll likely use a programmatic AWS user you create for this purpose, then load the Secret + Access key for that user (who has a policy allowing them to access the bucket in question) as a github secret. Then you can define a github action referencing the secret.
Decent writeup of the process here: https://dev.to/johnkevinlosito/deploy-static-website-to-s3-using-github-actions-4a0e
It might not be as common with R, but often people write boilerplate code which is just a kickoff to structuring a codebase. Often boilerplates will include some of the setup for interconnectivity between frameworks as well, such as these Node, Express, and beyond.
The readme could better convey what the code is, but what it is appears to be boilerplate. The best boilerplate I can think of for R is Golem's. Package of Shiny App Using Golem generates a bunch of files and directories. I think Drake also generates boilerplate.
Over the last year or so, I've been using Transcrypt to create React/Material-UI front end web applications coded with Python. You use the JavaScript library API's but code to them with Python instead of JavaScript. The resulting Python code is clean and fully lintable. Since I've started using Transcrypt, front-end development has actually been enjoyable for me.
To give you an idea of what it looks like, I did a write-up a while ago on converting the official React Tic-Tac-Toe tutorial to use hooks, but using Python instead of JavaScript.
it's interesting to note (at least to me) that some emoji outside of the skin tone modifiers are already constructed like this internally - the spaceman emoji is encoded internally as a person emoji and a rocket emoji with a special "connector" character placed between them - the rocket emoji "modifies" the person.
https://dev.to/joeattardi/how-emojis-work-3a2g
so I have no idea why there's not already say, a left arrow + the finger gun emoji to create a left-pointing finger gun, outside of the extremely slow application process you have to go through to suggest changes to the emoji system.
eh. emoji are weird.
Hi//u/aldonley, your point about resolvers is less of an issue now that Amplify supports direct Lambda resolvers. This means no more VTL, which I can imagine alleviates a large amount of pain.
The actual principles of React's implementation aren't too complicated, but yeah, the real codebase is pretty complex.
There was a recent article collecting several "build your own React" posts here:
https://dev.to/iainfreestone/9-examples-of-building-your-own-version-of-react-51a8
And I have a long list of articles on React's internals here:
https://github.com/markerikson/react-redux-links/blob/master/react-implementation.md
As a general observation: all the actual logic is implemented in the react-reconciler package. That package gets included in each platform-specific reconciler package, ie, ReactDOM and React Native. The react package is just some data types and wrapper functions that ultimately call into whichever reconciler you're using.
Also, the React repo is undergoing a significant refactor atm - apparently there's some kind of an "old/new" split going on right now. You might want to pick a tag from a slightly older release (say, 16.12 or so), and browse the codebase as it existed at that point in time.
Finally, while it's more about the externally visible behavior, you might be interested in my post A (Mostly) Complete Guide to React Rendering Behavior.
I am an American now living in Germany working as a software dev and I feel fortunate for having the opportunity to live in a non-barbaric country that values the single life that humans have to live. I feel so sorry for Americans who have no idea what living a decent life is like. I was one of those before I moved here by chance. Having had a son within the last year, I can not imagine what it would be like to not have parental leave for more than a year. Not having this is barbaric, both for the mother and the child. Newborns need soooooooooooo much, and mothers need to recover. Not having parental leave is just cruel. Not having a good work life balance is just narrow minded. Living here has given me the opportunity to have enough "down time" and not be stressed about a health issue bankrupting me that I have been able to focus on what is a fundamental threat to our survival: climate change: https://dev.to/pablooliva/how-i-decided-to-fight-climate-change-as-a-software-developer-89n
I found another interesting article: https://dev.to/rdegges/please-stop-using-local-storage-1i04
If you don't mind can you please scroll down to the first comment. The second reply from " Jonathan Gros-Dubois" Please read it and tell me if he is correct or not?
I'm starting to feel like I don't know what is right and what not now :D
What is the evidence for the claim that Docker or Kubernetes are trashy programs? (aside from you potentially not finding them useful)
Are you saying there's a higher density of bugs in them because they're written in Golang? I don't believe there's evidence for that claim at all. insofar as people have looked into empirically determining bugginess of a software, Golang does really well.
We've actually got support for [integrated audio](https://aka.ms/vsls-audio based on the exact realization that you mentioned. As far as use cases, we're finding folks using Live Share in a bunch of different ways, due to the inefficiencies that screen sharing can impose. You can check out more details about why we built Live Share in this post.
See these articles:
Because importing it from a torrent does not allow verifying all blocks, states, and transactions.
You usually don't have to run an archive node. The following configuration will completely verify all blocks and execute all transactions:
parity --no-warp --pruning fast --pruning-history 10000
And this only requires ~70 GB of disk space. On SSD, you can fully sync this within ~ a week. I wrote a related blog post last year:
https://dev.to/5chdn/the-ethereum-blockchain-size-will-not-exceed-1tb-anytime-soon-58a
The numbers are outdated; I am in the process of gathering new data for both Geth and Parity.
I use both for work. If I could sum up the major conceptual difference between them I'd say Python is uniform and predictable, JavaScript is expressive and nimble. So going into JS don't expect a rigid "one way to do it" kind of scenario. This means you'll encounter code created by different people that might look like completely different languages. This is mostly superficial as the syntax of the language isn't inconsistent, it's just extremely versatile. So for JS more than other languages I think it's important to learn patterns. Just googling I found this: https://dev.to/omensah/design-patterns-for-developers-using-javascript----part-one--b3e and I'm sure there are many other resources online to help familiarize you with JS patterns.
Although this may seem tedious at first, I guarantee by the time you've become comfortable with the diversity of expressive programming that you can achieve with JS you'll realize how powerful it makes it. This is why JS performs very well as a functional language building powerful UI with React or Angular and can easily jump to the server and build super powerful high concurrency back-ends for almost any application.
Yes, you are absolutely right but there is a reason why I chose linked-lists to show how Stacks and Queues works rather than just using Arrays. The reason is that while implementing stacks in JavaScript we can just use Push & Pop methods and we can show this is how stacks works but what about if we have to implement stacks in C or C++. In those languages, we do not have push and pop inbuilt methods but if he or she has gone through this linked-list method, he will atleast have an idea that this is one way using which we can proceed. So, in order to make a robust approch to stacks and queues I have used Linked-List approach.
Please have a look at this video- https://dev.to/vaidehijoshi/stacks-and-queues--basecs-video-series--20oj
Hi sixfeetvince, I think this is a great question! Definitely this is a question that should be asked (and answered) a lot more often, because I think there are as many people in your shoes as stars in the sky.
And--I've been there and done that!
When I was in your place, I floundered around for about a year and a half trying to figure out what to do. Do I just take some online trainings? In what? Do I try for certifications in various languages or processes? Do I read books? Do I actually go back to school and get my masters degree?
This is a terrible position to be in because usually by this time in your career, you need more money and stakes are higher, because you have debt, or a house, or a car payment, or a new child, or all of these things.
It can be entirely monumental a task, overwhelming and crippling.
I decided to do all of the things I mentioned above, and I also gave myself a long time to do it in. It's four years later right now, maybe four and a half years later, for me, and I earned my masters degree (I'll post a link I wrote about that) as well as attended conferences, local meetups, watched online videos, took online courses, read books, made side projects, etc. etc.
My advice in the end is: find things to do that are fun to do, that you want to do, and do them.
Here's the link about my master's degree: https://dev.to/scottshipp/why-i-did-my-masters-in-software-engineering-instead-of-computer-science-6kb
Talk about grasping in the dark. Talk about being new to the industry, or talk about things that you're learning about.
Advice on starting a tech blog is bigger than one reddit post can offer, but if you're looking for context, take a look at some of the relevant communities on Medium and Dev.to.
The goal isn't to style yourself as an expert... it's simply to catalogue your journey.
Hello!
Elm can absolutely be used as a frontend for any type of backend application. Elm apps are built and served just like any javascript SPA.
Your Django backend should expose JSON endpoints which your Elm app will fetch using a package like elm-lang/http.
There is a bit of work involved to map your JSON responses to Elm data types through JSON decoders, but there are tools online to assist (like this Json-To-Elm project).
For a fully working example of this, check out this article and linked github repo: https://dev.to/rtfeldman/tour-of-an-open-source-elm-spa
Elm's development can certainly seem slow compared to Javascript frameworks, but this is deliberate. Evan takes his time to carefully plan the language and ensure new features are solid before releasing them. He recently posted a roadmap, which should be within the first couple pages on r/elm.
I'd highly recommend going with cmake. It's way more human readable comparing it to Makefile. Actually it will generate a Makefile for you so you can build actual firmware.
When it comes to hal you have option to use ST's C hal, or if you want to go full C++ there are quite few modern C++ STM32 hal libs out there. To be honest I've never tried any yet. The project I'm currently working on is based on STM32WB and I'm using ST's C hal, application layer is in C++, and I'm using cmake for build automation.
This blog might be a good starting point https://dev.to/younup/cmake-on-stm32-the-beginning-3766
I can help you if you want.
You can see my GitHub and one of my blog posts.
There's that but it's not recent: https://dev.to/hugovk/python-version-share-over-time-6-1jb8
The author gives links to the module he used so you could probably reuse that to extract more recent stats.
'In 2020 Meteor has been taken over by Meteor Software, which is vc-funded by Tiny Ventures, so MDG can focus on their new main business with Apollo. Meteor Software offered a strong collaboration with the community, shorter release cycles and a vision for the future of Meteor, which is becoming reality with the upcoming major 2.0 release.
A major upgrade has been introduced by using React Native as alternative to cordova while keeping all the benefits that Meteor offers. Hosting plans also changed to include more affordable plans and the famous free-tier plan is back again!'
Basically MDG have moved on to Apollo and Tiny Ventures are funding a new team and revamp of Meteor.
https://dev.to/jankapunkt/why-choose-meteor-or-not-for-your-next-project-1gnh
WebComponents are an interesting topic. As a long time proponent (I started Solid to be a WebComponents library), I have a few thoughts coming out the other side. https://dev.to/ryansolid/maybe-web-components-are-not-the-future-hfh
What about react-fluent-form? I implemented my own library because other libraries were not intuitive enough for me. You can read the documentation here:
https://www.react-fluent-form.com/
If you are more like of a blog guy i also wrote and introductional blog:
https://dev.to/ysfaran/react-fluent-form-how-to-write-forms-with-validation-in-few-steps-56ho
react-fluent-form didn't get too much attentionen yet so i would love the hear some feedback and maybe some comparison to other and more popular libraries from user side.
I appreciate any feedback! Feel free to file github issues in case of bugs or feature requests. Thank you!
It feels to me this is a fast moving space at the moment and I have not seen good books on it. Simon Brown does good work.
https://dev.to/simonbrown/software-architecture-isn-t-about-big-design-up-front-4hol
https://dev.to/simonbrown/a-minimal-approach-to-software-architecture-documentation-4k6k
Also featured ->
https://twitter.com/ArchiThinkery/status/1278176949999894530
What is up with that URL?!
I guess it redierects to this article on dev.to:
https://dev.to/liviufromendtest/how-to-write-css-selectors-like-a-boss-4k47
The article... doesn't contain anything interesting. It is basic info about how CSS selectors work:
- by ID
- by Class
- by "name" attribute
- by "any" attribute
- by multiple attributes
- by part of an attribute
- by parent element
- by text inside element
The article is basically an ad for the authors product (Endtest).
File this content under Spam...
Programación, man!
Leete como definir variables en JS en MDN, llená el perfil de LinkedIn con los hashtags mas populares de dev.to (por ejemplo #assembly, #ia, #a11y, #cssgrid, #gamedev, #archlinux, #ui, #ux, #cloud, #serverless, #scrum, #tensorflow) y en una semana, máximo, estas laburando remoto en Europa, cobrando en euros, mientras te tomas unos tragos en alguna playa!
These other answers are a bit misleading. There's a lot of reasons to use an Object over an Array. Objects are a bit slower, like /u/AegirLeet said, however it's a minor performance boost in the same way that using single quotes are faster than double quotes. I'm not suggesting you use StdClass, but instead build your own Class that adds value for your context.
​
Some reading as to why Objects > Arrays:
https://dev.to/aleksikauppila/dont-return-associative-arrays-28il
Use arrow functions:
xhr.addEventListener("readystatechange", () => {
Instead of:
xhr.addEventListener("readystatechange", function() {
​
When you are assigning this.store to var stoke, "this" is not pointing to the context where $store is located.
So I didn't do an internship but I can imagine it's similar to start your first day as a junior engineer... Here's an article I wrote, but if you just want me to sum it up... They know your level of skill already, it's okay to learn on the job, do your best and make an actual effort to learn while working versus just trying to "get things done"
If interested: https://dev.to/iamtravisw/5-things-i-wish-i-knew-before-my-first-day-of-being-a-junior-software-engineer-4cfd
​
Good luck!
Both sites have the same content, but from different authors. This is all smelling awful. While I trust dev.to I'm left feeling like the content has been stolen and re-published. These sort of things suck and erode trust in the community (a community of techies, nonetheless!.. I expect something as low as this in other industries, not here.)
I mean, you can put those words in my mouth or you can read the write-up I made regarding the subject and see what backs up my view
I started a series tailored towards NodeJS developers who want to learn Rust:
https://dev.to/gruberb/intro-to-web-programming-in-rust-for-nodejs-developers-lp
Feel free to follow along.
My two cents: Knowing both languages will put you ahead in the up coming years! Although Rust can (soon) everything Go can as well.
Is this something like Medium but specifically for developers? As someone who's constantly struggling to come up with an original idea for a side project that would hopefully become a business, I wonder how platforms like this gather an audience when they offer pretty much the same functionality as numerous others and just a different skin.
>Well, it might not be a very "humane" thing to say, but as far as I can tell, most people on dev.to are imposters in one way or another.
In a lot of ways I agree with you, but what I take away from dev.to is that there is a sizable market of people struggling with basic parts of software development. Impostors or not, I do like the trend of people documenting their struggles for the world to see, even if most professionals will find it trivial, if only that it might help someone else.
>Also as a side note, saying that you have "inadequacies" is not a nasty or harmful statement. It's just a fact of life. If you were perfect there would be nothing to improve, nothing to overcome, and life would be ultimately boring.
I couldn't agree more. Recognizing your limitations is one of the healthiest mindsets you can have, especially when paired with the drive to constantly improve oneself.
You should check the sidebar for /r/bash. The website rosettacode.org is also very nice for this. It's a compendium of programs, each written in several languages to act as a Rosetta. Another resource are programming challenge websites. I like codewars.com. O'Rilley has the bash cookbook, which may still be free, and is pretty much exactly what you want. No starch press has a book called wicked cool shell scripts, which is pretty much a collection of shell scripts and explanations of how they work. Maybe that's the most appropriate for what you're asking for.
Also, this isn't more scripts, but the three most valuable resources I've found for bash are this:
BashPitfalls, https://mywiki.wooledge.org/BashPitfalls , a list of common antipatterns in bash; why they are wrong, and how to do it right. Reference this when trying to determine if someone knows their stuff. Many of these mistakes are still taught. In fact, it's like shitty advice about bash has become permanently ingrained in the Internet hive mind, and then institutionalized by trade schools. Really, his entire wiki is gold. Take a look.
Shell Scripts Matter, https://dev.to/thiht/shell-scripts-matter , a short article about approaching shell scripts with the same maturity that you should any other programming project. That means using version control, writing tests, and checking for errors with a static analysis tool. Read this first.
The official gnu bash user manual, which is book length and definitive. Lots of nitpicky details in here. Did you know that function bodies don't need curly braces? Any compound command will do, like a while loop, for example. Oh, and, surprise -- since you didn't quote your delimiter for the here doc you used everything starting with a dollar sign in your string has been replaced with a variable expansion. And, hey, there's this amazing thing called readline.
I took a college class on Linux administration that didn't teach me any of this. What the hell?
Just run parity --no-warp and you have a full verified copy of the blockchain at ~ 90GB. I just ran this number this week.
Did you actually read the link I posted https://dev.to/indy_singh_uk/strings-are-evil-9f9#12 their program only ever reached ~16,000KB, or 16MB in memory usage, because although over its lifetime it made a total of 7.4GB in allocations, it was continually cleaning up after itself, for example: allocate 2MB, allocate 2MB, allocate 2MB, allocate 2MB, garbage collect 8MB
Hey there. I was in the same boat as you - tried a lot of different resources but none seemed to stuck. What helped me understand was a combination of a few things:
First, to outline what redux really is: https://dev.to/hemanth/explain-redux-like-im-five
From there, I went through Dan Abramov's own introduction to Redux on Egghead: https://egghead.io/series/getting-started-with-redux
I still didn't fully get it, so to get a practical real-world example I followed this up with Wes Bos' free Redux course: https://learnredux.com/ - this is a little bit outdated in terms of the other technology, but the Redux in the course is still valid and frankly, when not worrying about the old router syntaxes and other things, this course actually does some good explaining of not only how, but why.
Now this is where things really started to stick. At this point I actually went over Dan Abramov's videos again (or at least some of the subjects that were still a little bit cloudy), and now everything seemed to stick.
I built a few small meaningless applications with few actions and very simple reducers and upscaled my redux integration level in the next project. Now I feel like I have a decent grasp on it (still have yet to go forward with Redux Thunk, but I don't see a use right now).
It's important to note that you should not start with trying to pull Redux into your existing project (unless it is really simple). I'd start a new very basic example (I would say todo-list, but since you've already done that maybe a bookstore with a list(array) of books(objects)?), and think Redux from the get-go. This helps you understand how things work together and this will definitely help you integrate it into an already existing project later.
Best of luck! I'm pretty bored lately and in-between jobs until start 2018, so if I can help you are more than welcome to PM me!
Had to switch back briefly for a project, and at the time, My cofounders were not ready to hire TypeScript developers (difficulty finding candidates and salary considerations in the future). So I was forced to work with plain JavaScript and Meteor.
It’s all over now though. I retired from the project. Now they’re back to PHP and I’m building my own CMS in TypeScript. Everyone is happy.
First thing I would recommend is this course https://watchandcode.com/ . Then, after you finish it, read a book about javascript, maybe the one that's recommended on sivers.org, Professional JavaScript for Web Developers. If I could go back in time, I would start learning in that order. With watchandcode you will get insight on what you can do with javascript, you will build a project with plain javascript, so you will not get bored with details or stuff you won't use in the first year or two while working as a junior. This article https://dev.to/pbeekums/teach-writing-code-first explains what I'm trying to say. I hope I helped you. Good luck!