I think it has to do with the times. Because sl admin came up in a pre DRF time when people use Django to serve templates, the work to build it into the framework came more naturally. With lots of more modern web app frameworks mainly focusing on just being APIs for single page applications, having html templates and stuff in the core project and having contributors build this stuff in doesn’t happen as naturally.
I totally agree though- huge selling point of Django!
Funny that this is the exact opposite of "Speed matters: Why working quickly is more important than it seems" (https://news.ycombinator.com/item?id=36312295) from a couple days ago here.
Both speed and "slow productivity" have their place depending on the type of work you do.
I think for junior and mid level ICs, and leadership/management focused people (maybe even senior ICs), speed is paramount.
For staff/principal roles, the balance shifts toward being able to be able to focus more singularly on very challenging problems.
Maybe for consumer apps, but for a lot of enterprise apps that have to be compatible with existing APIs or domain-specific data standard that require two name fields, that’s not really a viable approach.
Quickly growing edtech SaaS company that is changing the way students plan out their college and career paths. We build student-friendly market-leading tools for all of the tasks students need to accomplish to figure out what they'll do after high school. Examples: college search, course planning, career videos, college applications, internships, etc. We have 80 + different features, customers in 15 states, and are the fastest growing solution in the space. Raised seed funding a couple years ago and have been growing organically based on revenue since.
keywords: education, edtech, workforce development
Product and Engineering team is currently 10 people. We're planning on growing a lot in the next year. This is good time to get in and help grow/scale the team.
BE Stack: Django, DRF, Graphene, Celery, AWS, Redis
FE Stack: React + react hooks, react-query, GraphQL some older modules use redux, material ui
I'm our CTO and will be managing the hiring for these roles. If you're interested in director or VP of eng roles, we will also be hiring in the next couple months for more leadership roles. Please feel free to reach out to me with any questions: mike[at]schoolinks.com
Quickly growing edtech SaaS company that is changing the way students plan out their college and career paths. We build student-friendly market-leading tools for all of the tasks students need to accomplish to figure out what they'll do after high school. Examples: college search, course planning, career videos, college applications, internships, etc. We have 80 + different features, customers in 15 states, and are the fastest growing solution in the space. Raised seed funding a couple years ago and have been growing organically based on revenue since.
keywords: education, edtech, workforce development
Product and Engineering team is currently 9 people. We're planning on growing a lot in the next year. This is good time to get in and help grow/scale the team.
BE Stack: Django, DRF, Graphene, Celery, AWS, Redis
FE Stack: React + react hooks, react-query, GraphQL some older modules use redux, material ui
I applaud your ambition, but i can’t imagine how this would be work. You’re employed full time, you’re in grad school full time, and you’re a new father—- how would you actually have any time to do an internship? How much time you could actually give? How would you be able to concentrate enough to learn the concepts and apply them to actually be a net contributor to the company after a certain amount of time? As someone who who has hired many interns and seen some work out and others not, I don’t see that you’re setup for success- and the type of team that would bring you on in this situation likely wouldn’t be one you would want to learn from.
I don’t know all of your situation, but if I we’re looking at your profile, having an internship as a software engineer would make think you’re more de-risked as a hire than having a grad degree.
Apple Airpod Pros -- long battery life, near instant bluetooth tethering. Even other expensive headphones/earbuds (Bose) for instance could not compete with the ease of use, noise cancellation, and comfort.
I don't think about headphones anymore, they just work the way they're supposed to.
Same, Crown Heights to Midtown. Would time my commute so I could get a seat and pull out my laptop to just code with no emails or other stuff coming in. Probably some of the most productive time. You just have to be good with heading in early and living far enough away to get on subways when they are relatively empty further out from Manhattan.
Quickly growing ed tech SaaS company that is changing the way students plan out their futures. We build student-friendly college and career readiness tools. Think college search, course planning, career videos, etc. We've got 25 + different modules.
We're hiring for an experienced full stack engineer and looking for someone with:
- Django Experience
- React Experience
- Strong interest in the education space-- basically someone who is passionate about the product and would want to shape the long term direction of what we're building.
Raised seed funding and healthy revenue coming in, Pre-series A, so lots of growth potential for this hire.
SchooLinks | Experienced Full Stack (Django + React) | Austin, TX or Remote
schoolinks.com
We're a college and career readiness platform currently being used by many large school districts, including Dallas Independent School District. We're looking for a mid to senior level, experienced, full stack developer to join our quickly expanding team and looking to leave a lasting impact on a product that leaves a lasting impact on students' lives.
Requirements/About you:
- Hunger to really understand problems and data from a conceptual level— we don't just want to tell you what to do do, but want you to figure out how to solve problems with data integration and framework design. We're building for speed and scale
- You are not comfortable just building what you're told... specifically you must be comfortable taking ownership over technical decisions about code structure, tooling, and be interested in the actual product you're working on
- Looking to grow professionally (and ideally looking to do it quickly!)
- At least 4 years of experience shipping production quality code in both the FE and BE
- At least 2 year of experience in Django OR React (we can help you get up to speed in one, but not both)
- Experience using MySQL or some other SQL engine in a production environment
Nice to haves:
- You either want to be coming a technical manager or are open to that possibility in the future (we're looking to actively groom technical leadership in our organization)
- AWS experience
- Experience with Python Pandas
- Previous work with Celery/RabbitMQ
- Interest or experience with education and educational data (standards/conventions, SIS, state reporting, etc.)
- Knowledge of web app caching and performance optimization
1. I think it’s better to focus on doing - especially if you’re interested in working with an earier stage company. You’re much more versatile and if you choose the right company with an upward trajectory then you have the chance to specialize more into data science and learn model building if you want to. Also, data science seems sexy, but I find it most rewarding when you can put your own models into prod and also I think it’s useful for people to have the context around what it involves before they specialize. I’m 28, and had a lot of peers go into data science and quickly realize that it was the hype that lead them there and that they enjoy engineering more.
2. Look for work in a different part of the country... or maybe just the right organization that’s willing to take a chance on you. We’re in Austin and we’ve hired smart, hardworking kids who’ve never touched the languages we use and get them contributing meaningfully in <2 months.
3) I used to work for a startup where our CTO would not hire a data scientist unless they could write production code (in backbone and rails which I didn’t know at the time) and after I started, I spend 4-5 months just learning to be a full stack dev- I think that was so useful for my career as a data scientist. It meant that data scientists at this company could put whatever models they were running into the product- it drastically simplified org structure—- much more autonomy and fewer project management dependencies.
Sure not a lot of data scientists wanted to also be or make them selves into full stack developed, but you’d end up with the really gritty ones who and they’d end up being more loyal and much more on the same page as the rest of the engineering team it was way better for the whole org.
We’re hiring interns + junior full time people by the way
I could not read the actual article- seems some script in one of the adds was redirecting me to some spammy Win $1000 sweepstakes every time I clicked the link. Did that happen to anyone else? (Using mobile safari)
The hiring process includes a 5 minute recorded video screen about some JS and React/RN basics. Then a brief 30-45 min live coding challenge, code discussion, and some situational questions.
A bit about us:
SchooLinks is a college and career readiness platform with curriculum that engages students throughout the process of self discovery, career education and college planning and application. The student-centric experience is able to create a wealth of behavioral data, and its machine learning algorithms leverage those data to personalize college recommendations and content to further drive student engagement. SchooLinks then serves actionable insights to counselors that help them act in real time to become more effective. On a district level, the sophisticated data models power a full suite of accountability tools to allow administrators to monitor and achieve desired college and career readiness outcomes.
Our engineering team is INSANELY productive. We're shipping new modules almost every week and we offer an environment where you'll be challenged and able to shape the product. The company is quickly growing and looking for candidates who will be able to eventually contribute in leadership positions.
SchooLinks - SchooLinks.com | Post-seed, revenue generating, fast growing edtech startup located in downtown Austin, TX. Hiring full time, full stack developers. Python + PHP and Angular.
In an ideal situation for science writing, who someone is, their agenda, etc, shouldn't matter for interpretation right? But here having read the piece without that context, and then having someone point out who the author was really changed my interpretation- for better or for worse.
Many of the points she makes about statistical validity make sense - complex, non linear systems are difficult to predict, models need to be validated on data different from their training sets, etc. So those points, without digging into the real meat of how they're applied to these models specifically -- which she knows lawyers won't, serve to mislead.
I think what's also at the heart of this discussion though is whether what she's writing really is science or if it's opinion/has an agenda. When one puts oneself in the position of writing an overview like this, well then maybe it's one's responsibility to present (as well as complicate) the general consensus rather than present an argument that is not that mainstream as more of a consensus then it really is.
Okay, that makes sense, I agree with you there. Thanks for making that point. What maybe would have been better and a less normative way to make the point is that she has as track record of writing and making statements that advance claims that are outside the mainstream of climate science.
One point that it looks like Curry takes aim with more generally is the degree to which there is a consensus about global warming among scientists. She says that 97% of scientists can't believe in it because they haven't studied it or built their own models, etc -- they have "second order belief"
That's an important epistemological point to make. I guess we should all make our own GCMs to confirm for ourselves that we believe in AGW?? Sure maybe if we all had unlimited time. In science we share a common set of methodological beliefs and assumptions-- maybe there's a breakdown for her there, but I'd like to think the at the research institutions and tools that exist help accurately propagate true findings to the public especially in a matter that's as pressing to our long term wellbeing as climate change!
Sorry? Sure, don't feel the need to believe any of their refutations, but you can follow their links to her statements and decide whether or not you agree with her take.
Yeah it's kind of sad actually. I started reading this as serious piece and then sent it to a professor I had during my undergrad for a class on climate change. So embarrassing!!
The broad points about training data and non-linearities are important- but on a second pass it's hard to believe that people who spend their lives building GCMs don't think deeply about these challenges.
I totally agree though- huge selling point of Django!